reassign 736880 libpam-systemd 204-5
reassign 726763 libpam-systemd 204-5
reassign 731426 libpam-systemd 204-5
reassign 731602 libpam-systemd 204-5
reassign 735591 libpam-systemd 204-5
reassign 735593 libpam-systemd 204-5
reassign 735628 libpam-systemd 204-5
forcemerge 729576 736880 726763 731426
Control: reassign -1 libpam-systemd 204-5
On 2013-12-22 17:38:53 +0100, Vincent Lefevre wrote:
On 2013-12-22 16:21:15 +0100, Andreas Cadhalpun wrote:
this seems like yet another duplicate of Bug #726763.
Bug #726763 is assigned to gnome-settings-daemon, while #729576
occurs without it
Hi,
On 28.12.2013 02:07, Vincent Lefevre wrote:
On 2013-12-22 23:30:21 +0100, Andreas Cadhalpun wrote:
If GNOME developers want to require systemd as the init system,
I don't see this as a reason not to add the dependency. Users
are not forced to install GNOME packages. And if they want GNOME,
On Sat, Dec 28, 2013 at 07:31:46PM +0100, Andreas Cadhalpun wrote:
After that gnome-shell and gdm3 should add a recommendation for
systemd-sysv, since most people will want to use the functionality
like suspend from menus, that needs systemd as PID 1, but
occasionally some people may prefer
Hi Steve,
On 28.12.2013 20:32, Steve Langasek wrote:
On Sat, Dec 28, 2013 at 07:31:46PM +0100, Andreas Cadhalpun wrote:
After that gnome-shell and gdm3 should add a recommendation for
systemd-sysv, since most people will want to use the functionality
like suspend from menus, that needs
On Sat, Dec 28, 2013 at 08:51:58PM +0100, Andreas Cadhalpun wrote:
On 28.12.2013 20:32, Steve Langasek wrote:
On Sat, Dec 28, 2013 at 07:31:46PM +0100, Andreas Cadhalpun wrote:
After that gnome-shell and gdm3 should add a recommendation for
systemd-sysv, since most people will want to use the
On 28.12.2013 20:56, Steve Langasek wrote:
On Sat, Dec 28, 2013 at 08:51:58PM +0100, Andreas Cadhalpun wrote:
While I don't really like it, I do not know of any alternative that
exists now, but, of course, you are invited to create one.
It exists, it's called systemd-shim and it's available
On 2013-12-22 23:30:21 +0100, Andreas Cadhalpun wrote:
If GNOME developers want to require systemd as the init system,
I don't see this as a reason not to add the dependency. Users
are not forced to install GNOME packages. And if they want GNOME,
they would have to accept the consequences
On Tue, 24 Dec 2013 23:52:50 +0100
Vincent Lefevre vinc...@vinc17.net wrote:
No, the menu is refreshed since when I install or remove systemd +
libpam-systemd, then log out, I can see changes.
This is because when you log out, you create a new lightdm-gtk-greeter
process and you see the change.
On 2013-12-25 20:15:16 +0100, Pascal Dormeau wrote:
Shouldn't it run the lightdm_get_can_* () test at runtime when the
user opens the power_menu ?
When the user opens the menu would be the best, IMHO.
I do not know how to achieve this. The best I could do to remove the
gtk_widget_hide
Message resent due to delivery failure
Hi Vincent,
On Tue, 24 Dec 2013 02:01:21 +0100
Vincent Lefevre vinc...@vinc17.net wrote:
I'm wondering whether there is a race condition, making differences
between machines.
if (!lightdm_get_can_suspend ())
gtk_widget_hide (GTK_WIDGET
On 2013-12-24 16:41:41 +0100, Pascal Dormeau wrote:
Then I had a look
at /usr/share/polkit-1/actions/org.freedesktop.login1.policy
reboot and shutdown (respectively suspend and hibernate) permissions
differ inside the multiple-sessions stanza.
It is allow_active yes for shutdown
On Tue, 24 Dec 2013 18:57:32 +0100
Vincent Lefevre vinc...@vinc17.net wrote:
With D-Bus monitoring[*], I could see that there was between 1 or 3
sessions at the same time. Perhaps the user sessions were removed too
late.
[*] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732623#132
On 2013-12-24 21:23:50 +0100, Pascal Dormeau wrote:
Unless I am wrong again, I understand that lightdm-gtk-greeter creates
its power_menu once and for all when first launched and does not
refresh it after.
No, the menu is refreshed since when I install or remove systemd +
libpam-systemd, then
Control: reassign -1 lightdm 1.8.5-2
Hi Vincent,
On 22.12.2013 23:30, Andreas Cadhalpun wrote:
I just tried twm, but twm just hangs and gives many of the following
Sorry, twm does not hang, I just had no idea how minimal twm really is:
It does not show anything after login, only the
Hi Andreas,
On 2013-12-23 14:30:28 +0100, Andreas Cadhalpun wrote:
(Seriously, does anyone use twm as window manager?)
I use it to test bugs only. :)
The major difference between testing and unstable concerning this bug is
lightdm, which is 1.6.3-1 in testing, but 1.8.5-2 in unstable. So I
Hi,
this seems like yet another duplicate of Bug #726763.
For suspend-related stuff to work in recent versions of gnome, one has
to use systemd as PID 1. To do this, one can either use the boot
parameter 'init=/bin/systemd' or install the package systemd-sysv.
The strange asking for a
On 2013-12-22 16:21:15 +0100, Andreas Cadhalpun wrote:
this seems like yet another duplicate of Bug #726763.
Bug #726763 is assigned to gnome-settings-daemon, while #729576
occurs without it installed. But perhaps #726763 is assigned to
the wrong package...
If #726763 occurs with GNOME and
Control: reassign 726763 gnome-shell
Hi Vincent,
On 22.12.2013 17:38, Vincent Lefevre wrote:
Bug #726763 is assigned to gnome-settings-daemon, while #729576
occurs without it installed. But perhaps #726763 is assigned to
the wrong package...
Yeah, that is probably assigned to the wrong
On 2013-12-22 17:47:42 +0100, Andreas Cadhalpun wrote:
On 22.12.2013 17:38, Vincent Lefevre wrote:
If #726763 occurs with GNOME and without lightdm, and is the same
problem as #729576, then this could confirm that it is a systemd
bug.
This is no bug in systemd,
Sorry, I mixed up two bugs
Hi,
On 22.12.2013 20:41, Vincent Lefevre wrote:
Sorry, I mixed up two bugs related to systemd and with similar bug
number (the other one is 732623, where the installation of systemd
breaks some lightdm features).
I have lightdm installed parallel to gdm3 and just switched to lightdm.
I cannot
Hi,
On 2013-12-22 21:20:18 +0100, Andreas Cadhalpun wrote:
On 22.12.2013 20:41, Vincent Lefevre wrote:
Sorry, I mixed up two bugs related to systemd and with similar bug
number (the other one is 732623, where the installation of systemd
breaks some lightdm features).
I have lightdm installed
Hi,
On 22.12.2013 22:33, Vincent Lefevre wrote:
On 2013-12-22 21:20:18 +0100, Andreas Cadhalpun wrote:
I have lightdm installed parallel to gdm3 and just switched to lightdm.
I had the same problem with both installed.
The problem is probably, that systemd is not PID 1.
I cannot reproduce
On 2013-12-22 23:30:21 +0100, Andreas Cadhalpun wrote:
Now, without logs from systemd, it's hard to tell the cause of
the difference.
What logs would you like to see?
The result of the tests CanSuspend, CanHibernate, CanReboot and
CanPowerOff, and possibly the cause of the result when it isn't
24 matches
Mail list logo
