First of all, sorry for my recent absence, I was hoping to spend some time on Arch over Christmas, which I didn't.
Anyway, today's systemd upgrade causes a problem which I was only able to solve by downgrading:
When systemd launched kdm.service, X started, but the kdm greeter never appeared - instead X just sat there with the busy mouse pointer. systemctl stop kdm.service hung too, I could only kill -9 the X process.
When I downgraded to 196-2, the greeter started immediately after the systemctl daemon-reexec in post_upgrade. I have no idea where to start, so any help is appreciated.
Even worse: After the downgrade, systemctl start /boot (and thus the automounter) didn't work, I had to mount /boot manually.
On 8 January 2013 10:27, Thomas Bächler thomas@archlinux.org wrote:
First of all, sorry for my recent absence, I was hoping to spend some time on Arch over Christmas, which I didn't.
Anyway, today's systemd upgrade causes a problem which I was only able to solve by downgrading:
When systemd launched kdm.service, X started, but the kdm greeter never appeared - instead X just sat there with the busy mouse pointer. systemctl stop kdm.service hung too, I could only kill -9 the X process.
When I downgraded to 196-2, the greeter started immediately after the systemctl daemon-reexec in post_upgrade. I have no idea where to start, so any help is appreciated.
Even worse: After the downgrade, systemctl start /boot (and thus the automounter) didn't work, I had to mount /boot manually.
Today I have accidentally upgraded to systemd 197 (I was trying to avoid it because of this email).
I can partially confirm this problem – after booting it takes quite some time (probably a few minutes) before X pops up. When the X finally starts, it shows the busy mouse pointer as you mentioned. However, for me KDM starts, even though it takes a while.
Lukas
I'm using KDE as well, but have not been able to reproduce this problem. Any chance you could get some more debug info out of it? Sounds like something times out...
On Fri, Jan 11, 2013 at 6:17 PM, Lukas Jirkovsky l.jirkovsky@gmail.com wrote:
On 8 January 2013 10:27, Thomas Bächler thomas@archlinux.org wrote:
First of all, sorry for my recent absence, I was hoping to spend some time on Arch over Christmas, which I didn't.
Anyway, today's systemd upgrade causes a problem which I was only able to solve by downgrading:
When systemd launched kdm.service, X started, but the kdm greeter never appeared - instead X just sat there with the busy mouse pointer. systemctl stop kdm.service hung too, I could only kill -9 the X process.
When I downgraded to 196-2, the greeter started immediately after the systemctl daemon-reexec in post_upgrade. I have no idea where to start, so any help is appreciated.
Even worse: After the downgrade, systemctl start /boot (and thus the automounter) didn't work, I had to mount /boot manually.
Today I have accidentally upgraded to systemd 197 (I was trying to avoid it because of this email).
I can partially confirm this problem – after booting it takes quite some time (probably a few minutes) before X pops up. When the X finally starts, it shows the busy mouse pointer as you mentioned. However, for me KDM starts, even though it takes a while.
Lukas
On 11 January 2013 18:26, Tom Gundersen teg@jklm.no wrote:
I'm using KDE as well, but have not been able to reproduce this problem. Any chance you could get some more debug info out of it? Sounds like something times out...
Console timeouts on mounting remote filesystems.
I remember I had this problem earlier which I solved by: systemctl disable remote-fs.target
However, this update reenabled it for some reason. Is there a way to make these changes permanent?
I have no idea why KDM starts longer than usual though. There's nothing unusual in any log. It seemed to me that I heard harddisk to be spinning more than usual when KDM is loading, but that's something I don't usually look for, so I may be wrong.
Lukas
On Fri, Jan 11, 2013 at 07:10:54PM +0100, Lukas Jirkovsky wrote:
On 11 January 2013 18:26, Tom Gundersen teg@jklm.no wrote:
I'm using KDE as well, but have not been able to reproduce this problem. Any chance you could get some more debug info out of it? Sounds like something times out...
Console timeouts on mounting remote filesystems.
I remember I had this problem earlier which I solved by: systemctl disable remote-fs.target
Why would you want to do this? Just use noauto,x-systemd.automount on your remote filesystems in fstab and they'll only be mounted on first access.
However, this update reenabled it for some reason. Is there a way to make these changes permanent?
The symlink is shipped by upstream and belongs to the systemd package. If you're bent on disabling it, you'll need to use pacman's NoExtract.
I have no idea why KDM starts longer than usual though. There's nothing unusual in any log. It seemed to me that I heard harddisk to be spinning more than usual when KDM is loading, but that's something I don't usually look for, so I may be wrong.
Lukas
On 11 January 2013 19:14, Dave Reisner d@falconindy.com wrote:
Why would you want to do this? Just use noauto,x-systemd.automount on your remote filesystems in fstab and they'll only be mounted on first access.
Thank you, I didn't know that.
The symlink is shipped by upstream and belongs to the systemd package. If you're bent on disabling it, you'll need to use pacman's NoExtract.
I see.
On 11 January 2013 19:10, Lukas Jirkovsky l.jirkovsky@gmail.com wrote:
I have no idea why KDM starts longer than usual though. There's nothing unusual in any log. It seemed to me that I heard harddisk to be spinning more than usual when KDM is loading, but that's something I don't usually look for, so I may be wrong.
Now I think I caught it. There's a quite long wait on: Starting Authorization Manager...
Lukas
On Fri, Jan 11, 2013 at 07:24:28PM +0100, Lukas Jirkovsky wrote:
On 11 January 2013 19:14, Dave Reisner d@falconindy.com wrote:
Why would you want to do this? Just use noauto,x-systemd.automount on your remote filesystems in fstab and they'll only be mounted on first access.
Thank you, I didn't know that.
The symlink is shipped by upstream and belongs to the systemd package. If you're bent on disabling it, you'll need to use pacman's NoExtract.
I see.
On 11 January 2013 19:10, Lukas Jirkovsky l.jirkovsky@gmail.com wrote:
I have no idea why KDM starts longer than usual though. There's nothing unusual in any log. It seemed to me that I heard harddisk to be spinning more than usual when KDM is loading, but that's something I don't usually look for, so I may be wrong.
Now I think I caught it. There's a quite long wait on: Starting Authorization Manager...
Which is polkit... Any joy with 0.107 instead of 0.109? You might have had both upgraded at the same time (guessing based on build dates).
On 11 January 2013 19:54, Dave Reisner d@falconindy.com wrote:
Which is polkit... Any joy with 0.107 instead of 0.109?
Nope. I don't even know if it's related to the slower startup.
You might have had both upgraded at the same time (guessing based on build dates).
I think I was already using polkit 0.109.
Fortunately this slowdown is not nearly as bad as waiting for NFS that is, thanks to your help, now fixed. I can live with that, I don't need to boot that often.
Lukas
Le mardi 8 janvier 2013 10:27:55 Thomas Bächler a écrit :
First of all, sorry for my recent absence, I was hoping to spend some time on Arch over Christmas, which I didn't.
Anyway, today's systemd upgrade causes a problem which I was only able to solve by downgrading:
When systemd launched kdm.service, X started, but the kdm greeter never appeared - instead X just sat there with the busy mouse pointer. systemctl stop kdm.service hung too, I could only kill -9 the X process.
When I downgraded to 196-2, the greeter started immediately after the systemctl daemon-reexec in post_upgrade. I have no idea where to start, so any help is appreciated.
Even worse: After the downgrade, systemctl start /boot (and thus the automounter) didn't work, I had to mount /boot manually.
No problems here with kde/systemd 197
++
Am 08.01.2013 10:27, schrieb Thomas Bächler:
First of all, sorry for my recent absence, I was hoping to spend some time on Arch over Christmas, which I didn't.
Anyway, today's systemd upgrade causes a problem which I was only able to solve by downgrading:
When systemd launched kdm.service, X started, but the kdm greeter never appeared - instead X just sat there with the busy mouse pointer. systemctl stop kdm.service hung too, I could only kill -9 the X process.
When I downgraded to 196-2, the greeter started immediately after the systemctl daemon-reexec in post_upgrade. I have no idea where to start, so any help is appreciated.
Even worse: After the downgrade, systemctl start /boot (and thus the automounter) didn't work, I had to mount /boot manually.
Okay, it seems this issue was related to network interface names: When I upgraded to 197-1, the network renaming was enabled by default, even for upgrades (which changed in -2). I have some custom services that explicitly wait for certain network devices, which then didn't show up. That prevented my system from reaching network.target and some services had very long delays, this probably blocked KDM from working properly (that last sentence is mostly guesswork).
arch-dev-public@lists.archlinux.org