[Touch-packages] [Bug 1926658] Re: initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share/initramfs-tools/init not being executable
Fixed in 0.140ubuntu2. ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1926658 Title: initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share /initramfs-tools/init not being executable Status in initramfs-tools package in Ubuntu: Fix Released Bug description: After updating the initramfs-tools 0.140ubuntu1, the system no longer boots. Instead, the busybox shell is started. The error says that "/init" cannot be started due to error -13. In investigated and figured out that the error occurs because the /usr/share/initramfs-tools/init script is not executable. It was executable in previous initramfs-tools versions. "chmod +x"ing it and rebuilding the initramfs works around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1926658/+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 1926658] [NEW] initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share/initramfs-tools/init not being executable
Public bug reported: After updating the initramfs-tools 0.140ubuntu1, the system no longer boots. Instead, the busybox shell is started. The error says that "/init" cannot be started due to error -13. In investigated and figured out that the error occurs because the /usr/share/initramfs-tools/init script is not executable. It was executable in previous initramfs-tools versions. "chmod +x"ing it and rebuilding the initramfs works around the problem. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1926658 Title: initramfs-tools 0.140ubuntu1 causes failure to boot due to /usr/share /initramfs-tools/init not being executable Status in initramfs-tools package in Ubuntu: New Bug description: After updating the initramfs-tools 0.140ubuntu1, the system no longer boots. Instead, the busybox shell is started. The error says that "/init" cannot be started due to error -13. In investigated and figured out that the error occurs because the /usr/share/initramfs-tools/init script is not executable. It was executable in previous initramfs-tools versions. "chmod +x"ing it and rebuilding the initramfs works around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1926658/+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 1742750] [NEW] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file
Public bug reported: Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-connect.patch, which changes line 38 of /etc/pulse/default.pa to read ".endif### Load audio drivers statically". It appears that there are a couple of line feeds missing here, and having the comment on the same line as the endif causes pulseaudio not to start. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1742750 Title: Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file Status in pulseaudio package in Ubuntu: New Bug description: Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on- connect.patch, which changes line 38 of /etc/pulse/default.pa to read ".endif### Load audio drivers statically". It appears that there are a couple of line feeds missing here, and having the comment on the same line as the endif causes pulseaudio not to start. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1543546] Re: Monitor DPI settings are ignored after upgrade to Xenial
michael@mamarley-desktop:~$ DISPLAY=:0 xdpyinfo | grep dimensions dimensions:7680x2160 pixels (1060x301 millimeters) michael@mamarley-desktop:~$ DISPLAY=:0 xdpyinfo | grep resolution resolution:184x182 dots per inch michael@mamarley-desktop:~$ I should also mention that this bug now only happens for applications running as root, such as Synaptic. Applications run as the normal user display at the correct size now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1543546 Title: Monitor DPI settings are ignored after upgrade to Xenial Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24" 4K) from Wily to Xenial. Before I did this, applications using all the toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value automatically detected from the monitor, causing them to automatically scale to a usable size. However, after upgrading to Xenial, GTK3 applications no longer have this behavior. Instead, they appear at the normal 96DPI size, causing them to be nearly unreadable due to the small size of their widgets. I am currently using GTK3 3.18.7-1ubuntu2, but the issue has been occurring since I upgraded to Xenial months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1543546/+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 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
Thanks, with this version of plasma-integration Quassel and VLC do not crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
I do have it installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
That environment variable is empty. I did upgrade appmenu-qt5; the installed version is 0.3.0+16.10.20160628.1-0ubuntu2~2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: Incomplete Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
VLC crashes every time you try to start it too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: New Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1620870] Re: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
Specifically, the "libqt5widgets5" package seems to be at fault. If I revert only this package to the previous version Quassel works properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: New Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1620870] [NEW] After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start
Public bug reported: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620870 Title: After updating to qtbase-opensource-src 5.6.1+dfsg-3ubuntu3~3, Quassel crashes every time on start Status in qtbase-opensource-src package in Ubuntu: New Bug description: Reverting to the previous version fixes the problem. Here is the stacktrace from the crash: #0 0x in ?? () #1 0x73896c5e in copyActionToPlatformItem (action=action@entry=0x55d65820, item=item@entry=0x55e24380, itemsMenu=0x55ede310) at widgets/qmenu.cpp:3228 #2 0x73896861 in QMenuPrivate::syncPlatformMenu (this=0x55e0a680) at widgets/qmenu.cpp:202 #3 0x73896977 in QMenu::setPlatformMenu (this=this@entry=0x55f40df0, platformMenu=) at widgets/qmenu.cpp:3425 #4 0x73a85a15 in QSystemTrayIconPrivate::addPlatformMenu (this=0x55ef0260, menu=0x55f40df0) at util/qsystemtrayicon.cpp:761 #5 0x73a85af2 in QSystemTrayIconPrivate::updateMenu_sys_qpa (this=0x55ef0260) at util/qsystemtrayicon.cpp:710 #6 0x73aa395f in QSystemTrayIconPrivate::updateMenu_sys (this=) at util/qsystemtrayicon_x11.cpp:312 #7 0x73a85033 in QSystemTrayIcon::setContextMenu (this=, menu=) at util/qsystemtrayicon.cpp:171 #8 0x556b6d22 in LegacySystemTray::init (this=this@entry=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/legacysystemtray.cpp:62 #9 0x556dea93 in StatusNotifierItem::init (this=0x5603ba30) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/statusnotifieritem.cpp:110 #10 0x556c0db3 in MainWin::setupSystray (this=this@entry=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:1014 #11 0x556c10a2 in MainWin::init (this=0x55d40e40) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/mainwin.cpp:221 #12 0x556c52f4 in QtUi::init (this=0x55cc4340) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtui.cpp:81 #13 0x5566d45d in QtUiApplication::init (this=0x7fffdd20) at /build/quassel-R1VeAR/quassel-0.12.4/src/qtui/qtuiapplication.cpp:162 #14 0x5566aa4c in main (argc=1, argv=0x7fffde88) at /build/quassel-R1VeAR/quassel-0.12.4/src/common/main.cpp:210 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620870/+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 1558331] Re: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-party repositories become unusable with "The repository is insufficiently signed by key (weak diges
I know that the PPAs need new keys, but it is not obvious how to do that. After extensive searching, I still cannot figure out how to do that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1558331 Title: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third- party repositories become unusable with "The repository is insufficiently signed by key (weak digest)" Status in apt package in Ubuntu: Confirmed Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1558331] Re: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-party repositories become unusable with "The repository is insufficiently signed by key (weak diges
Hmm, it looks like the combination of the warnings and errors may be especially confusing. I have several PPAs and the Google Chrome repository on my system. The PPAs have the packages themselves signed with SHA256, but the GPG key is only SHA1. These repositories should work, but display an error message after an "aptitude update". The packages in the Chrome repository are signed only with SHA1, so those won't work at all, producing an error message. However, Synaptic displays all the warnings and errors together and says that it is an Error, which tricked me into thinking that none of the repositories would work. Obviously, the PPAs need to be updated to use a stronger key. I can't see any way to do this manually though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1558331 Title: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third- party repositories become unusable with "The repository is insufficiently signed by key (weak digest)" Status in apt package in Ubuntu: Confirmed Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1558331] [NEW] After upgrading to apt 1.2.7 in Xenial, PPAs and most other third-party repositories become unusable with "The repository is insufficiently signed by key (weak dig
Public bug reported: The title pretty much says it all. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1558331 Title: After upgrading to apt 1.2.7 in Xenial, PPAs and most other third- party repositories become unusable with "The repository is insufficiently signed by key (weak digest)" Status in apt package in Ubuntu: New Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1543546] [NEW] Monitor DPI settings are ignored after upgrade to Xenial
Public bug reported: I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24" 4K) from Wily to Xenial. Before I did this, applications using all the toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value automatically detected from the monitor, causing them to automatically scale to a usable size. However, after upgrading to Xenial, GTK3 applications no longer have this behavior. Instead, they appear at the normal 96DPI size, causing them to be nearly unreadable due to the small size of their widgets. I am currently using GTK3 3.18.7-1ubuntu2, but the issue has been occurring since I upgraded to Xenial months ago. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1543546 Title: Monitor DPI settings are ignored after upgrade to Xenial Status in gtk+3.0 package in Ubuntu: New Bug description: I recently upgraded my Kubuntu x86_64 system with a HiDPI monitor (24" 4K) from Wily to Xenial. Before I did this, applications using all the toolkits (GTK2, GTK3, Qt4, and Qt5) properly obeyed the DPI value automatically detected from the monitor, causing them to automatically scale to a usable size. However, after upgrading to Xenial, GTK3 applications no longer have this behavior. Instead, they appear at the normal 96DPI size, causing them to be nearly unreadable due to the small size of their widgets. I am currently using GTK3 3.18.7-1ubuntu2, but the issue has been occurring since I upgraded to Xenial months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1543546/+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 1460345] [NEW] network-manager can cause a continuous IPv6 router solicitation loop
Public bug reported: As described in the upstream bug report https://bugzilla.redhat.com/show_bug.cgi?id=1207730, network-manager can cause a continuous IPv6 router solicitation loop. In my specific case, a large number of computers running network-manager are on the network. The resulting storm of traffic overloads the router and knocks computers not running network-manager off of IPv6. Could the fix please be backported? Thanks! ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1460345 Title: network-manager can cause a continuous IPv6 router solicitation loop Status in network-manager package in Ubuntu: New Bug description: As described in the upstream bug report https://bugzilla.redhat.com/show_bug.cgi?id=1207730, network-manager can cause a continuous IPv6 router solicitation loop. In my specific case, a large number of computers running network-manager are on the network. The resulting storm of traffic overloads the router and knocks computers not running network-manager off of IPv6. Could the fix please be backported? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460345/+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 1432158] Re: NM-wait-online makes my system take about twice as long to boot to the login screen
Hmm, it seems to not be doing it anymore. I guess an update sometime between when I filed the bug and now fixed the problem. (I had NetworkManager-wait-online disabled since I don't need its functionality, so I wouldn't have noticed.) Sorry for the trouble. ** Changed in: systemd (Ubuntu) Status: Incomplete = 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/1432158 Title: NM-wait-online makes my system take about twice as long to boot to the login screen Status in systemd package in Ubuntu: Fix Released Bug description: The enablement of NetworkManager-wait-online.service in network- manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly twice as long to boot to the login screen. I did some investigating and determined that this is because sddm.service depends on systemd-user-sessions.service which depends on remote-fs.target which depends on network-online.target which depends on NetworkManager-wait-online.service. For that reason, systemd is apparently waiting to start sddm until both the wired and wireless adapters are connected, which makes the system take much longer to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432158/+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 1434020] Re: With systemd 219-4ubuntu6, ifup fails on startup
219-4ubuntu7 fixes the problem. Thanks! ** 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/1434020 Title: With systemd 219-4ubuntu6, ifup fails on startup Status in systemd package in Ubuntu: Fix Released Bug description: After updating to systemd 219-4ubuntu6, the ifup services for both network cards in my system fail to start with /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory. My networks still come up because I am using network-manager, but without network-manager, it seems the network would not come up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1434020/+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 1434020] [NEW] With systemd 219-4ubuntu6, ifup fails on startup
Public bug reported: After updating to systemd 219-4ubuntu6, the ifup services for both network cards in my system fail to start with /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory. My networks still come up because I am using network-manager, but without network-manager, it seems the network would not come up. ** Affects: systemd (Ubuntu) Importance: Undecided Status: 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/1434020 Title: With systemd 219-4ubuntu6, ifup fails on startup Status in systemd package in Ubuntu: New Bug description: After updating to systemd 219-4ubuntu6, the ifup services for both network cards in my system fail to start with /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory. My networks still come up because I am using network-manager, but without network-manager, it seems the network would not come up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1434020/+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 1434020] Re: With systemd 219-4ubuntu6, ifup fails on startup
The problem seems to be that ifup@.service currently isn't sequenced to run after systemd-tmpfiles-setup.service (both of those are configured to run after local-fs.target). If I override ifup@.service and set After=local-fs.target network-pre.target systemd-tmpfiles- setup.service, it starts properly. -- 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/1434020 Title: With systemd 219-4ubuntu6, ifup fails on startup Status in systemd package in Ubuntu: New Bug description: After updating to systemd 219-4ubuntu6, the ifup services for both network cards in my system fail to start with /sbin/ifup: failed to open lockfile /run/network/.ifstate.lock: No such file or directory. My networks still come up because I am using network-manager, but without network-manager, it seems the network would not come up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1434020/+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 1432158] [NEW] network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as long to boot to the login screen
Public bug reported: The enablement of NetworkManager-wait-online.service in network-manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly twice as long to boot to the login screen. I did some investigating and determined that this is because sddm.service depends on systemd-user- sessions.service which depends on remote-fs.target which depends on network-online.target which depends on NetworkManager-wait- online.service. For that reason, systemd is apparently waiting to start sddm until both the wired and wireless adapters are connected, which makes the system take much longer to boot. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- 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/1432158 Title: network-manager 0.9.10.0-4ubuntu10 makes my system take about twice as long to boot to the login screen Status in network-manager package in Ubuntu: New Status in sddm package in Ubuntu: New Bug description: The enablement of NetworkManager-wait-online.service in network- manager 0.9.10.0-4ubuntu10 has made my Kubuntu Vivid x64 system take nearly twice as long to boot to the login screen. I did some investigating and determined that this is because sddm.service depends on systemd-user-sessions.service which depends on remote-fs.target which depends on network-online.target which depends on NetworkManager-wait-online.service. For that reason, systemd is apparently waiting to start sddm until both the wired and wireless adapters are connected, which makes the system take much longer to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1432158/+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 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d
Interesting, I tried running the journalctl command again and now it works. Here is the output. ** Attachment added: journalctl.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431110/+attachment/4342526/+files/journalctl.log -- 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/1431110 Title: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, network-manager often fails to start properly. Instead of startup up as it should, it seems to get into a tight loop, burning through about 25% of each thread of my CPU. This only happens on one of my systems, the one that is equipped with an SSD. I have another system with the same software configuration that is equipped with an HDD that has never experienced this problem. If I let it sit for a long time, sometimes it eventually stops. During the time the CPU usage is high, the following text is spammed repeatedly to /var/log/syslog: Mar 11 21:40:53 mamarley-laptop dnsmasq[21306]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2766 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.970764] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2767 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.987394] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21344]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:41:34 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable
[Touch-packages] [Bug 1431110] Re: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d
The directory is indeed missing. If I run the journalctl command, it just says No journal files were found. (No, I haven't modified the logging configuration.) Running the systemd-tmpfiles command does create that directory. I have attached the output. ** Attachment added: systemd-tmpfiles.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431110/+attachment/4342507/+files/systemd-tmpfiles.log -- 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/1431110 Title: network-manager sometimes fails to start properly, missing /run/sendsigs.omit.d Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, network-manager often fails to start properly. Instead of startup up as it should, it seems to get into a tight loop, burning through about 25% of each thread of my CPU. This only happens on one of my systems, the one that is equipped with an SSD. I have another system with the same software configuration that is equipped with an HDD that has never experienced this problem. If I let it sit for a long time, sometimes it eventually stops. During the time the CPU usage is high, the following text is spammed repeatedly to /var/log/syslog: Mar 11 21:40:53 mamarley-laptop dnsmasq[21306]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2766 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.970764] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2767 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.987394] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21344]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:41:34 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType:
[Touch-packages] [Bug 1431107] Re: apparmor.service starts before remounting r/w, fails
Yes, both of those things are true. I have attached the output of journalctl -ab. This particular startup also triggered the network- manager-related bug that I reported, and I had to manually run the systemd-tmpfiles command you posted over there to actually get the system to finish booting to the point where journalctl would return anything. ** Attachment added: journalctlab.log https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+attachment/4342543/+files/journalctlab.log -- 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/1431107 Title: apparmor.service starts before remounting r/w, fails Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot images on lvm2.service
Sure, it says: Requires=basic.target Wants=system.slice Before=multi-user.target shutdown.target graphical.target checkfs.service local-fs.target After=system.slice basic.target cryptdisks-early.service mdadm-raid.service systemd-udevd.service mountdevsubfs.service systemd-journald.socket multipath-tools-boot.service I don't use LVM 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/1431107 Title: ordering cycles with early boot images on lvm2.service Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot images on lvm2.service
OK, here it is: michael@mamarley-laptop:~$ cat /etc/init.d/lvm2 #!/bin/sh ### BEGIN INIT INFO # Provides: lvm2 lvm # Required-Start:mountdevsubfs # Required-Stop: # Should-Start: udev mdadm-raid cryptdisks-early multipath-tools-boot # Should-Stop: umountroot mdadm-raid # X-Start-Before:checkfs mountall # X-Stop-After: umountfs # Default-Start: S # Default-Stop: ### END INIT INFO # dummy job, Ubuntu does LVM setup in udev rules, so starting udev is enough true michael@mamarley-laptop:~$ systemctl show lvm2 | grep Path FragmentPath=/run/systemd/generator.late/lvm2.service SourcePath=/etc/init.d/lvm2 michael@mamarley-laptop:~$ cat /run/systemd/generator.late/lvm2.service # Automatically generated by systemd-sysv-generator [Unit] Documentation=man:systemd-sysv-generator(8) SourcePath=/etc/init.d/lvm2 Description=(null) Before=runlevel2.target runlevel3.target runlevel4.target runlevel5.target shutdown.target checkfs.service local-fs.target After=mountdevsubfs.service udev.service mdadm-raid.service cryptdisks-early.service multipath-tools-boot.service Conflicts=shutdown.target [Service] Type=forking Restart=no TimeoutSec=5min IgnoreSIGPIPE=no KillMode=process GuessMainPID=no RemainAfterExit=yes ExecStart=/etc/init.d/lvm2 start ExecStop=/etc/init.d/lvm2 stop -- 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/1431107 Title: ordering cycles with early boot images on lvm2.service Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1431107] Re: ordering cycles with early boot images on lvm2.service
Yeah, for some reason my system has them in in *all* the rcX.d directories. rc2-rc5 all have start scripts (S05lvm2) and the others have kill scripts, except for rcS.d, which actually has nothing. I guess I should delete all of them and add one in rcS.d? Should the one in rcS.d be a start or kill script? -- 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/1431107 Title: ordering cycles with early boot images on lvm2.service Status in systemd package in Ubuntu: Incomplete Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] Re: ordering cycles with early boot rcS scripts with inappropriate rc2.d links
That seems to make everything work OK on bootup. Thanks! I have no idea how those symlinks got there. I definitely didn't put them there manually. -- 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/1431107 Title: ordering cycles with early boot rcS scripts with inappropriate rc2.d links Status in systemd package in Ubuntu: Triaged Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1431107/+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 1431107] [NEW] AppArmor often fails to start when booting Kubuntu Vivid x64 system with systemd
Public bug reported: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service: control process exited, code=exited status=123 Mar 11 21:25:44 mamarley-laptop apparmor[237]: ...fail! Mar 11 21:25:44 mamarley-laptop systemd[1]: Failed to start LSB: AppArmor initialization. Mar 11 21:25:44 mamarley-laptop systemd[1]: Unit apparmor.service entered failed state. Mar 11 21:25:44 mamarley-laptop systemd[1]: apparmor.service failed. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:30:08 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1431107 Title: AppArmor often fails to start when booting Kubuntu Vivid x64 system with systemd Status in systemd package in Ubuntu: New Bug description: After switching to systemd, the AppArmor service often fails to start on boot. This seems to happen at least 50% of the times I turn on the system. If I attempt to start the process again after the system is otherwise finished booting, it works fine. I also have another system with the same software configuration but a much slower storage system (HDD instead of SSD) which never suffers from this problem, so I think it is probably a race condition. If I do systemctl status apparmor, I get the following output: michael@mamarley-laptop:~$ sudo systemctl status apparmor ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor) Active: failed (Result: exit-code) since Wed 2015-03-11 21:25:44 EDT; 1min 5s ago Docs: man:systemd-sysv-generator(8) Process: 237 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: mkstemp: Read-only file system Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 11 21:25:44 mamarley-laptop apparmor[237]: Skipping profile in /etc/apparmor.d/disable:
[Touch-packages] [Bug 1431110] [NEW] network-manager sometimes fails to start properly and gets into a tight loop when booting Kubuntu Vivid x64 system with systemd
Public bug reported: After switching to systemd, network-manager often fails to start properly. Instead of startup up as it should, it seems to get into a tight loop, burning through about 25% of each thread of my CPU. This only happens on one of my systems, the one that is equipped with an SSD. I have another system with the same software configuration that is equipped with an HDD that has never experienced this problem. If I let it sit for a long time, sometimes it eventually stops. During the time the CPU usage is high, the following text is spammed repeatedly to /var/log/syslog: Mar 11 21:40:53 mamarley-laptop dnsmasq[21306]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2766 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.970764] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21325]: FAILED to start up Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq disappeared from the bus. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq exited with error: Filesystem problem (missing file/directory; permissions; etc) (3) Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq appeared on DBus: :1.2767 Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info DNS: starting dnsmasq... Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn dnsmasq not available on the bus, can't update servers. Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: error [1426124453.987394] [dns-manager/nm-dns-dnsmasq.c:398] update(): dnsmasq owner not found on bus: Could not get owner of name 'org.freedesktop.NetworkManager.dnsmasq': no such name Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: warn DNS: plugin dnsmasq update failed Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: info Writing DNS information to /sbin/resolvconf Mar 11 21:40:53 mamarley-laptop NetworkManager[515]: dnsmasq: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory Mar 11 21:40:53 mamarley-laptop dnsmasq[21344]: failed to open pidfile /run/sendsigs.omit.d/network-manager.dnsmasq.pid: No such file or directory ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Mar 11 21:41:34 2015 InstallationDate: Installed on 2014-06-01 (283 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) MachineType: LENOVO 2359CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-lowlatency root=UUID=1f7829ef-ffb8-4182-ac92-40d613ea78c9 ro elevator=deadline intel_pstate=enable acpi_osi=Windows 2012 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/21/2014 dmi.bios.vendor: LENOVO dmi.bios.version: G4ETA2WW (2.62 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ETA2WW(2.62):bd08/21/2014:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530
[Touch-packages] [Bug 1240957] Re: Scrolling behaviour and window focus has changed and is inconsistent
This is still happening on Kubuntu 14.10. GTK3 applications like Synaptic won't scroll unless they are focused. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1240957 Title: Scrolling behaviour and window focus has changed and is inconsistent Status in Compiz: Fix Released Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “compiz” package in Ubuntu: Fix Released Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Won't Fix Bug description: I wasn't sure which package to file this bug against, but seeing as it's a general desktop usability/consistency bug, the top level desktop environment seemed like a good target. On Ubuntu 13.10, AMD64, everything default (Unity 7 on X.org etc), except for installing nvidia-319-updates, all current packages as of now (2013-10-17; unity 7.1.2+13.10.20131014.1-0ubuntu1), I now have this behaviour which is different from Ubuntu versions up to 13.04, and, is also inconsistent within itself. Here's what I've found: The scrolling behaviour has changed, and seems to be different per application in Ubuntu 13.10. The old behaviour (up to 13.04): mouse pointer above window would allow scrolling, regardless of focus Apps that use the old behaviour: libreoffice, firefox, gnome-terminal The new behaviour (13.10): window must be focused, and pointer hovered above to allow scrolling Apps that use the new behaviour: nautilus, gedit, ubuntu-bug, software-updater STEPS TO REPRODUCE 1. Open gEdit, press enter until the window is scrollable. 2. Open Firefox, go to a webpage that's scrollable. 3. Place gEdit above Firefox but off to the right side so gEdit's scrollbar is still visible, have gEdit focused. 4. Position mouse pointer above gEdit, observe scrollwheel causes gEdit window to scroll. 5. Move mouse pointer above Firefox but do not focus Firefox, observe scrollwheel causes Firefox window to scroll. 6. Focus Firefox, leave pointer above Firefox, observe scrollwheel causes Firefox window to scroll 7. Move mouse pointer above gEdit but do not focus gEdit, observe scrollwheel FAILS to cause gEdit window to scroll. This behaviour is the same with any combination of the above apps (libreoffice, firefox, gnome-terminal all scrollable as long as pointer is above them; nautilus, gedit, software-updater, ubunut-bug will not scroll unless focused *and* have pointer above them) What *SHOULD* happen, is that any window will scroll as long as the pointer is above it. That's how it's always been in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Oct 17 22:12:18 2013 InstallationDate: Installed on 2013-09-30 (17 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20130925.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1240957/+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 1374825] [NEW] VDPAU does not work in libav on Utopic
Public bug reported: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I get [7f909958] vdpau_avcodec generic error: decoder profile not supported: 6. ** Affects: libav (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic Status in “libav” package in Ubuntu: New Bug description: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I get [7f909958] vdpau_avcodec generic error: decoder profile not supported: 6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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 1374825] Re: VDPAU does not work in libav on Utopic
This seems to be due to an API change in libav. They dropped the old API for using VDPAU decoding, which broke every application that uses VDPAU through libav. https://libav.org/releases/libav-10.5.release ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New ** Also affects: mplayer (Ubuntu) Importance: Undecided Status: New ** Also affects: mplayer2 (Ubuntu) Importance: Undecided Status: New ** Changed in: libav (Ubuntu) Status: New = Invalid ** Also affects: mpv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1374825 Title: VDPAU does not work in libav on Utopic Status in “libav” package in Ubuntu: Invalid Status in “mplayer” package in Ubuntu: New Status in “mplayer2” package in Ubuntu: New Status in “mpv” package in Ubuntu: New Status in “vlc” package in Ubuntu: New Bug description: After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU support has stopped working in all applications that use libav. In mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec... and in VLC I get [7f909958] vdpau_avcodec generic error: decoder profile not supported: 6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1374825/+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
