You are not logged in.
You can get your system bootable again with this:
https://bbs.archlinux.org/viewtopic.php … 8#p1459368Gnome-software lets your system boot in some kind of single user mode where it updates packages. That target is not enabled by default on archlinux, resulting in a system that boots to a disabled target.
This service is something I am assuming all users of gnome-software will need to have enabled, so is there a way to enable this service passively as gnome-software or packagekit is installed? Otherwise I for see a while lot of people having unbootable systems their first boot
I don't really know what I'm doing.
Offline
@Pank, I printed a self-made pdf with evince a couple of days ago, and didn't have any issues.
I can test if you have a pdf that doesn't print that you could link.
Offline
The reality that nobody really should update his system with some Packagekit GUI no matter if some special systemd target is enabled or not. There is no way for Gnome Software to parse any messages regarding *.pacnew's etc. or info, which is provided as echo statements in *.install files.
Offline
On both my systems I have problems with the full pdf book here here. Try the third sample (pdf link). I print two pages per page. On my one computer the page is pushed up so that approx. 1/8 of the page is visible (rest is white). On the PC I got a fully white pages. I use evince preview, or print to cups-pdf. I have no problem with evince 3.12.
Arch x64 on Thinkpad X200s/W530
Offline
I noticed a small bug while testing gnome-unstable : python-cairo is a missing dependency of gnome-music. I had to install it if I want to launch gnome-music.
Offline
I am using Adwaita for the Window and GTK theme and have enabled the "Global Dark Theme" setting (I assume this is how you enable the new reword Adwaita Dark Theme). Most windows look fine (gedit, terminal, nautilus, [gnome-apps]), however, some apps such as Chrome, Terminator, LibreOffice, etc still have white window decorations. Is there anything I can do to fix this or is it a "wait until the apps catch up" type situation?
Offline
Global dark theme only works with gtk3 applications.
Finding matching dark gtk2 theme is only solution I know of, or find a theme that's dark by default and works on both.
EDIT:
@Pank, I tried the pdf you linked. Everything looks ok in print preview, and when printed to pdf with evince 3.13.92
you could try clearing evince's saved print settings with:
mv ~/.config/evince/print-settings ~/.config/evince/print-settings.bak
while evince isn't running.
Last edited by ooo (2014-09-23 19:55:27)
Offline
I am using Adwaita for the Window and GTK theme and have enabled the "Global Dark Theme" setting (I assume this is how you enable the new reword Adwaita Dark Theme). Most windows look fine (gedit, terminal, nautilus, [gnome-apps]), however, some apps such as Chrome, Terminator, LibreOffice, etc still have white window decorations. Is there anything I can do to fix this or is it a "wait until the apps catch up" type situation?
try this Adwaita-dark version http://goo.gl/gJYmgQ
Offline
kas21 wrote:I am using Adwaita for the Window and GTK theme and have enabled the "Global Dark Theme" setting (I assume this is how you enable the new reword Adwaita Dark Theme). Most windows look fine (gedit, terminal, nautilus, [gnome-apps]), however, some apps such as Chrome, Terminator, LibreOffice, etc still have white window decorations. Is there anything I can do to fix this or is it a "wait until the apps catch up" type situation?
try this Adwaita-dark version http://goo.gl/gJYmgQ
So, does this just refer to Gnome-Shell's GTK3 theme and add a GTK2 theme?
Offline
@Pank, I tried the pdf you linked. Everything looks ok in print preview, and when printed to pdf with evince 3.13.92
you could try clearing evince's saved print settings with:
mv ~/.config/evince/print-settings ~/.config/evince/print-settings.bak
while evince isn't running.
Thanks. I tried renaming my print-settings file, but I'm still getting weird prints.
Did you specify two pages per side in the second tab of the print dialog?
This is what it looks like for me: http://i.imgur.com/gCNutTS.png
Arch x64 on Thinkpad X200s/W530
Offline
roi.dm wrote:kas21 wrote:I am using Adwaita for the Window and GTK theme and have enabled the "Global Dark Theme" setting (I assume this is how you enable the new reword Adwaita Dark Theme). Most windows look fine (gedit, terminal, nautilus, [gnome-apps]), however, some apps such as Chrome, Terminator, LibreOffice, etc still have white window decorations. Is there anything I can do to fix this or is it a "wait until the apps catch up" type situation?
try this Adwaita-dark version http://goo.gl/gJYmgQ
So, does this just refer to Gnome-Shell's GTK3 theme and add a GTK2 theme?
gtk-3.0/gtk.css
@import url("resource:///org/gtk/libgtk/theme/Adwaita/gtk-contained-dark.css");
and mod the gtk2 to match (almost) the gtk3
(you need to reload the shell, sometimes you need to logout)
Last edited by roi.dm (2014-09-23 20:47:26)
Offline
Did you specify two pages per side in the second tab of the print dialog?
This is what it looks like for me: http://i.imgur.com/gCNutTS.png
nope, I used one page per side.
with two pages per side, I actually get identical results to yours with the pdf you linked.
I also tested the beaviour with an another pdf, and with two pages per side it apparently only prints the page on the right, and leaves the left one blank.
Offline
I upgraded from the gnome-unstable repo, did I needed also to enable testing and testing-community ?
Does your keyboard volume keys and backlight working in a Wayland session ?
Offline
I upgraded from the gnome-unstable repo, did I needed also to enable testing and testing-community ?
Does your keyboard volume keys and backlight working in a Wayland session ?
[gnome-unstable] is always built against the testing repos which means you have to enable ALL of them.
Offline
@blackout23
Thanks.
Offline
Pank wrote:Did you specify two pages per side in the second tab of the print dialog?
This is what it looks like for me: http://i.imgur.com/gCNutTS.png
nope, I used one page per side.
with two pages per side, I actually get identical results to yours with the pdf you linked.
I also tested the beaviour with an another pdf, and with two pages per side it apparently only prints the page on the right, and leaves the left one blank.
Would you mind testing it with Evince 3.12? If you also do not get an error there I'll open a bug report. Thanks!
Arch x64 on Thinkpad X200s/W530
Offline
Does your keyboard volume keys and backlight working in a Wayland session ?
The keys does works but only when I'm starting the gnome-shell Wayland session from GDM and not when running "# gnome-shell --wayland --display-server"
Edit: "gnome-session --session=gnome-wayland" works nicely.
Last edited by dhead (2014-09-24 00:02:36)
Offline
Would you mind testing it with Evince 3.12? If you also do not get an error there I'll open a bug report. Thanks!
looks just like it should in print preview (both pages visible) with evince 3.12.2
Offline
On both my systems I have problems with the full pdf book here here. Try the third sample (pdf link). I print two pages per page. On my one computer the page is pushed up so that approx. 1/8 of the page is visible (rest is white). On the PC I got a fully white pages. I use evince preview, or print to cups-pdf. I have no problem with evince 3.12.
I get identical results... Whenever I use 2 pages per side, it doesn't work, no matter which PDF I try to print. I've tried with evince 3.12 and it works as it should.
Offline
In the actual state of gnome unstable repo, the mouse focus does weird things.
Open a gnome-terminal and change to the desktop (any other virtual desktop ctrl + alt + down) and the mouse does nothing, the cursor is like mode text shape, and i can't click on anything, neither double button click, nothing.
I have to go to shell mode (super key) and back so the mouse respond again.
Offline
In the actual state of gnome unstable repo, the mouse focus does weird things.
Open a gnome-terminal and change to the desktop (any other virtual desktop ctrl + alt + down) and the mouse does nothing, the cursor is like mode text shape, and i can't click on anything, neither double button click, nothing.
I have to go to shell mode (super key) and back so the mouse respond again.
What drivers are you using? I don't have this issue with intel drivers.
Offline
Im using intel drivers too. Its only happens whenever change from an app to desktop. Changing between apps its fine.
Maybe im explaining wrong the issue because my poor english. Ill try again.
I open any app (gnome-terminal is better because i can see how the mouse cursor don't change when it should be) then I focus the mouse over the terminal, later I change to another virtual desktop with ctrl + alt + down. If there isn't any app in this new virtual desktop, the mouse cursor don't change and leave the text cursor shape, and mouse clicks do nothing anymore, however if I change to shell (windows key or focus in botton left) the mouse is fine again.
Offline
Im using intel drivers too. Its only happens whenever change from an app to desktop. Changing between apps its fine.
Maybe im explaining wrong the issue because my poor english. Ill try again.
I open any app (gnome-terminal is better because i can see how the mouse cursor don't change when it should be) then I focus the mouse over the terminal, later I change to another virtual desktop with ctrl + alt + down. If there isn't any app in this new virtual desktop, the mouse cursor don't change and leave the text cursor shape, and mouse clicks do nothing anymore, however if I change to shell (windows key or focus in botton left) the mouse is fine again.
I can confirm this issue. I'm using intel drivers as well. (git version, mesa as well)
Offline
pushakk wrote:Im using intel drivers too. Its only happens whenever change from an app to desktop. Changing between apps its fine.
Maybe im explaining wrong the issue because my poor english. Ill try again.
I open any app (gnome-terminal is better because i can see how the mouse cursor don't change when it should be) then I focus the mouse over the terminal, later I change to another virtual desktop with ctrl + alt + down. If there isn't any app in this new virtual desktop, the mouse cursor don't change and leave the text cursor shape, and mouse clicks do nothing anymore, however if I change to shell (windows key or focus in botton left) the mouse is fine again.
I can confirm this issue. I'm using intel drivers as well. (git version, mesa as well)
The same thing happens for me as well, but I can get out of it by simply clicking the mouse once. The desktop right-click menu opens when I do that, and the cursor changes to the normal one.
Mesa and intel from the testing repo here.
Offline
I can confirm this bug as well. what's interesting is that if you leave your cursor over the close window button, switch desktops, and click your mouse button, you can close the window. You can also minimize and resize the window from another workspace.
Offline