[Touch-packages] [Bug 2012119] Re: imageinfo fails in Ubuntu 23.04 with a "no such file or directory" error
Downgrading popt from 1.19+dfsg-1 to 1.18-3build1 shows that the problem is not in imageinfo but in popt. ** Package changed: imageinfo (Ubuntu) => popt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to popt in Ubuntu. https://bugs.launchpad.net/bugs/2012119 Title: imageinfo fails in Ubuntu 23.04 with a "no such file or directory" error Status in popt package in Ubuntu: New Bug description: imageinfo fails in Ubuntu 23.04 with a "no such file or directory" error, eg: $ imageinfo --size /usr/share/backgrounds/Lunar-lobster-side_by_Gixo-dark.png imageinfo: unable to open image `��s��U': No such file or directory @ error/blob.c/OpenBlob/2924. $ imageinfo --size /usr/share/backgrounds/Copper_Mountain_by_Eduardo_Battaglia.jpg imageinfo: unable to open image `�=�V': No such file or directory @ error/blob.c/OpenBlob/2924. The filename it complains is not found seems to be random and changes each time. Under WSL, it fails but just says "unable to open image `': No such file", ie it doesn't show the random text. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: imageinfo 0.04-0ubuntu12 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 18 16:31:02 2023 InstallationDate: Installed on 2021-09-28 (536 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210924) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: imageinfo UpgradeStatus: Upgraded to lunar on 2023-03-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/popt/+bug/2012119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
systemd 246.6-1ubuntu1 and apport 2.20.11-0ubuntu48 fix this issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: Fix Released Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I'm still seeing this bug with apport 2.20.11-0ubuntu48 and systemd 246.5-1ubuntu1. Do we need systemd 246.6 before it is fixed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Fix Released Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Fix Released Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'.
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Also, if you want to reduce the massive size of the journal logs that this bug creates, do something like this: sudo journalctl --rotate sudo journalctl --vacuum-size=100M That second command reduces it to 100 MB, but you can specify larger or smaller sizes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Trying again... After reading the linked systemd bug report, I changed /usr/lib/systemd/system/apport-autoreport.path from having PathExistsGlob to PathChangedGlob and ran sudo systemctl daemon-reload, and this seemed to fix the problem: [Unit] Description=Process error reports when automatic reporting is enabled (file watch) ConditionPathExists=/var/lib/apport/autoreport [Path] PathChangedGlob=/var/crash/*.crash [Install] WantedBy=paths.target Now journalctl -e shows: Sep 23 18:00:35 xps15 whoopsie-upload-all[12306]: /var/crash/_opt_wine-devel_bin_wine-preloader.1000.cr> Sep 23 18:00:35 xps15 whoopsie-upload-all[12306]: All reports processed Sep 23 18:00:35 xps15 systemd[1]: apport-autoreport.service: Succeeded. Sep 23 18:00:35 xps15 systemd[1]: Finished Process error reports when automatic reporting is enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I changed [Path] PathChangedGlob=/var/crash/*.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: In Progress Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
Doesn't systemd normally stop trying to start a service if it fails too often? That's clearly not happening here, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in apport source package in Groovy: Confirmed Status in systemd source package in Groovy: New Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17
[Touch-packages] [Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I ran into this and applied the workaround of deleting all the files in /var/crash to stop the journalctl spam and 100% CPU usage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' Status in apport package in Ubuntu: Confirmed Bug description: after upgrade from Ubuntu 20.04 to 20.10 seeing systemd use 100% cpu forever top top - 10:16:19 up 20 min, 1 user, load average: 3.91, 4.28, 3.39 Tasks: 332 total, 2 running, 330 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.7 us, 6.4 sy, 11.9 ni, 62.2 id, 0.0 wa, 0.0 hi, 0.8 si, 0.0 st MiB Mem : 15917.6 total, 8553.4 free, 2604.3 used, 4759.9 buff/cache MiB Swap: 2048.0 total, 2048.0 free, 0.0 used. 12633.7 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 177316 12252 8684 R 100.0 0.1 15:01.25 systemd 4636 kush 39 19 633796 176152 16360 S 98.3 1.1 17:51.56 tracker-miner-f 820 message+ 20 0 10740 6452 4212 S 39.8 0.0 6:19.06 dbus-daemon 316 root 19 -1 535916 322896 320824 S 15.3 2.0 3:16.41 systemd-journal 844 syslog20 0 221136 5840 3920 S 13.6 0.0 2:14.52 rsyslogd 858 root 20 0 83708 74124 7568 S 12.7 0.5 2:06.98 systemd-logind 5 root 20 0 0 0 0 I 3.4 0.0 0:05.01 kworker/0:0-events 35566 kush 20 0 3850088 588344 262192 S 2.5 3.6 0:30.48 MainThread 5626 kush 20 0 5004788 260876 93400 S 1.7 1.6 3:05.19 gnome-shell 7033 kush 20 0 869792 66440 44272 S 1.7 0.4 0:06.05 gnome-terminal- 36790 kush 20 0 2525432 156636 98568 S 1.7 1.0 0:04.99 Web Content 957 root 20 0 1556196 45044 24284 S 0.8 0.3 0:02.48 containerd 1038 root 20 0 10460 4412 3300 S 0.8 0.0 0:00.16 fancontrol sudo tail -n 100 /var/log/syslog Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Start request repeated too quickly. Aug 14 10:14:17 lhotse systemd[1]: apport-autoreport.service: Failed with result 'start-limit-hit'. Aug 14 10:14:17 lhotse systemd[1]: Failed to start Process error reports when automatic reporting is enabled. Aug 14 10:14:17 lhotse systemd[1]:
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
My Ubuntu 20.04 installation just did this - something changed the org.gnome.desktop.lockdown disable-lock-screen to true and also the blank screen to never (did an update do this?). But there's nothing I can see in gnome-control-center to modify this value, making this bug pretty obscure when it happens. Wouldn't a setting in g-c-c make a lot of sense if you can actually disable the screen lock completely? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308169] Re: apport-bug on .crash file for a stable release doesn't notify crash was sent
This is still present in 19.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1308169 Title: apport-bug on .crash file for a stable release doesn't notify crash was sent Status in apport package in Ubuntu: Triaged Bug description: When giving apport-bug a .crash file and telling it to send the report, it writes an empty .upload file, but does not appear to send the report: ryan@feh:~$ sudo apport-bug /var/crash/_usr_lib_squid3_pinger.0.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (63.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ryan@feh:~$ ls -lsa /var/crash/_usr_lib_squid3_pinger.0.* 64 -rw-r- 1 root root 63854 Apr 15 10:33 /var/crash/_usr_lib_squid3_pinger.0.crash 0 -rw-r--r-- 1 root root 0 Apr 15 10:44 /var/crash/_usr_lib_squid3_pinger.0.upload ryan@feh:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportLog: ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: called for pid 10115, signal 11, core limit 0 ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: executable: /usr/lib/squid3/pinger (command line "(pinger)") ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: wrote report /var/crash/_usr_lib_squid3_pinger.0.crash ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CrashReports: 640:0:0:16086:2014-04-12 19:58:08.832940604 -0700:2014-04-13 03:55:12.546230475 -0700:/var/crash/_usr_lib_mailman_bin_list_lists.0.crash 640:0:0:63854:2014-04-15 10:33:06.036259174 -0700:2014-04-15 10:36:21.278098132 -0700:/var/crash/_usr_lib_squid3_pinger.0.crash 644:0:0:0:2014-04-15 10:36:23.354031253 -0700:2014-04-15 10:36:23.354031253 -0700:/var/crash/_usr_lib_squid3_pinger.0.upload 640:33:33:982302:2014-04-12 19:47:16.481460672 -0700:2014-04-13 03:55:12.478232672 -0700:/var/crash/_usr_bin_php5.33.crash 640:0:0:42350107:2014-04-15 05:24:07.978228219 -0700:2014-04-15 05:23:28.267508485 -0700:/var/crash/_usr_sbin_apache2.0.crash Date: Tue Apr 15 10:40:38 2014 InstallationDate: Installed on 2012-04-17 (728 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 (20120415) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-04-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1308169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819132] Re: DNS is broken after reboot or suspend
Marking as fix released because it looks like this was resolved by this morning's update (by a reconfiguration of systemd? dpkg.log says that it installed version 240-6ubuntu2, but it also says that this version has been installed since the 13th of March). /etc/resolv.conf now contains "nameserver 127.0.0.53". ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: Fix Released Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819132] Re: DNS is broken after reboot or suspend
The problem seems to occur because the wireless network connects before my user logs in. If I do a reboot and login cycle with the wireless router turned off, when I turn it back on and the computer connects, /run/resolvconf/resolv.conf is updated correctly with the DNS nameserver information, as expected. Note that whether or not DNS is working properly, systemd-resolve --status indicates that systemd-resolved has the correct information - it says "Current DNS Server: 10.1.1.1" - the problem is just that nobody updates the resolv.conf file unless a user is logged in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1819132 Title: DNS is broken after reboot or suspend Status in systemd package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819132] [NEW] DNS is broken after reboot or suspend
Public bug reported: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog: nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connectedfull limited /org/freedesktop/NetworkManager/Devices/2 whisky5 1 b76ae48f-93bb-4e57-8f1e-aac201b9dacb /org/freedesktop/NetworkManager/ActiveConnection/1 enx00e04c68026f ethernet unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.15.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1819132 Title: DNS is broken after reboot or suspend Status in network-manager package in Ubuntu: New Bug description: Relatively recently, after I reboot Ubuntu 19.04, the wireless network connects but DNS is not working. This is because the /etc/resolv.conf file, which is a symlink to ../run/resolvconf/resolv.conf, has no nameserver entries: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. Either turning the wireless card off and on again or running "sudo systemctl restart systemd-resolved" fixes the problem. This is also a problem after resuming from suspend - either the resolv.conf file has no nameservers, or the previous nameservers are still in it and appear before the new ones (so DNS queries time out). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu2 Uname: Linux 5.0.0-05-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 17:30:17 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-08-16 (569 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.1.1.1 dev wlp2s0 proto dhcp metric 600 10.1.1.0/24 dev wlp2s0 proto kernel scope link src 10.1.1.3 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-01-15 (51 days ago) WifiSyslog:
[Touch-packages] [Bug 1812161] Re: Screen backlight control does not work in Disco on Dell XPS 9560
Oops, it was either acpi_osi=! or acpi_osi='Windows 2009' that was causing the problem. I had copied them in to try and get the nvidia card working after resume, but it turns out they aren't needed for the nvidia card to work anyway. Sorry for the noise. ** Changed in: upower (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Invalid Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812161] [NEW] Screen backlight control does not work in Disco on Dell XPS 9560
Public bug reported: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64: installed bbswitch, 0.8, 4.20.0-042000-generic, x86_64: installed bbswitch, 0.8, 4.20.3-042003-generic, x86_64: installed nvidia, 415.27, 4.20.0-042000-generic, x86_64: installed nvidia, 415.27, 4.20.3-042003-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be] InstallationDate: Installed on 2017-08-16 (518 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Dell Inc. XPS 15 9560 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-13-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 i915.modeset=1 nouveau.runpm=0 rcutree.rcu_idle_gp_delay=1 acpi_osi=! "acpi_osi=Windows 2009" SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-01-15 (1 days ago) dmi.bios.date: 10/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.product.sku: 07BE dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+19.04.20190103-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco gnome-shell regression reproducible third-party-packages ubuntu ** Tags added: gnome-shell -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1812161 Title: Screen backlight control does not work in Disco on Dell XPS 9560 Status in xorg package in Ubuntu: New Bug description: When I press the screen backlight up/down buttons, gnome-shell pops up the backlight control window saying that the backlight is being adjusted, but the actual screen brightness does not change. The problem is that gnome is adjusting /sys/class/backlight/acpi_video0/brightness instead of /sys/class/backlight/intel_backlight/brightness. If I manually change the latter as root with, say: root@xps-9560:~ echo 600 > /sys/class/backlight/intel_backlight/brightness then the brightness changes. The brightness control worked fine in Cosmic on this laptop, so this is a regression. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 17 14:47:37 2019 DistUpgraded: 2019-01-15 23:10:12,938 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.18.0-13-generic, x86_64:
[Touch-packages] [Bug 869341] Re: "Online Accounts" icon and UI appears in g-c-c when gnome-online-accounts package is not installed, ignoring user's registration input.
It's still an issue in Ubuntu 18.04 and 18.10. g-c-c should really prompt the user to install gnome-online-accounts if it is not installed instead of pretending to work and then failing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/869341 Title: "Online Accounts" icon and UI appears in g-c-c when gnome-online- accounts package is not installed, ignoring user's registration input. Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Invalid Bug description: On all my Oneiric boxes I have registered my Google account via the GNOME Control Center (from the command line), via the "Online Accounts" panel. I selected this panel, clicked the "+" under the empty account list, chose "Google" (the only choice) for the account and the Google login screen appeared in the dialog. I entered my e-mail address and password, left "Stay signed in" marked and clicked "Sign in". After that I clicked on the button to grant access and the dialog disappeared without the account getting added. Instead, in the terminal I get this output: -- till@eee-pc:~$ gnome-control-center & [1] 15744 till@eee-pc:~$ Gtk-Message: Failed to load module "gnomesegvhandler" (gnome-control-center:15744): GLib-GIO-CRITICAL **: g_dbus_proxy_call_internal: assertion `G_IS_DBUS_PROXY (proxy)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/869341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
I had this problem, too. journalctl -b|grep glamor showed this: /usr/lib/gdm3/gdm-x-session[2205]: (EE) modeset(0): glamor initialization failed which is why gnome-shell was falling back to llvmpipe. However, there was some funny business going on with my libGL installation, because ldd /usr/bin/glxinfo showed: libGL.so.1 => /usr/local/lib/libGL.so.1 (0x7fe67e633000) libGLX.so.0 => /usr/local/lib/libGLX.so.0 (0x7fe67dccd000) libGLdispatch.so.0 => /usr/local/lib/libGLdispatch.so.0 (0x7fe67da16000) meaning I must have manually built and installed versions of libGL/X at some point. I deleted the libGL/X libraries and the xorg folder from /usr/local/lib and after a reboot I now have intel mesa graphics again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767468] Re: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration
@Brian: just FYI, the /etc/X11/Xsession.d/50_check_unity_support file is actually checking for ubuntu, not xubuntu: if [ "x$DESKTOP_SESSION" = "xubuntu" ] will be true if $DESKTOP_SESSION is "ubuntu", because it's prepending "x" to $DESKTOP_SESSION. My unity_support_check was failing (it returns 1) so LIBGL_ALWAYS_SOFTWARE was being set to one. However, after I removed the /etc/X11/Xsession.d/50_check_unity_support file and reboot, LIBGL_ALWAYS_SOFTWARE is not set but I still get a llvm_pipe session. This bug looks a lot like #1752938, which is about losing hardware acceleration but without removing unity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1767468 Title: Upgrade from 16.04 to 18.04, then uninstalling unity disables hardware acceleration Status in nux package in Ubuntu: Confirmed Bug description: After upgrading from 16.04 to 18.04 on a very plain Intel Skylake graphics, hardware acceleration is gone. Glxinfo and System Information report 'llvmpipe' (software rasterizer) It is caused by the file /etc/X11/Xsession.d/50_check_unity_support which can be deleted and then this problem goes away. > 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglvnd0 1.0.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 27 20:24:48 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-21 (735 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libglvnd UpgradeStatus: Upgraded to bionic on 2018-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1767468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748095] Re: Non-root user can reboot machine from the command line
I sometimes need to reboot a server that I'm logged into. In this case, I got the wrong gnome-terminal tab by mistake and rebooted my laptop instead, losing all my current work, which was an extremely suboptimal outcome. I checked rebooting from another user when my first user logged in, and it didn't let me do it - it told me the command to try, however, which did require authentication. (Rebooting from the system menu didn't work at all, it just silently failed, but that's another matter.) I agree typing reboot into a terminal is not something that desktop users typically do - in which case, why support it? Or at least why not make the user confirm it's what they actually want before rebooting? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748095 Title: Non-root user can reboot machine from the command line Status in systemd package in Ubuntu: Opinion Bug description: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? Note that you can't reboot a server if you are logged in via ssh as a non-root user: Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748095] Re: Non-root user can reboot machine from the command line
Doesn't the shutdown icon warn you if there are other users logged in who might lose work? So shouldn't the reboot command do the same thing if you are not root? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748095 Title: Non-root user can reboot machine from the command line Status in systemd package in Ubuntu: Opinion Bug description: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? Note that you can't reboot a server if you are logged in via ssh as a non-root user: Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748095] Re: Non-root user can reboot machine from the command line
(And pulling the power cord on my laptop doesn't reboot or even shutdown the computer, so I don't think it's a good comparison. Holding the power button down for ten seconds is a better comparison, but it's still not a good one because reboot acts immediately, not after you confirm it by typing it in ten times or something.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1748095 Title: Non-root user can reboot machine from the command line Status in systemd package in Ubuntu: Opinion Bug description: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? Note that you can't reboot a server if you are logged in via ssh as a non-root user: Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a
Thanks, removing the packages makes the errors go away. Do you think the error message is misleading? Instead of saying "Failed to start AppArmor initialization", perhaps it should say, "Failed to load some profiles"? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1756800 Title: Failed to start AppArmor initialization with status=123/n/a Status in apparmor package in Ubuntu: Won't Fix Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: AppArmor in Ubuntu 18.04 fails to start every time: $ systemctl status apparmor.service ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 773 (code=exited, status=123) Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail! Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'. Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization. journalctl -xe gives essentially the same lack of information issued after a systemctl restart apparmor.service. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apparmor 2.11.0-2ubuntu19 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 13:50:42 2018 InstallationDate: Installed on 2017-08-16 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1 SourcePackage: apparmor Syslog: Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus mediation is enabled Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] AppArmor D-Bus mediation is enabled Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-24T16:47:24.395996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a
I get this: $ sudo apparmor_parser --replace /etc/apparmor.d/usr.bin.webbrowser-app AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/graphics.d' $ sudo apparmor_parser --replace /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor at line 14: Could not open '/usr/share/apparmor/hardware/audio.d' FWIW, I don't actually have a /usr/share/apparmor folder. Would these errors prevent apparmor from running at all? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1756800 Title: Failed to start AppArmor initialization with status=123/n/a Status in apparmor package in Ubuntu: New Bug description: AppArmor in Ubuntu 18.04 fails to start every time: $ systemctl status apparmor.service ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 773 (code=exited, status=123) Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail! Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'. Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization. journalctl -xe gives essentially the same lack of information issued after a systemctl restart apparmor.service. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apparmor 2.11.0-2ubuntu19 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 13:50:42 2018 InstallationDate: Installed on 2017-08-16 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1 SourcePackage: apparmor Syslog: Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus mediation is enabled Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] AppArmor D-Bus mediation is enabled Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-24T16:47:24.395996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756800] Re: Failed to start AppArmor initialization with status=123/n/a
Another user reported what sounds like the same issue at https://ubuntuforums.org/showthread.php?t=2386129=13749658#post13749658 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1756800 Title: Failed to start AppArmor initialization with status=123/n/a Status in apparmor package in Ubuntu: New Bug description: AppArmor in Ubuntu 18.04 fails to start every time: $ systemctl status apparmor.service ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 773 (code=exited, status=123) Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail! Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'. Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization. journalctl -xe gives essentially the same lack of information issued after a systemctl restart apparmor.service. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apparmor 2.11.0-2ubuntu19 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 13:50:42 2018 InstallationDate: Installed on 2017-08-16 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1 SourcePackage: apparmor Syslog: Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus mediation is enabled Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] AppArmor D-Bus mediation is enabled Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-24T16:47:24.395996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1756800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1756800] [NEW] Failed to start AppArmor initialization with status=123/n/a
Public bug reported: AppArmor in Ubuntu 18.04 fails to start every time: $ systemctl status apparmor.service ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 773 (code=exited, status=123) Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail! Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'. Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization. journalctl -xe gives essentially the same lack of information issued after a systemctl restart apparmor.service. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apparmor 2.11.0-2ubuntu19 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Mon Mar 19 13:50:42 2018 InstallationDate: Installed on 2017-08-16 (214 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-12-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=1 SourcePackage: apparmor Syslog: Mar 19 13:47:22 xps15-9560 dbus-daemon[1252]: [system] AppArmor D-Bus mediation is enabled Mar 19 13:47:23 xps15-9560 dbus-daemon[1491]: [session uid=125 pid=1491] AppArmor D-Bus mediation is enabled Mar 19 13:47:39 xps15-9560 dbus-daemon[2160]: [session uid=1001 pid=2160] AppArmor D-Bus mediation is enabled UpgradeStatus: Upgraded to bionic on 2017-11-17 (121 days ago) mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-24T16:47:24.395996 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1756800 Title: Failed to start AppArmor initialization with status=123/n/a Status in apparmor package in Ubuntu: New Bug description: AppArmor in Ubuntu 18.04 fails to start every time: $ systemctl status apparmor.service ● apparmor.service - AppArmor initialization Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2018-03-19 13:47:22 AWST; 56s ago Docs: man:apparmor(7) http://wiki.apparmor.net/ Process: 773 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Main PID: 773 (code=exited, status=123) Mar 19 13:47:21 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:21 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.web Mar 19 13:47:22 xps15-9560 apparmor[773]: AppArmor parser error for /etc/apparmor.d/usr.lib.mediascanner-2.0.mediascanner-extractor in /e Mar 19 13:47:22 xps15-9560 apparmor[773]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 19 13:47:22 xps15-9560 apparmor[773]:...fail! Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Main process exited, code=exited, status=123/n/a Mar 19 13:47:22 xps15-9560 systemd[1]: apparmor.service: Failed with result 'exit-code'. Mar 19 13:47:22 xps15-9560 systemd[1]: Failed to start AppArmor initialization. journalctl -xe gives essentially the same lack of information issued
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
@Maarten: Maybe spotify will install and work from its flatpak? It's the second flatpak app listed here: https://www.omgubuntu.co.uk/2017/07/7 -flatpak-apps-can-install-right-now-flathub -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
FWIW, I got opera-stable and viber to install with libcurl4 by extracting their debs, manually editing their control file to say libcurl3|libcurl4, recreating the deb using the "ar -r" command, and then using dpkg -i to reinstall. They run fine but of course I haven't been able to test all their functionality. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
@Brian Murray: I think that it is incorrect to mark this bug as invalid - at the very least it should be kept as confirmed against the 18.04 release notes so they can include a warning against upgrading to Ubuntu 18.04 because it may not be compatible with a number of popular third- party applications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748095] [NEW] Non-root user can reboot machine from the command line
Public bug reported: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? Note that you can't reboot a server if you are logged in via ssh as a non-root user: Failed to set wall message, ignoring: Interactive authentication required. Failed to reboot system via logind: Interactive authentication required. Failed to open /dev/initctl: Permission denied Failed to talk to init daemon. I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=dd72d916-58fc-49a1-9798-feded5ce6eff ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Open a gnome-terminal as your normal user and type 'reboot' and ENTER. The PC reboots immediately, losing all unsaved work for all users (this is the case on both my VM and laptop running Ubuntu 18.04, so I don't think it's a weird configuration issue). In the old days, didn't you have to be root (or sudoed) for this command - to work? I guess it means that potentially a non-root user can reboot a - server he is logged into, as well? + to work? While we're on the subject, wouldn't it be nicer if the reboot command (ie when run as root) asked you to confirm before executing, pointing out that all unsaved work for all users will be lost? - I am assuming this is a systemd issue, because reboot just links to - systemctl, and systemctl can be executed by non-root users: + Note that you can't reboot a server if you are logged in via ssh as a + non-root user: - $ ll /sbin/reboot /bin/systemctl + Failed to set wall message, ignoring: Interactive authentication required. + Failed to reboot system via logind: Interactive authentication required. + Failed to open /dev/initctl: Permission denied + Failed to talk to init daemon. + + + I am assuming this is a systemd issue, because reboot just links to systemctl, and systemctl can be executed by non-root users: + + $ ll /sbin/reboot /bin/systemctl -rwxr-xr-x 1 root root 182352 Dec 12 21:25 /bin/systemctl* lrwxrwxrwx 1 root root 14 Dec 12 21:25 /sbin/reboot -> /bin/systemctl* ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 8 12:49:33 2018 InstallationDate: Installed on 2017-12-18 (51 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171212) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus
[Touch-packages] [Bug 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
If it helps anyone, I've got 4.14-rc5 and apparmor working. I've posted a patch at the duplicate bug https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1724450. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724450] [NEW] apparmor is broken for kernel 4.14
Public bug reported: Several critical systems are broken with the default Ubuntu 17.10 apparmor profile when booting in kernel 4.14, eg DHCP/networking and mysql-server. I got it working by applying the attached patch from the /etc directory. The patch is mostly based on the patch provided in comment #34 in the upstream bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=877581. I had to remove the sections for the files that Ubuntu doesn't have (such as tor, tor.browser, haveged and libvirt) and to get DHCP to work, I also had to add 'w' permission to /usr/lib/NetworkManager/nm-dhcp-helper to avoid this syslog message: apparmor="DENIED" operation="create" profile="/usr/lib/NetworkManager /nm-dhcp-helper" pid=3876 comm="nm-dhcp-helper" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 4.14.0-rc5-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:59:38 2017 InstallationDate: Installed on 2017-08-16 (62 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-rc5-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7 SourcePackage: apparmor UpgradeStatus: Upgraded to artful on 2017-08-17 (62 days ago) modified.conffile..etc.apparmor.d.abstractions.nameservice: [modified] mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-18T12:17:08.648386 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Patch added: "apparmor-for-4.14.diff" https://bugs.launchpad.net/bugs/1724450/+attachment/4974449/+files/apparmor-for-4.14.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1724450 Title: apparmor is broken for kernel 4.14 Status in apparmor package in Ubuntu: New Bug description: Several critical systems are broken with the default Ubuntu 17.10 apparmor profile when booting in kernel 4.14, eg DHCP/networking and mysql-server. I got it working by applying the attached patch from the /etc directory. The patch is mostly based on the patch provided in comment #34 in the upstream bug at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=877581. I had to remove the sections for the files that Ubuntu doesn't have (such as tor, tor.browser, haveged and libvirt) and to get DHCP to work, I also had to add 'w' permission to /usr/lib/NetworkManager/nm-dhcp-helper to avoid this syslog message: apparmor="DENIED" operation="create" profile="/usr/lib/NetworkManager /nm-dhcp-helper" pid=3876 comm="nm-dhcp-helper" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apparmor 2.11.0-2ubuntu17 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 4.14.0-rc5-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 18 12:59:38 2017 InstallationDate: Installed on 2017-08-16 (62 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcKernelCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-rc5-generic root=UUID=0eb64261-6dff-464a-8373-596794c1fafe ro rootflags=subvol=@ quiet splash acpi_rev_override=5 scsi_mod.use_blk_mq=1 vt.handoff=7 SourcePackage: apparmor UpgradeStatus: Upgraded to artful on 2017-08-17 (62 days ago) modified.conffile..etc.apparmor.d.abstractions.nameservice: [modified] mtime.conffile..etc.apparmor.d.abstractions.nameservice: 2017-10-18T12:17:08.648386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1724450/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
I also have this issue in Ubuntu 17.10 (running gdm/gnome-shell). Uninstalling dbus-user-session isn't really an option, because tons of apps depend on it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Confirmed Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend
I have noticed that doing a "sudo service network-manager restart"
usually fixes things, but not always and not for everything. For
instance, on my laptop at the moment firefox can't find any webpages
("Server not found"), but Chrome is working fine; ntpd is complaining
twice a minute in the log that it can't find 0.ubuntu.pool.ntp.org etc,
even though "nslookup 0.ubuntu.pool.ntp.org" gives a valid address;
"ping google.com" says "Name or service not known", even though
"nslookup google.com" returns a valid address. "dig google.com" is
working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1631241
Title:
Name resolution stops working after resume from suspend
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
suspend DNS resolution stops working.
After resuming, systemd-resolved is running and libnss-resolve is
installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
name server. The dnsmasq-base package is installed since it is pulled
in by both network-manager and lxc1, and both NM and libvirt have
spawned instances of dnsmasq:
> 1155 pts/2S+ 0:00 grep dnsmasq
> 2724 ?S 0:00 dnsmasq -u lxc-dnsmasq --strict-order
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override
--except-interface=lo --interface=lxcbr0
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
> 2992 ?S 0:00 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
> 2993 ?S 0:00 /usr/sbin/dnsmasq
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
> 22879 ?S 0:00 /usr/sbin/dnsmasq --no-resolv
--keep-in-foreground --no-hosts --bind-interfaces
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1
--cache-size=0 --conf-file=/dev/null --proxy-dnssec
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq
--conf-dir=/etc/NetworkManager/dnsmasq.d
Let me know if you need any extra info.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libnss-resolve 231-9git1
ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
Uname: Linux 4.8.0-17-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Oct 7 13:52:40 2016
InstallationDate: Installed on 2015-07-22 (443 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64
(20150422)
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1631241/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626935] Re: [yakkety] desktop is black and/or flickering after plugging in a second monitor
Is this a modesetting driver issue? I believe I've seen this happen when hotplugging an external monitor. It only happens for me with the modeset driver, though, not the intel driver. The modesetting driver is excellent for some things (eg it doesn't tear on the external monitor like the intel driver does), but it does struggle a bit when changing resolutions and screen layouts (eg every time I log in, it completely unnecessarily changes my laptop screen resolution from 1920x1080 to 640x480 and then back again to 1920x1080). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1626935 Title: [yakkety] desktop is black and/or flickering after plugging in a second monitor Status in compiz package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Confirmed Bug description: Using 16.04 daily image: 20160919(downloading date) With testing package for 4.8 kernel: ppa:canonical-kernel-team/unstable Graphic chips: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] [10de:139b] (rev ff) Desktop wallpaper on extended display shows black background only, and the hdmi detection is very unstable. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Sep 23 05:30:30 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-09-20 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-14-generic.efi.signed root=UUID=d16ac6eb-1b3e-4aa5-813b-57b5c7ef165a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1626935/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618423] Re: Modesetting driver cannot handle different display resolutions for two monitors
No, the issue didn't occur in Xenial, which defaults to the intel driver. (The intel driver doesn't have these issues.) Just to be clear - it is possible that the issue is resolved with the later BIOS, but I won't know until I can test the known bad configuration again. (Unfortunately, I can't use the later BIOS full- time thanks to the brightness issue.) In general, the modesetting driver works fine (and it doesn't tear on the external display when scrolling, unlike the intel driver, which is nice). Modesetting does struggle a bit when changing resolutions, and X slows down for a while after the resolution changes. It usually speeds back up within say 10 seconds, but sometimes the slowdown persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors Status in xorg package in Ubuntu: Incomplete Bug description: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of the desktop, except for the unity launcher and unity top bar. Anything that leaves the top quarter leaves trails and flickers awfully (see attached image, which shows everything except the flickering). I also tried it with the laptop on 2560x1440 (I had to add it manually because of a a separate bug where the modesetting driver limits the max vertical refresh frequency of default modelines to 60 Hz) and exactly the same thing happens (although the geometry isn't one quarter any more). It works fine with the intel driver, but not the modesetting driver, so it seems to be an xserver issue rather than a unity issue. It also works fine if I set both monitors to 1920x1080. The modesetting driver seems to struggle with setting resolutions. When I first log into the desktop, it takes a good 5 seconds longer than the intel driver to set up the screens, and for a while it looks like I have a 640x480 screen (judging by the huge mouse pointer I get). Given this bug and the vertical refresh bug, maybe yakkety shouldn't default to the modesetting driver? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 30 19:26:06 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-9136-generic, x86_64: installed bbswitch, 0.8, 4.7.2-040702-generic, x86_64: installed nvidia, 367-367.44, 4.4.0-9136-generic, x86_64: installed nvidia, 367-367.44, 4.7.2-040702-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.7.2-040702-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-07-24 (36 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
[Touch-packages] [Bug 1618423] Re: Modesetting driver cannot handle different display resolutions for two monitors
The output of those commands are: 1.2.13 and 08/08/2016. I can't test the same configuration that I originally tested for another week, but on another 1680x1050 monitor it did work, eventually. I had to restart lightdm several times because things happened like the mouse click no longer working, once when I changed the resolution it flipped everything sideways, and the mouse started moving extraordinarily slowly and the desktop was unusable. My issue is that there's a more severe bug with the brightness control after resume in the newer BIOS and its predecessor, so I can't use it (see http://en.community.dell.com/techcenter/os- applications/f/4613/p/19985875/20927410#20927410). Dell's official response is that they are aware of it, but they clearly aren't fixing it since they have released a second BIOS with the same bug. If it's purely a BIOS issue, why does the modeset driver have this screen resolution problem and not the intel driver? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors Status in xorg package in Ubuntu: Incomplete Bug description: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of the desktop, except for the unity launcher and unity top bar. Anything that leaves the top quarter leaves trails and flickers awfully (see attached image, which shows everything except the flickering). I also tried it with the laptop on 2560x1440 (I had to add it manually because of a a separate bug where the modesetting driver limits the max vertical refresh frequency of default modelines to 60 Hz) and exactly the same thing happens (although the geometry isn't one quarter any more). It works fine with the intel driver, but not the modesetting driver, so it seems to be an xserver issue rather than a unity issue. It also works fine if I set both monitors to 1920x1080. The modesetting driver seems to struggle with setting resolutions. When I first log into the desktop, it takes a good 5 seconds longer than the intel driver to set up the screens, and for a while it looks like I have a 640x480 screen (judging by the huge mouse pointer I get). Given this bug and the vertical refresh bug, maybe yakkety shouldn't default to the modesetting driver? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 30 19:26:06 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-9136-generic, x86_64: installed bbswitch, 0.8, 4.7.2-040702-generic, x86_64: installed nvidia, 367-367.44, 4.4.0-9136-generic, x86_64: installed nvidia, 367-367.44, 4.7.2-040702-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.7.2-040702-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-07-24 (36 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1 version.ia32-libs:
[Touch-packages] [Bug 1618423] [NEW] Modesetting driver cannot handle different display resolutions for two monitors
Public bug reported: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of the desktop, except for the unity launcher and unity top bar. Anything that leaves the top quarter leaves trails and flickers awfully (see attached image, which shows everything except the flickering). I also tried it with the laptop on 2560x1440 (I had to add it manually because of a a separate bug where the modesetting driver limits the max vertical refresh frequency of default modelines to 60 Hz) and exactly the same thing happens (although the geometry isn't one quarter any more). It works fine with the intel driver, but not the modesetting driver, so it seems to be an xserver issue rather than a unity issue. It also works fine if I set both monitors to 1920x1080. The modesetting driver seems to struggle with setting resolutions. When I first log into the desktop, it takes a good 5 seconds longer than the intel driver to set up the screens, and for a while it looks like I have a 640x480 screen (judging by the huge mouse pointer I get). Given this bug and the vertical refresh bug, maybe yakkety shouldn't default to the modesetting driver? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg 1:7.7+13ubuntu3 Uname: Linux 4.7.2-040702-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 30 19:26:06 2016 DistUpgraded: 2016-07-25 02:38:44,004 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-9136-generic, x86_64: installed bbswitch, 0.8, 4.7.2-040702-generic, x86_64: installed nvidia, 367-367.44, 4.4.0-9136-generic, x86_64: installed nvidia, 367-367.44, 4.7.2-040702-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 530 [1028:06e4] InstallationDate: Installed on 2016-07-04 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.7.2-040702-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-07-24 (36 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 reproducible ubuntu yakkety ** Attachment added: "hires with modesetting.png" https://bugs.launchpad.net/bugs/1618423/+attachment/4730766/+files/hires%20with%20modesetting.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1618423 Title: Modesetting driver cannot handle different display resolutions for two monitors Status in xorg package in Ubuntu: New Bug description: I have an external 1920x1080 monitor attached to my laptop, which has a 3840x2160 display. When I run them both at their native resolutions, the laptop display only works in the top quarter of
[Touch-packages] [Bug 1574020] Re: Can't use networkmanager from lightdm
Another use case for allowing connections from lightdm is where Ubuntu won't boot into a desktop (it happens!) and you want to switch to a tty console and access the internet (eg to run upgrades) but you have no ethernet card. In this case it's a huge pain if you can't connect to the wireless network from lightdm. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574020 Title: Can't use networkmanager from lightdm Status in NetworkManager: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615184] Re: systemd update breaks screen lock, dpms, startup programs
Ok, so after today's updates dpms and screen lock are now working with systemd 231-4, so marking as fixed again. ** Changed in: systemd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615184 Title: systemd update breaks screen lock, dpms, startup programs Status in systemd package in Ubuntu: Fix Released Status in systemd package in Debian: Fix Released Bug description: This morning's updates broke both the screen lock (it never auto-locks now) and dpms (if you manually lock the screen, it doesn't turn off any more). "xset dpms force off" still works to turn the screen off and "gnome- screensaver-command -l" still locks the screen, so it probably isn't gnome-screensaver's fault. Is it a lightdm issue perhaps? Which app is in charge of this? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:22:54 2016 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 60 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615184] Re: systemd update breaks screen lock, dpms, startup programs
I've confirmed that the screen lock also does not come on in a VM running yakkety with systemd 231-4. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615184 Title: systemd update breaks screen lock, dpms, startup programs Status in systemd package in Ubuntu: New Status in systemd package in Debian: Fix Released Bug description: This morning's updates broke both the screen lock (it never auto-locks now) and dpms (if you manually lock the screen, it doesn't turn off any more). "xset dpms force off" still works to turn the screen off and "gnome- screensaver-command -l" still locks the screen, so it probably isn't gnome-screensaver's fault. Is it a lightdm issue perhaps? Which app is in charge of this? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:22:54 2016 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 60 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615184] Re: systemd update breaks screen lock, dpms, startup programs
Reading the associated Debian bug (http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=834367), it's a different one from this bug. That bugs refers to issues after running systemctl daemon-reexec (which happens when systemd is upgraded) caused by keypresses being sent to a tty console as well as to the X session, and the workaround is to reboot. This bug occurs with the latest systemd installed even after a reboot, and is not related to the systemd upgrade process. I have certainly seen all those issues when systemd is upgraded (usually one of my monitors turns off, even though it is set to be on; I have seen the keypresses echoed to a tty console; I have had the system reboot on CTRL-ALT-DEL even though I was in an X-session; and I have seen it switch to tty consoles unexpectedly from an X-session). So just to be clear: _this_ bug occurs after any number of reboots with systemd 231-4 installed. It does not occur with systemd 231-1 installed. It does not appear to be related to http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=834367. (Really, I would not have reported a bug if I knew there was an upgraded version of the relevant package available.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615184 Title: systemd update breaks screen lock, dpms, startup programs Status in systemd package in Ubuntu: New Status in systemd package in Debian: Fix Released Bug description: This morning's updates broke both the screen lock (it never auto-locks now) and dpms (if you manually lock the screen, it doesn't turn off any more). "xset dpms force off" still works to turn the screen off and "gnome- screensaver-command -l" still locks the screen, so it probably isn't gnome-screensaver's fault. Is it a lightdm issue perhaps? Which app is in charge of this? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:22:54 2016 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 60 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615184] Re: systemd update breaks screen lock, dpms, startup programs
No, that's *exactly* what I did. I upgraded from 231-1 to 231-4 and rebooted and things broke. I did it three times just to be sure. ** Changed in: systemd (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615184 Title: systemd update breaks screen lock, dpms, startup programs Status in systemd package in Ubuntu: New Status in systemd package in Debian: Fix Released Bug description: This morning's updates broke both the screen lock (it never auto-locks now) and dpms (if you manually lock the screen, it doesn't turn off any more). "xset dpms force off" still works to turn the screen off and "gnome- screensaver-command -l" still locks the screen, so it probably isn't gnome-screensaver's fault. Is it a lightdm issue perhaps? Which app is in charge of this? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:22:54 2016 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 60 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615184] Re: screen lock and dpms broken in yakkety
Luckily I had a snapshot from earlier. Bisecting upgrades shows that the problem is in one of these packages: libpam-systemd/yakkety 231-4 amd64 [upgradable from: 231-1] libsystemd-dev/yakkety 231-4 amd64 [upgradable from: 231-1] libsystemd0/yakkety 231-4 amd64 [upgradable from: 231-1] systemd/yakkety 231-4 amd64 [upgradable from: 231-1] systemd-sysv/yakkety 231-4 amd64 [upgradable from: 231-1] With these packages installed, I have: * Screen lock/dpms is broken * A lot of startup programs don't run (weather indicator, nm-applet, tomboy notes, system load indicator, for instance) * I get a black screen background at startup (until I run nautilus manually). ** Package changed: gnome-screensaver (Ubuntu) => systemd (Ubuntu) ** Summary changed: - screen lock and dpms broken in yakkety + systemd update breaks screen lock, dpms, startup programs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615184 Title: systemd update breaks screen lock, dpms, startup programs Status in systemd package in Ubuntu: New Bug description: This morning's updates broke both the screen lock (it never auto-locks now) and dpms (if you manually lock the screen, it doesn't turn off any more). "xset dpms force off" still works to turn the screen off and "gnome- screensaver-command -l" still locks the screen, so it probably isn't gnome-screensaver's fault. Is it a lightdm issue perhaps? Which app is in charge of this? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-screensaver 3.6.1-7ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:22:54 2016 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 60 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1615184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615185] [NEW] ubuntu does not remove folders for mounted drives in /media on reboot
Public bug reported: Whenever I reboot, if there are drivers mounted with corresponding folders in /media (whether internal or external, btfrs, ntfs, or ext4), after the reboot the original folder is still present and the drives re- mount in a new folder. (Note that I mount drives in /media instead of /media/ so that all users can access them, in case this is relevant.) eg if there was a file mounted in /media/drive, after reboot there is an empty folder /media/drive and a new one /media/drive1 with the drive mounted in it. A subsequent reboot means there will be /media/drive, /media/drive1, and /media/drive2, and so on until I manually remove the old folders. I'm guessing that the issue is that systemd is not unmounting the drives properly on reboot since is a problem in Ubuntu 16.04 as well as yakkety. It's unlikely to be a lack-of-time issue since sometimes on reboot systemd will wait for 90 seconds or more for the cryptfs swap to unmount before giving up. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:27:37 2016 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-9134-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1615185 Title: ubuntu does not remove folders for mounted drives in /media on reboot Status in systemd package in Ubuntu: New Bug description: Whenever I reboot, if there are drivers mounted with corresponding folders in /media (whether internal or external, btfrs, ntfs, or ext4), after the reboot the original folder is still present and the drives re-mount in a new folder. (Note that I mount drives in /media instead of /media/ so that all users can access them, in case this is relevant.) eg if there was a file mounted in /media/drive, after reboot there is an empty folder /media/drive and a new one /media/drive1 with the drive mounted in it. A subsequent reboot means there will be /media/drive, /media/drive1, and /media/drive2, and so on until I manually remove the old folders. I'm guessing that the issue is that systemd is not unmounting the drives properly on reboot since is a problem in Ubuntu 16.04 as well as yakkety. It's unlikely to be a lack-of-time issue since sometimes on reboot systemd will wait for 90 seconds or more for the cryptfs swap to unmount before giving up. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-4 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Sat Aug 20 12:27:37 2016 InstallationDate: Installed on 2016-07-04 (46 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: Dell Inc. XPS 15 9550 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-9134-generic root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ quiet splash nogpumanager vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-07-24 (26 days ago) dmi.bios.date: 04/07/2016
[Touch-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Alt-F8 triggers resizing windows in compiz/Unity as well! That's good to know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in Decorator for compiz-fusion: New Status in One Hundred Papercuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Ubuntu MATE: Opinion Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in light-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Confirmed Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268146] Re: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe)
@madbiologist: thanks for looking into it. I haven't upgraded to the A12 BIOS because the list of fixes and enhancements was very small and only mentioned it was a fix for some issues when upgrading to Windows 8. (Additionally, Dell doesn't provide a way to update the BIOS from Linux for this machine so upgrading it is a PITA.) FWIW, compiz works fine on this machine after I did a complete reinstall of 14.04, so it was some issue with the upgrade process that I ran into, and that seems to be a common theme here. Perhaps the upgrade inadvertently left an old intel driver in place (eg with an invalid ABI) and so the system rejected it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1268146 Title: Very high cpu usage for compiz in 14.04 (mesa incorrectly using llvmpipe) Status in mesa package in Ubuntu: Confirmed Bug description: I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz. Strangely, glxinfo reports this, which is totally incorrect - I'm running on Intel Sandy Bridge HD3000 graphics and VMware isn't even installed on this PC: OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 256 bits) OpenGL version string: 2.1 Mesa 10.0.1 So I guess that compiz might be using lots of cpu because it's using llvmpipe as the renderer. So is this a mesa bug? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-1.16-generic 3.13.0-rc7 Uname: Linux 3.13.0-1-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Jan 11 22:27:28 2014 DistUpgraded: 2014-01-11 12:30:22,360 ERROR SystemError from cache.commit(): installArchives() failed DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:050e] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev ff) (prog-if ff) InstallationDate: Installed on 2012-08-25 (504 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-1-generic root=UUID=67083065-b92e-4596-a218-817c1dfc8ae7 ro quiet splash intel_pstate=enable crashkernel=384M-:128M vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-11 (0 days ago) dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Sat Jan 11 22:20:55 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41063 vendor DEL xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407192] Re: firefox icon frequently replaced by placeholder
Seems to be fixed for me now - at least, the geeqie icon is shown correctly now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: Fix Committed Status in Unity: Invalid Status in bamf package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for firefox in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407192] Re: firefox icon frequently replaced by placeholder
geeqie still displays the placeholder icon with bamfdaemon 0.5.1+14.10.20140925-0ubuntu2, though, so I suspect it isn't fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for firefox in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407192] Re: firefox icon frequently replaced by placeholder
And I just had my permanently-locked firefox icon in the launcher replaced with the placeholder, so it's definitely not fixed in that version of bamf. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for firefox in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407192] Re: firefox icon frequently replaced by placeholder
I find the launchbar always displays the grey question mark icon for geeqie so long as it's not already locked to the launchbar. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1407192 Title: firefox icon frequently replaced by placeholder Status in BAMF Application Matching Framework: In Progress Status in Unity: Invalid Status in bamf package in Ubuntu: In Progress Status in unity package in Ubuntu: Invalid Bug description: Several times over the last week I have noticed that the when I start firefox, the default icon is replaced by a grey square with a question mark in the center as shown in the attached image. The only fix I've found is to unlock firefox from the launcher, quit the program, search for firefox in the dash, manually drag the icon onto the launcher, and then open it(i.e. if I start firefox directly from the dash, the grey icon appears on the launcher again). I haven't noticed this occurring with any other program. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 2 21:38:32 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fb43] InstallationDate: Installed on 2014-12-11 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141210) MachineType: TOSHIBA Satellite L875D ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.30 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: PLCSC8 dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.30:bd12/06/2012:svnTOSHIBA:pnSatelliteL875D:pvrPSKFQU-003034:rvnAMD:rnPLCSC8:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L875D dmi.product.version: PSKFQU-003034 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 1 20:07:44 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1407192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1407556] Re: Wrong Qt backend used in desktop session (xcb vs. Mir)
Is there anything I can try? All I did was install it and try it, so it ran with the default settings. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1407556 Title: Wrong Qt backend used in desktop session (xcb vs. Mir) Status in unity8 package in Ubuntu: Incomplete Status in unity8-desktop-session package in Ubuntu: New Bug description: I installed unity8-desktop-session-mir in my vmplayer vivid guest and tried logging into it, got only a black screen, and found a unity8 crash file in the /var/crash afterwards. I also almost always (9 out of 10 times) get a black screen if I try to log into a ubuntu-desktop-mir session, and if I do manage to get a normal screen with ubuntu-desktop-mir, resizing it gives me the black screen. So this might be related to a bug in mir. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity8 8.02+15.04.20141216.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 Date: Mon Jan 5 11:03:29 2015 ExecutablePath: /usr/bin/unity8 ExecutableTimestamp: 1418728702 InstallationDate: Installed on 2015-01-03 (1 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141220) ProcCmdline: unity8 ProcCwd: /home/rocko ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity8 StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so QPlatformIntegrationFactory::create(QString const, QStringList const, int, char**, QString const) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: unity8 crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.unity8.log: () QXcbConnection: Could not connect to display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1407556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308169] Re: apport-bug on .crash file does not send report
I ran into this issue in the unstable Vivid release, and I had to comment out the 'problem_types': ['Bug', 'Package'], line in /etc/apport/crashdb.conf to get apport-bug working again. https://help.ubuntu.com/community/ReportingBugs suggests that you only need to do this for stable releases, though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1308169 Title: apport-bug on .crash file does not send report Status in apport package in Ubuntu: Confirmed Bug description: When giving apport-bug a .crash file and telling it to send the report, it writes an empty .upload file, but does not appear to send the report: ryan@feh:~$ sudo apport-bug /var/crash/_usr_lib_squid3_pinger.0.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (63.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ryan@feh:~$ ls -lsa /var/crash/_usr_lib_squid3_pinger.0.* 64 -rw-r- 1 root root 63854 Apr 15 10:33 /var/crash/_usr_lib_squid3_pinger.0.crash 0 -rw-r--r-- 1 root root 0 Apr 15 10:44 /var/crash/_usr_lib_squid3_pinger.0.upload ryan@feh:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportLog: ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: called for pid 10115, signal 11, core limit 0 ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: executable: /usr/lib/squid3/pinger (command line (pinger)) ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: wrote report /var/crash/_usr_lib_squid3_pinger.0.crash ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CrashReports: 640:0:0:16086:2014-04-12 19:58:08.832940604 -0700:2014-04-13 03:55:12.546230475 -0700:/var/crash/_usr_lib_mailman_bin_list_lists.0.crash 640:0:0:63854:2014-04-15 10:33:06.036259174 -0700:2014-04-15 10:36:21.278098132 -0700:/var/crash/_usr_lib_squid3_pinger.0.crash 644:0:0:0:2014-04-15 10:36:23.354031253 -0700:2014-04-15 10:36:23.354031253 -0700:/var/crash/_usr_lib_squid3_pinger.0.upload 640:33:33:982302:2014-04-12 19:47:16.481460672 -0700:2014-04-13 03:55:12.478232672 -0700:/var/crash/_usr_bin_php5.33.crash 640:0:0:42350107:2014-04-15 05:24:07.978228219 -0700:2014-04-15 05:23:28.267508485 -0700:/var/crash/_usr_sbin_apache2.0.crash Date: Tue Apr 15 10:40:38 2014 InstallationDate: Installed on 2012-04-17 (728 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Beta amd64 (20120415) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-04-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1308169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366805] Re: Can't log in to Unity8 in VirtualBox; Mir crashes with std::exception::what: Error opening DRM device
*** This bug is a duplicate of bug 1118903 *** https://bugs.launchpad.net/bugs/1118903 Actually, I don't think this should be a duplicate of #1118903. Why should we be forced to use (dreadfully slow) software rendering for unity8 in a VM when we don't need to do so for unity7? Wouldn't it be better to fix mir so it can use vboxdrv's DRM capabilties? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1366805 Title: Can't log in to Unity8 in VirtualBox; Mir crashes with std::exception::what: Error opening DRM device Status in Mir: New Status in mir package in Ubuntu: Confirmed Bug description: When I try to login to Unity Next the system-compositor seems to crash immediately. I'm using Ubuntu Next on VirtualBox. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-desktop-mir (not installed) ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Mon Sep 8 15:10:15 2014 GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-07-09 (61 days ago) InstallationMedia: Ubuntu-Desktop-Next 14.10 Utopic Unicorn - Alpha amd64 (20140708) SourcePackage: unity-system-compositor SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UnitySystemCompositorLog: Warning: ignoring unrecognised arguments: ERROR: /build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptrmir::udev::Context) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Error opening DRM device 123, No medium found UnitySystemCompositorLogOld: Warning: ignoring unrecognised arguments: ERROR: /build/buildd/mir-0.7.0+14.10.20140829/src/platform/graphics/mesa/display_helpers.cpp(242): Throw in function int mir::graphics::mesa::helpers::DRMHelper::open_drm_device(const std::shared_ptrmir::udev::Context) Dynamic exception type: N5boost16exception_detail10clone_implINS0_19error_info_injectorISt13runtime_error std::exception::what: Error opening DRM device 123, No medium found UpgradeStatus: No upgrade log present (probably fresh install) version.libdrm: libdrm2 2.4.56-1 version.lightdm: lightdm 1.11.8-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1366805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1284981] Re: Locally-integrated menus stop working in Virtualbox and Transmission
This bug is still present in the latest Ubuntu 14.10 as of 2014-12-29. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1284981 Title: Locally-integrated menus stop working in Virtualbox and Transmission Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: With (the absolutely awesome) locally-integrated menus enabled, if you open the VirtualBox the menus initially work as expected, ie they appear in VirtualBox's titlebar when you hover the mouse over it. But if you open a popup window by clicking on New or Settings and then close it, it the menus no longer appear when you hover over the titlebar. One workaround is that the menus start working again if you focus on another application's window and then click on VirtualBox again so it regains focus, so it's as if the popup window has retained the focus for LIM even once it is closed. Also worth noting is that if you open a VirtualBox popup window and focus on another application without closing the VirtualBox popup window, when you go back to the popup window and close it, the menus work as expected. I tried reproducing this using the popup windows in Synaptic, gnome- disks, and gnome-terminal, but they all work fine. I'm running virtualbox-4.3 4.3.8-92456~Ubuntu~raring. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5 Uname: Linux 3.13.0-13-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Feb 26 13:31:49 2014 InstallationDate: Installed on 2014-02-08 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1284981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397483] Re: Unity restores windows to random workspaces on system resume
I just suspended a second time before restoring one of the windows to the primary workspace, and when I resumed it was neither on the primary nor the secondary workspace. I disabled workspaces and it reappeared on the primary one. My guess is that unity restored the window to its workspace+1 each time so it went to workspace 3 after the second resume. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1397483 Title: Unity restores windows to random workspaces on system resume Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc6-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 29 10:35:31 2014 InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1397483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 949606] Re: 64 bit dev packages should include 32 bit .so library file
** This bug is no longer a duplicate of bug 1246013 Would be nice for libgl1-mesa-dev to be multiarched -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/949606 Title: 64 bit dev packages should include 32 bit .so library file Status in mesa package in Ubuntu: Triaged Bug description: 64 bit dev packages contain a 64 bit version of the library file(s) that they provide for linking but not a 32 bit version of the library file(s). In previous versions of Ubuntu, however, it was possible to compile 32 bit applications using the 64 bit dev packages in by installing ia32-libs, which contained the required 32 bit library files. In the move to multiarch, 32 bit library files are being removed from ia32-libs. Multiarch (I assume) aims to keep the architectures separate, so the generally intended solution is to install the i386 version of the dev package when compiling 32 bit applications, ie side-by-side with the 64 bit dev package. However, some 64 bit development packages conflict with their 32 bit equivalent. This creates a regressive situation where it is impossible to install them side-by-side - you are forced to either install the 32 bit package, which breaks 64 bit compilations, or the 64 bit package, which breaks 32 bit compilations. An example is libglu1-mesa-dev, which conflicts with libglu1-mesa- dev:i386. The libglu1-mesa-dev file contains all the necessary development files for 32 bit *except* for the 32 bit library file. It does contain the 64 bit library file. Since the library file is part of the development files, libglu1-mesa-dev does not contain all the necessary development files for 32 bit, ie it does not contain all the necessary development files for multiarch. I think that it *should* contain all the necessary files for building multarch applications. The two workarounds are: 1. Manually re-install the required i386 dev packages before compiling 32 bit apps, and then manually re-install the required amd64 dev packages before compiling 64 bit apps. This is a real pain. 2. Install the i386 binary package (eg libglu1-mesa:i386) and the amd64 dev package (eg libglu1-mesa-dev), and manually create symlinks for the i386 libXYZ.so package (eg sudo ln -s /usr/lib/i386-linux- gnu/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so). This is a more permanent solution but is a real pain to set up, as you have to find each missing library manually, and some library files, like mesa/libGL.so.1, are in subfolders. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libglu1-mesa-dev 8.0.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,grid,resize,compiztoolbox,vpswitch,place,gnomecompat,move,regex,animation,imgpng,snap,mousepoll,session,expo,workarounds,wall,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Thu Mar 8 10:20:54 2012 DistUpgraded: Log time: 2012-02-26 08:25:08.500725 DistroCodename: precise DistroVariant: ubuntu DkmsStatus: virtualbox-guest, 4.1.8, 3.2.0-12-generic, x86_64: installed virtualbox-guest, 4.1.8, 3.2.0-14-generic, x86_64: installed virtualbox-guest, 4.1.8, 3.2.0-17-generic, x86_64: installed virtualbox-guest, 4.1.8, 3.2.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=630a9f76-6f8f-43be-bb99-6be721c9deaf ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: mesa UpgradeStatus: Upgraded to precise on 2012-02-26 (11 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx
[Touch-packages] [Bug 1397483] [NEW] Unity restores windows to random workspaces on system resume
Public bug reported: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc6-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 29 10:35:31 2014 InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Description changed: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. + IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc6-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 29 10:35:31 2014 InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: - LANGUAGE=en_AU:en - TERM=xterm - PATH=(custom, no user) - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + TERM=xterm + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1397483 Title: Unity restores windows to random workspaces on system resume Status in unity package in Ubuntu: New Bug description: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1
[Touch-packages] [Bug 1377537] [NEW] Screen does not lock or turn off automatically
Public bug reported: In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn off after the designated time in System Settings / Brightness and Lock. The screen lock can still be activated manually from the System menu or keyboard shortcut (although I notice that the default has changed from CTRL-ALT-DEL to Super-L, and if I change this back in the System Settings / Keyboard / Shortcuts, both combinations work - it seems that the unity plugin in compiz (CCSM / unity / general) has aother screen lock key short cut). Other users are reporting the same issue: see http://ubuntuforums.org/showthread.php?t=2246601highlight=turn. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-rc7-git-20140929.1829 x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 5 08:07:30 2014 InstallationDate: Installed on 2014-02-08 (238 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-04 (0 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1377537 Title: Screen does not lock or turn off automatically Status in “unity” package in Ubuntu: New Bug description: In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn off after the designated time in System Settings / Brightness and Lock. The screen lock can still be activated manually from the System menu or keyboard shortcut (although I notice that the default has changed from CTRL-ALT-DEL to Super-L, and if I change this back in the System Settings / Keyboard / Shortcuts, both combinations work - it seems that the unity plugin in compiz (CCSM / unity / general) has aother screen lock key short cut). Other users are reporting the same issue: see http://ubuntuforums.org/showthread.php?t=2246601highlight=turn. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-rc7-git-20140929.1829 x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 5 08:07:30 2014 InstallationDate: Installed on 2014-02-08 (238 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 814833] Re: Opening the dash is very slow and laggy
+1 for what Guillaume F said in comment #45. Sometimes the dash takes so long to populate that it tells me Sorry, there is nothing that matches your search, even though I know there are matches. And at random times it resets the search filters to include Files and Folders - I turn this off as soon as it happens, as it is too slow to complete searching when this is turned on. Is that relevant to this bug, though, or is this bug only about the intial delay in drawing the dash? I only find it is very slow to draw the dash if the system runs out of RAM and starts swapping to disk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/814833 Title: Opening the dash is very slow and laggy Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: When I was running off a usb drive at least, opening of the app/files dash lagged a second or two behind the actual clicking of the logo button. Just a minor thing, but was hard to ignore it To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/814833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
