[Bug 1705813] [NEW] systemd upgrade to 229-4ubuntu19 fails

2017-07-22 Thread Sebastian Nohn
Public bug reported:

systemd upgrade to 229-4ubuntu19 fails:

Calculating upgrade... Done
The following packages will be upgraded:
  libmysqlclient20 libnss-myhostname libpam-systemd libsystemd0 libudev1
  mysql-client-5.7 mysql-client-core-5.7 mysql-common mysql-server
  mysql-server-5.7 mysql-server-core-5.7 systemd systemd-sysv udev
14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 23.8 MB of archives.
After this operation, 106 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
systemd-sysv amd64 229-4ubuntu19 [12.4 kB]
Get:2 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
libpam-systemd amd64 229-4ubuntu19 [115 kB]
Get:3 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
libsystemd0 amd64 229-4ubuntu19 [205 kB]
Get:4 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
libnss-myhostname amd64 229-4ubuntu19 [36.4 kB]
Get:5 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 systemd 
amd64 229-4ubuntu19 [3,811 kB]
Get:6 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 udev 
amd64 229-4ubuntu19 [992 kB]
Get:7 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 libudev1 
amd64 229-4ubuntu19 [55.0 kB]
Get:8 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-client-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [6,020 kB]
Get:9 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-common all 5.7.19-0ubuntu0.16.04.1 [15.7 kB]
Get:10 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-client-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [1,654 kB]
Get:11 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-server-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [2,463 kB]
Get:12 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-server-core-5.7 amd64 5.7.19-0ubuntu0.16.04.1 [7,588 kB]
Get:13 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
libmysqlclient20 amd64 5.7.19-0ubuntu0.16.04.1 [809 kB]
Get:14 http://mirrors.digitalocean.com/ubuntu xenial-updates/main amd64 
mysql-server all 5.7.19-0ubuntu0.16.04.1 [10.8 kB]
Fetched 23.8 MB in 0s (32.4 MB/s)   
Preconfiguring packages ...
(Reading database ... 112119 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_229-4ubuntu19_amd64.deb ...
Unpacking systemd-sysv (229-4ubuntu19) over (229-4ubuntu17) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up systemd-sysv (229-4ubuntu19) ...
(Reading database ... 112119 files and directories currently installed.)
Preparing to unpack .../libpam-systemd_229-4ubuntu19_amd64.deb ...
Unpacking libpam-systemd:amd64 (229-4ubuntu19) over (229-4ubuntu17) ...
Preparing to unpack .../libsystemd0_229-4ubuntu19_amd64.deb ...
Unpacking libsystemd0:amd64 (229-4ubuntu19) over (229-4ubuntu17) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Setting up libsystemd0:amd64 (229-4ubuntu19) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
(Reading database ... 112119 files and directories currently installed.)
Preparing to unpack .../libnss-myhostname_229-4ubuntu19_amd64.deb ...
Unpacking libnss-myhostname:amd64 (229-4ubuntu19) over (229-4ubuntu17) ...
Preparing to unpack .../systemd_229-4ubuntu19_amd64.deb ...
Unpacking systemd (229-4ubuntu19) over (229-4ubuntu17) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
Processing triggers for ureadahead (0.100.0-19) ...
Setting up systemd (229-4ubuntu19) ...
addgroup: The group `systemd-journal' already exists as a system group. Exiting.

Broadcast message from systemd-journ...@web01.fra.de.nohn.net (Sat
2017-07-22 09:07:52 UTC):

systemd[1]: Freezing execution.

Failed to try-restart systemd-networkd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
See system logs and 'systemctl status systemd-networkd.service' for details.

Failed to try-restart systemd-resolved.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
See system logs and 'systemctl status systemd-resolved.service' for details.
Failed to try-restart systemd-timesyncd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out
See system logs and 'systemctl status systemd-timesyncd.service' for details.
Failed to retrieve unit: Failed to activate service 'org.freedesktop.systemd1': 
timed out
(Reading database ... 112121 files and directories currently installed.)
Preparing to unpack .../udev_229-4ubuntu19_amd64.deb ...
Unpacking udev (229-4ubuntu19) over (229-4ubuntu17) ...
Failed to execute operation: Failed to activate service 
'org.freedesktop.systemd1': timed out
Preparing to unpack .../libudev1_229-4ubuntu19_amd64.deb ...
Unpacking libudev1:amd64 (229-4ubuntu19) over (229-4ubuntu17) 

[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04

2016-11-21 Thread Sebastian Nohn
As a workaround, add

blacklist acpi_als

to

/etc/modprobe.d/blacklist.conf

>From what I read, this auto brightness "feature" sucks anyway, so this
may be the best whether you are affected by this bug or not.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1584457

Title:
  gsd-backlight-helper spamming the logs since upate to 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1584457] Re: gsd-backlight-helper spamming the logs since upate to 16.04

2016-11-21 Thread Sebastian Nohn
Does not look like this is fixed. I just upgraded from 14.04 to 16.04.1
and my syslog gets spammed with

Nov 21 14:36:09 bnasws02 gnome-session[1536]: Error executing command as 
another user: Not authorized
Nov 21 14:36:09 bnasws02 gnome-session[1536]: This incident has been reported.
Nov 21 14:36:10 bnasws02 gnome-session[1536]: Error executing command as 
another user: Not authorized
Nov 21 14:36:10 bnasws02 gnome-session[1536]: This incident has been reported.
Nov 21 14:36:22 bnasws02 gnome-session[1536]: Error executing command as 
another user: Not authorized
Nov 21 14:36:22 bnasws02 gnome-session[1536]: This incident has been reported.
Nov 21 14:36:23 bnasws02 gnome-session[1536]: Error executing command as 
another user: Not authorized
Nov 21 14:36:23 bnasws02 gnome-session[1536]: This incident has been reported.
Nov 21 14:36:31 bnasws02 gnome-session[1536]: Error executing command as 
another user: Not authorized
Nov 21 14:36:31 bnasws02 gnome-session[1536]: This incident has been reported.

my auth.log with:

Nov 21 14:36:43 bnasws02 pkexec[24666]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]
Nov 21 14:36:43 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for 
user root by (uid=1000)
Nov 21 14:36:43 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create 
session: Already running in a session
Nov 21 14:36:43 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot 
determine display-device
Nov 21 14:36:43 bnasws02 pkexec[24667]: sebastian: Executing command 
[USER=root] [TTY=unknown] [CWD=/home/sebastian] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]
Nov 21 14:36:47 bnasws02 pkexec[24675]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]
Nov 21 14:36:47 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for 
user root by (uid=1000)
Nov 21 14:36:47 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create 
session: Already running in a session
Nov 21 14:36:47 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot 
determine display-device
Nov 21 14:36:47 bnasws02 pkexec[24676]: sebastian: Executing command 
[USER=root] [TTY=unknown] [CWD=/home/sebastian] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]
Nov 21 14:36:50 bnasws02 pkexec[24685]: gdm: Error executing command as another 
user: Not authorized [USER=root] [TTY=unknown] [CWD=/var/lib/gdm3] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]
Nov 21 14:36:50 bnasws02 pkexec: pam_unix(polkit-1:session): session opened for 
user root by (uid=1000)
Nov 21 14:36:50 bnasws02 pkexec: pam_systemd(polkit-1:session): Cannot create 
session: Already running in a session
Nov 21 14:36:50 bnasws02 pkexec: pam_ck_connector(polkit-1:session): cannot 
determine display-device
Nov 21 14:36:50 bnasws02 pkexec[24686]: sebastian: Executing command 
[USER=root] [TTY=unknown] [CWD=/home/sebastian] 
[COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 
927]


** Changed in: gnome-settings-daemon (Ubuntu Xenial)
   Status: Triaged => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1584457

Title:
  gsd-backlight-helper spamming the logs since upate to 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1584457/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1559924] [NEW] systemd kills rsyslog as one of the first jobs, preventing logging of the other jobs shutting down

2016-03-21 Thread Sebastian Nohn
Public bug reported:

systemd kills rsyslog as one of the first jobs. So after that no other
jobs are logging that they are shutting down and what they are doing
during shutdown.

The default should be shutting down logging at the latest possible point
in time when shutting down a machine.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1559924

Title:
  systemd kills rsyslog as one of the first jobs, preventing logging of
  the other jobs shutting down

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1559924/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 90075] Re: cannot configure wireless access with static IP and WPA encryption using network-manager-gnome

2007-04-09 Thread Sebastian Nohn
I can configure WPA in roaming mode without any problem (Atheros
Communications, Inc. AR5212 802.11abg NIC (rev 01)), but in static
configuration, WPA isn't even offered. Instead, I can only configure
WEP.

-- 
cannot configure wireless access with static IP and WPA encryption using 
network-manager-gnome
https://bugs.launchpad.net/bugs/90075
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs