[Dx-packages] [Bug 2051343] Re: unity: FTBFS in Noble
This bug was fixed in the package unity-lens-files - 7.1.0+17.10.20170605-0ubuntu4 --- unity-lens-files (7.1.0+17.10.20170605-0ubuntu4) noble; urgency=medium * Fix outdated test case code. (LP: #2051343) -- Aaron Rainbolt Fri, 29 Mar 2024 00:43:56 + ** Changed in: unity-lens-files (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2051343 Title: unity: FTBFS in Noble Status in unity package in Ubuntu: Fix Committed Status in unity-api package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-files package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Invalid Status in unity-scope-home package in Ubuntu: Fix Released Bug description: As seen in the test rebuild: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html [ 9%] Building CXX object tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DUSE_X11 -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googletest/include -I/usr/include/unity/unity -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/libappstream-glib -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/webp -I/usr/include/uuid -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/libindicator3-0.4 -I/usr/include/json-glib-1.0 -I/usr/include/libbamf3 -I/usr/lib/x86_64-linux-gnu/libbamf3/include -I/usr/include/gnome-desktop-3.0 -I/usr/i nclude/gsettings-desktop-schemas -I/usr/include/libxml2 -I/usr/include/unity-settings-daemon-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/unity-misc -I/usr/include/zeitgeist-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/compiz -I/<>/obj-x86_64-linux-gnu/tests -I/<>/tests/. -I/<>/tests/.. -I/<>/tests/../services -I/<>/tests/../UnityCore -I/<>/tests/../plugins/unityshell/src -I/<>/obj-x86_64-linux-gnu -I/<>/plugins/unity-mt-grab-handles/src -I/<>/dash -I/<>/decorations -I/<>/launcher -I/<>/panel -I/<>/hud -I/<>/shortcuts -I/<>/shutdown -I/<>/unity-shared -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix- map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/unity-7.7.0+23.04.20230222.2-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++11 -fno-permissive -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=deprecated-declarations -Wno-error=unused-local-typedefs -Wno-sign-compare -MD -MT tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o -MF CMakeFiles/test-main-libs.dir/test_main.cpp.o.d -o CMakeFiles/test-main-libs.dir/test_main.cpp.o -c /<>/tests/test_main.cpp In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /<>/tests/test_main.cpp:1: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. 279 | #error C++ versions less than C++14 are not supported. | ^ make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2051343] Re: unity: FTBFS in Noble
This bug was fixed in the package unity-lens-applications - 7.1.0+16.10.20160927-0ubuntu7 --- unity-lens-applications (7.1.0+16.10.20160927-0ubuntu7) noble; urgency=medium * Fix multiple Vala errors leading to build failure. (LP: #2051343) -- Aaron Rainbolt Fri, 29 Mar 2024 00:25:16 + -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2051343 Title: unity: FTBFS in Noble Status in unity package in Ubuntu: Fix Committed Status in unity-api package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-files package in Ubuntu: In Progress Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Invalid Status in unity-scope-home package in Ubuntu: Fix Released Bug description: As seen in the test rebuild: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html [ 9%] Building CXX object tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DUSE_X11 -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googletest/include -I/usr/include/unity/unity -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/libappstream-glib -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/webp -I/usr/include/uuid -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/libindicator3-0.4 -I/usr/include/json-glib-1.0 -I/usr/include/libbamf3 -I/usr/lib/x86_64-linux-gnu/libbamf3/include -I/usr/include/gnome-desktop-3.0 -I/usr/i nclude/gsettings-desktop-schemas -I/usr/include/libxml2 -I/usr/include/unity-settings-daemon-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/unity-misc -I/usr/include/zeitgeist-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/compiz -I/<>/obj-x86_64-linux-gnu/tests -I/<>/tests/. -I/<>/tests/.. -I/<>/tests/../services -I/<>/tests/../UnityCore -I/<>/tests/../plugins/unityshell/src -I/<>/obj-x86_64-linux-gnu -I/<>/plugins/unity-mt-grab-handles/src -I/<>/dash -I/<>/decorations -I/<>/launcher -I/<>/panel -I/<>/hud -I/<>/shortcuts -I/<>/shutdown -I/<>/unity-shared -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix- map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/unity-7.7.0+23.04.20230222.2-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++11 -fno-permissive -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=deprecated-declarations -Wno-error=unused-local-typedefs -Wno-sign-compare -MD -MT tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o -MF CMakeFiles/test-main-libs.dir/test_main.cpp.o.d -o CMakeFiles/test-main-libs.dir/test_main.cpp.o -c /<>/tests/test_main.cpp In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /<>/tests/test_main.cpp:1: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. 279 | #error C++ versions less than C++14 are not supported. | ^ make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2051343] Re: unity: FTBFS in Noble
This bug was fixed in the package unity-lens-music - 6.9.1+16.04-0ubuntu5 --- unity-lens-music (6.9.1+16.04-0ubuntu5) noble; urgency=medium * Fix Vala incompatibilities. (LP: #2051343) -- Aaron Rainbolt Fri, 29 Mar 2024 00:56:25 + ** Changed in: unity-lens-music (Ubuntu) Status: In Progress => Fix Released ** Changed in: unity-scope-home (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2051343 Title: unity: FTBFS in Noble Status in unity package in Ubuntu: Fix Committed Status in unity-api package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-files package in Ubuntu: In Progress Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Invalid Status in unity-scope-home package in Ubuntu: Fix Released Bug description: As seen in the test rebuild: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html [ 9%] Building CXX object tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DUSE_X11 -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googletest/include -I/usr/include/unity/unity -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/libappstream-glib -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/webp -I/usr/include/uuid -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/libindicator3-0.4 -I/usr/include/json-glib-1.0 -I/usr/include/libbamf3 -I/usr/lib/x86_64-linux-gnu/libbamf3/include -I/usr/include/gnome-desktop-3.0 -I/usr/i nclude/gsettings-desktop-schemas -I/usr/include/libxml2 -I/usr/include/unity-settings-daemon-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/unity-misc -I/usr/include/zeitgeist-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/compiz -I/<>/obj-x86_64-linux-gnu/tests -I/<>/tests/. -I/<>/tests/.. -I/<>/tests/../services -I/<>/tests/../UnityCore -I/<>/tests/../plugins/unityshell/src -I/<>/obj-x86_64-linux-gnu -I/<>/plugins/unity-mt-grab-handles/src -I/<>/dash -I/<>/decorations -I/<>/launcher -I/<>/panel -I/<>/hud -I/<>/shortcuts -I/<>/shutdown -I/<>/unity-shared -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix- map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/unity-7.7.0+23.04.20230222.2-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++11 -fno-permissive -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=deprecated-declarations -Wno-error=unused-local-typedefs -Wno-sign-compare -MD -MT tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o -MF CMakeFiles/test-main-libs.dir/test_main.cpp.o.d -o CMakeFiles/test-main-libs.dir/test_main.cpp.o -c /<>/tests/test_main.cpp In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /<>/tests/test_main.cpp:1: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. 279 | #error C++ versions less than C++14 are not supported. | ^ make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2051343] Re: unity: FTBFS in Noble
This bug was fixed in the package unity-scope-home - 6.8.2+19.04.20190412-0ubuntu4 --- unity-scope-home (6.8.2+19.04.20190412-0ubuntu4) noble; urgency=medium * Fix problems with values being non-public when they should have been. (LP: #2051343) -- Aaron Rainbolt Fri, 29 Mar 2024 01:14:49 + ** Changed in: unity-lens-applications (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2051343 Title: unity: FTBFS in Noble Status in unity package in Ubuntu: Fix Committed Status in unity-api package in Ubuntu: New Status in unity-lens-applications package in Ubuntu: Fix Released Status in unity-lens-files package in Ubuntu: In Progress Status in unity-lens-music package in Ubuntu: Fix Released Status in unity-lens-video package in Ubuntu: Invalid Status in unity-scope-home package in Ubuntu: Fix Released Bug description: As seen in the test rebuild: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html [ 9%] Building CXX object tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o cd /<>/obj-x86_64-linux-gnu/tests && /usr/bin/c++ -DUSE_X11 -I/usr/src/googletest/googlemock/include -I/usr/src/googletest/googletest/include -I/usr/include/unity/unity -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dee-1.0 -I/usr/include/gio-unix-2.0 -I/usr/include/libappstream-glib -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/webp -I/usr/include/uuid -I/usr/include/atk-1.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/pixman-1 -I/usr/include/libdbusmenu-glib-0.4 -I/usr/include/gtk-3.0 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi -I/usr/include/libindicator3-0.4 -I/usr/include/json-glib-1.0 -I/usr/include/libbamf3 -I/usr/lib/x86_64-linux-gnu/libbamf3/include -I/usr/include/gnome-desktop-3.0 -I/usr/i nclude/gsettings-desktop-schemas -I/usr/include/libxml2 -I/usr/include/unity-settings-daemon-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/Nux-4.0 -I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/unity-misc -I/usr/include/zeitgeist-2.0 -I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/compiz -I/<>/obj-x86_64-linux-gnu/tests -I/<>/tests/. -I/<>/tests/.. -I/<>/tests/../services -I/<>/tests/../UnityCore -I/<>/tests/../plugins/unityshell/src -I/<>/obj-x86_64-linux-gnu -I/<>/plugins/unity-mt-grab-handles/src -I/<>/dash -I/<>/decorations -I/<>/launcher -I/<>/panel -I/<>/hud -I/<>/shortcuts -I/<>/shutdown -I/<>/unity-shared -g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix- map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/<>=/usr/src/unity-7.7.0+23.04.20230222.2-0ubuntu2 -Wdate-time -D_FORTIFY_SOURCE=3 -DGNOME_DESKTOP_USE_UNSTABLE_API -std=c++11 -fno-permissive -Wall -Wcast-align -Wempty-body -Wformat-security -Winit-self -Warray-bounds -Wno-error=deprecated-declarations -Wno-error=unused-local-typedefs -Wno-sign-compare -MD -MT tests/CMakeFiles/test-main-libs.dir/test_main.cpp.o -MF CMakeFiles/test-main-libs.dir/test_main.cpp.o.d -o CMakeFiles/test-main-libs.dir/test_main.cpp.o -c /<>/tests/test_main.cpp In file included from /usr/src/googletest/googletest/include/gtest/gtest-message.h:57, from /usr/src/googletest/googletest/include/gtest/gtest-assertion-result.h:46, from /usr/src/googletest/googletest/include/gtest/gtest.h:64, from /<>/tests/test_main.cpp:1: /usr/src/googletest/googletest/include/gtest/internal/gtest-port.h:279:2: error: #error C++ versions less than C++14 are not supported. 279 | #error C++ versions less than C++14 are not supported. | ^ make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/2051343/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2057710] Re: Accountsservice FTBFS on noble
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu4 --- accountsservice (23.13.9-2ubuntu4) noble; urgency=medium * debian/patches/0001-tests-s-assertEquals-assertEqual.patch: Add patch to fix FTBFS with unittest from Python 3.12. (LP: #2057710) -- David Mohammed Tue, 12 Mar 2024 21:51:36 + ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2057710 Title: Accountsservice FTBFS on noble Status in accountsservice package in Ubuntu: Fix Released Bug description: package version 23.13.9-2ubuntu FTBFS on all architectures. This is because of an invalid test This has been resolved upstream - see the attached debdiff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2057710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2044300] Re: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main)
This bug was fixed in the package zeitgeist - 1.0.4-5ubuntu1 --- zeitgeist (1.0.4-5ubuntu1) noble; urgency=low * Merge with Debian unstable. Remaining changes: (LP: #2044300) - Add nodisplay_autostart.patch: Don't show in Startup Applications - Add pre_populator.patch: Pre-populate the log with some events so that the Unity dash isn't empty on first run. * Added changes: - Add fix-monitor-test.patch: monitor test is failing in Ubuntu if it is linked with libzeitgeist-datamodel. * Dropped changes: - add_datahub_autostart_delay.patch, no longer required. zeitgeist (1.0.4-5) unstable; urgency=medium * fix source helper tool copyright-check + work with Path::Tiny 0.144 + avoid insecure shell expansion * add patch cherry-picked upstream to support Python 3.11; closes: bug#1032125, thanks to s3v * declare compliance with Debian Policy 4.6.2 * update copyright info: update coverage zeitgeist (1.0.4-4) unstable; urgency=medium * update source helper script copyright-check * update copyright info: + use field License-Grant + update coverage zeitgeist (1.0.4-3) unstable; urgency=medium * add patch cherry-picked upstream to fix wrong parameter for Event.full() ctor * declare compliance with Debian Policy 4.6.1 * update copyright info: + merge Files sections with identical licensing + sort copyright holders + use field Reference + update coverage * add source helper script copyright-check * use semantic newlines in long descriptions and copyright file License grants * build-depend on dh-sequence-pkgkde-symbolshelper (not pkg-kde-tools) * build-depend on dh-sequence-gir (not gobject-introspection) * build-depend on dh-sequence-python3 (not dh-python) * tighten packaging shell files zeitgeist (1.0.4-2) unstable; urgency=medium * relax to (build-)depend unversioned on libdee-dev libgirepository1.0-dev libglib2.0-dev libgtk-3-dev libjson-glib-dev libsqlite3-dev libtelepathy-glib-dev valac: needed versions satisfied in all supported releases of Debian * drop ancient Breaks/Replaces, and relax to have zeitgeist-datahub depend unversioned on zeitgeist-core * declare compliance with Debian Policy 4.6.0 (not too spcifically on 4.6.0.1) * set Rules-Requires-Root: no * new maintainer: Debian semweb Team, with myself as uploader; closes: bug#919274 * install upstream NEWS and README.md with all binary packages (not only with zeitgeist-core) * update patch DEP-3 headers * install ontology files in binary package zeitgeist, and mention that in long description * update patch skip-failing-tests.patch to enable no longer failing tests * fix wrap test checking in dbus-run-session (although dbus-related tests still fail but in different way now); build-depend on dbus-daemon; closes: bug#836060, thanks to Simon McVittie * drop no longer needed calls to dpkg-maintscript-helper in maintainer scripts zeitgeist (1.0.4-1) experimental; urgency=medium [ upstream ] * new release [ Jonas Smedegaard ] * adopt package: set myself as maintainer * update git-buildpackage config: + sign tags + filter-out any .git* file + use DEP14 branch naming scheme + add usage comment * update watch file: + use format 4 + track Gitlab source + add filenamemangle + set dversionmangle=auto + add usage comment * use pkgkde_symbolshelper; build-depend on pkg-kde-tools * drop patch cherry-picked upstream now applied * unfuzz remaining patches, with shortening quilt options zeitgeist (1.0.3-7) unstable; urgency=medium * QA upload. * Use upstream patch to fix ftbfs. (Closes: #997287) * Update Standards-Version to 4.6.0.1 zeitgeist (1.0.3-6) unstable; urgency=medium * QA upload. * Source-only upload. zeitgeist (1.0.3-5) unstable; urgency=medium * QA upload. [ Debian Janitor ] * Remove constraints unnecessary since stretch: + Build-Depends: Drop versioned constraint on bash-completion and gobject-introspection. -- Sudip Mukherjee Mon, 25 Dec 2023 17:37:52 + ** Changed in: zeitgeist (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2044300 Title: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Status in zeitgeist package in Ubuntu: Fix Released Bug description: Please merge zeitgeist 1.0.4-5 (universe) from Debian unstable (main) Explanation of the Ubuntu delta: Carry forward three previous Ubuntu specific patch. 1. add_datahub_autostart_delay.patch 2. nodisplay_autostart.patch 3. pre_populator.patch Extra change for this version: The monitor-test was skipped in the previous version as it was failing. That
[Dx-packages] [Bug 2024182] Re: GHSL-2023-139: use-after-free in user.c
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu2
---
accountsservice (23.13.9-2ubuntu2) mantic; urgency=medium
* SECURITY UPDATE: use-after-free in user.c (LP: #2024182)
- debian/patches/0010-set-language.patch: updated to properly return
from functions after throw_error() has been called.
- CVE-2023-3297
-- Marc Deslauriers Wed, 28 Jun 2023
11:10:09 -0400
** Changed in: accountsservice (Ubuntu Mantic)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/2024182
Title:
GHSL-2023-139: use-after-free in user.c
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Focal:
Fix Released
Status in accountsservice source package in Jammy:
Fix Released
Status in accountsservice source package in Kinetic:
Fix Released
Status in accountsservice source package in Lunar:
Fix Released
Status in accountsservice source package in Mantic:
Fix Released
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
`GHSL-2023-139`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified a potential security vulnerability in
[accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).
We are committed to working with you to help resolve this issue. In
this report you will find everything you need to effectively
coordinate a resolution of this issue with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2023-139` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
An unprivileged local attacker can trigger a use-after-free
vulnerability in accountsservice by sending a D-Bus message to the
accounts-daemon process.
## Product
accountsservice
## Tested Version
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)
The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
but it is present on both.
## Details
### Use-after-free when `throw_error` is called (`GHSL-2023-139`)
After receiving a D-Bus [method
call](https://dbus.freedesktop.org/doc/dbus-
specification.html#message-protocol-types), a D-Bus server is expected
to send either a `METHOD_RETURN` or a `ERROR` message back to the
client, _but not both_. This is done incorrectly in several places in
accountsservice. For example, in
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
language.patch?h=import/22.08.8-1ubuntu7#n427):
```c
static void
user_change_language_authorized_cb (Daemon*daemon,
User *user,
GDBusMethodInvocation *context,
gpointer data)
{
const gchar *language = data;
if (!user_HOME_available (user)) {
/* SetLanguage was probably called from a login greeter,
and HOME not mounted and/or not decrypted.
Hence don't save anything, or else accountsservice
and ~/.pam_environment would become out of sync. */
throw_error (context, ERROR_FAILED, "not access to HOME yet
so language not saved"); <= 1
goto out;
}
out:
accounts_user_complete_set_language (ACCOUNTS_USER (user), context);
<= 2
}
```
If `user_HOME_available` returns an error, then `throw_error` is
called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
is also sent at 2. This is incorrect D-Bus protocol, but the more
serious problem is that it causes a use-after-free because both
`throw_error` and `accounts_user_complete_set_language` decrease the
reference count on `context`. In other words, `context` is freed by
`throw_error` and a UAF occurs in
`accounts_user_complete_set_language`.
An attacker can trigger the bug above by causing `user_HOME_available`
to fail, which they can do by deleting all the files from their home
directory. But there are other incorrect uses of `throw_error` in
`user.c` which are less inconvenient to trigger. For example, this
command triggers a call to `throw_error` in `user_update_environment`
due to the invalid characters in the string.
```bash
dbus-send --system --print-reply --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage
string:'**'
```
On Ubuntu 23.04, the above
[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in ayatana-indicator-messages package in Ubuntu: In Progress Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2024560] Re: Check if 0010-set-language needs to be update for the new languages property
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2024560 Title: Check if 0010-set-language needs to be update for the new languages property Status in accountsservice package in Ubuntu: Fix Released Bug description: Upstream did changes to add a languages properties https://gitlab.freedesktop.org/accountsservice/accountsservice/-/commit/881e0ea7 I've rebased 0010-set-language to apply correctly but we should review if we need to adapt the patch to apply a similar logic to the new languages property that it's doing for old language one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024560/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2024870] Re: accountsservice segfault when toggling autologin
This bug was fixed in the package accountsservice - 23.13.9-2ubuntu1 --- accountsservice (23.13.9-2ubuntu1) mantic; urgency=medium * Includes some extra upstream bugfixes accountsservice (23.13.9-2) unstable; urgency=medium * debian/patches/git_user_manager.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout (lp: #2015962) * debian/patches/git_default_gdm.patch: - default to gdm if there display-manager.service isn't a known target, which is the case for our gdm called gdm3, fixes the service crashing when trying to toggle autologin (lp: #2024870) -- Sebastien Bacher Mon, 26 Jun 2023 16:25:07 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2024870 Title: accountsservice segfault when toggling autologin Status in accountsservice package in Ubuntu: Fix Released Bug description: Error encountered after first boot ubuntu-gnome-desktop installed on LiveServer Daily 23.10 attempting to set AutoLogin in Settings>User. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: accountsservice 23.13.9-1ubuntu1 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 Date: Thu Jun 22 21:28:14 2023 ExecutablePath: /usr/libexec/accounts-daemon ExecutableTimestamp: 1687359023 ProcCmdline: /usr/libexec/accounts-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: accountsservice UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2024870/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1998052] Re: mate-indicator-applet-complete uses increasing amount of CPU
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-applet (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1998052 Title: mate-indicator-applet-complete uses increasing amount of CPU Status in indicator-applet package in Ubuntu: New Bug description: The mate-indicator-appelet-complete uses an increasing amount of CPU% reached 5% after a couple of days without a reboot. It goes up about 2% each day. I can reset the usage by running killall mate-indicator- in terminal. Then choosing the reload option on the resulting popup message. I don't reboot often so I use the killall every couple of days. I have the following apps in my MATE-indicator: sound, messages, Network, Livepatch, BOINCTasks.js, My weather indicator, Caffeine, gpodder, variety, printers I am new to reporting bugs, please let me know if you require more information like system info etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1998052/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un
This bug was fixed in the package indicator-messages - 13.10.1+18.10.20180918-0ubuntu5 --- indicator-messages (13.10.1+18.10.20180918-0ubuntu5) lunar; urgency=medium * debian/conrol, debian/*.install: drop the libmessaging-menu0, libmessaging-menu-dev and gir1.2-messagingmenu-1.0 binary packages. Those are built and provided by ayatana-indicator-messages and cannot realistically be published to the archive during builds right now. They have been removed from the archive already when copied-forward. * debian/rules: change --fail-missing to --list-missing so that we don't fail when we don't install all the built files. Remove unneeded removal of *.la files as we don't install the library bits anymore. * debian/rules: make sure dh_auto_install does what it's supposed to. -- Łukasz 'sil2100' Zemczak Wed, 19 Apr 2023 16:55:12 +0100 ** Changed in: indicator-messages (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Committed Status in ayatana-indicator-messages package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2016312] [NEW] /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_sign
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/0e715044718e39117f0d6382a7dc032e629ee88e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: lunar -- /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service:11:free_fetch_user_request:g_closure_invoke:signal_emit_unlocked_R:g_signal_emit_valist:g_signal_emit https://bugs.launchpad.net/bugs/2016312 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu7 --- accountsservice (22.08.8-1ubuntu7) lunar; urgency=medium * debian/patches/gitlab_manager_requests.patch: - Disconnect from manager signals when freeing a request and resolve indicator-messages crashing on logout, thanks Marco! (lp: #2015962) -- Sebastien Bacher Thu, 13 Apr 2023 23:59:56 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Released Status in indicator-messages package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2015962] Re: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_un
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-messages (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015962 Title: indicator-messages-service crashed with SIGSEGV in g_type_check_instance() from g_signal_handlers_disconnect_matched() from act_user_manager_finalize() from g_object_unref() from im_accounts_service_dispose() Status in accountsservice package in Ubuntu: Incomplete Status in indicator-messages package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-messages. This problem was most recently seen with package version 13.10.1+18.10.20180918-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/94c77bb11d79da78a8cb610adb9252f41d2ab4a4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2015962/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2015183] Re: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:119
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: accountsservice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2015183 Title: Invalid read of size 8 in gnome-shell from accountsservice: free_fetch_user_request (act-user-manager.c:1717) from on_find_user_by_name_finished (act-user-manager.c:1192) Status in accountsservice package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/64e3f2e18d0341d9671739f096085c0310725018 ==33999== Invalid read of size 8 ==33999==at 0x4D2D599: g_type_check_instance_is_fundamentally_a (gtype.c:4164) ==33999==by 0x4D149EA: g_object_set_data (gobject.c:4242) ==33999==by 0x363DCFD9: free_fetch_user_request (act-user-manager.c:1717) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BCE64C: complete_in_idle_cb (gtask.c:1323) ==33999== Address 0xb966c30 is 0 bytes inside a block of size 64 free'd ==33999==at 0x484620F: free (vg_replace_malloc.c:872) ==33999==by 0x4D2C66B: g_type_free_instance (gtype.c:2062) ==33999==by 0x4D1A0A6: UnknownInlinedFun (gobject.c:1556) ==33999==by 0x4D1A0A6: g_object_notify (gobject.c:1602) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:562) ==33999==by 0x363E3519: UnknownInlinedFun (act-user.c:557) ==33999==by 0x363E3519: _act_user_update_from_object_path (act-user.c:1346) ==33999==by 0x363E3C3F: fetch_user_incrementally (act-user-manager.c:1804) ==33999==by 0x363E3E7F: on_find_user_by_name_finished (act-user-manager.c:1192) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C382AB: reply_cb (gdbusproxy.c:2571) ==33999==by 0x4BCE612: g_task_return_now (gtask.c:1309) ==33999==by 0x4BD2042: UnknownInlinedFun (gtask.c:1378) ==33999==by 0x4BD2042: g_task_return (gtask.c:1335) ==33999==by 0x4C28801: g_dbus_connection_call_done (gdbusconnection.c:5885) ==33999== Block was alloc'd at ==33999==at 0x4848A13: calloc (vg_replace_malloc.c:1328) ==33999==by 0x4DB5550: g_malloc0 (gmem.c:163) ==33999==by 0x4D31B7C: g_type_create_instance (gtype.c:1965) ==33999==by 0x4D1920F: g_object_new_internal (gobject.c:2246) ==33999==by 0x4D1A7B7: g_object_new_with_properties (gobject.c:2409) ==33999==by 0x4D1B560: g_object_new (gobject.c:2055) ==33999==by 0x363DE5F1: create_new_user (act-user-manager.c:707) ==33999==by 0x363E41D8: act_user_manager_get_user (act-user-manager.c:1896) ==33999==by 0x5DDE8B5: ffi_call_unix64 (unix64.S:104) ==33999==by 0x5DDB34C: ffi_call_int.lto_priv.0 (ffi64.c:673) ==33999==by 0x5DDDF32: ffi_call (ffi64.c:710) ==33999==by 0x4F28BD8: Gjs::Function::invoke(JSContext*, JS::CallArgs const&, JS::Handle, _GIArgument*) (function.cpp:995) ==33999== ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: accountsservice 22.08.8-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Apr 4 14:29:55 2023 InstallationDate: Installed on 2022-11-28 (126 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2015183/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2012879] Re: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_fini
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu6 --- accountsservice (22.08.8-1ubuntu6) lunar; urgency=medium * debian/patches/git_users_requests.patch: - included more fixes from upstream !128, resolves an invalid read which is leading to crashes client softwares (lp: #2012879) -- Sebastien Bacher Fri, 07 Apr 2023 15:10:37 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2012879 Title: indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() Status in accountsservice package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012879/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1966905] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice]
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu5 --- accountsservice (22.08.8-1ubuntu5) lunar; urgency=medium * src/libaccountsservice/act-user-manager.c: - cherry pick a fix invalid users requests (lp: #1966905) -- Sebastien Bacher Mon, 27 Mar 2023 22:02:47 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1966905 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from free_fetch_user_request() [accountsservice] Status in accountsservice: New Status in gnome-control-center: Unknown Status in accountsservice package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: This is now the #1 gnome-shell crasher in Ubuntu 23.04. https://errors.ubuntu.com/problem/d85747462e756cb405d1e87b9c59b0b995a7d394 https://errors.ubuntu.com/problem/1674bdbf40a28b5f59067ffde832ba508ecba114 Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==
[Dx-packages] [Bug 2012879] [NEW] indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_fi
You have been subscribed to a public bug: https://errors.ubuntu.com/problem/2416b63fd3efcd8ec09f184b6f50981fc56fb16d Crash in indicator-messages-service ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: indicator-messages 13.10.1+18.10.20180918-0ubuntu3 Uname: Linux 6.2.0-18-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 27 14:25:09 2023 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ExecutableTimestamp: 1633601577 ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-messages/indicator-messages-service ProcCwd: /home/dan ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: indicator-messages UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-crash jammy kinetic lunar rls-ll-incoming -- indicator-messages-service crashed with SIGSEGV in ACT_IS_USER() from _act_user_update_from_object_path() from fetch_user_incrementally() from on_find_user_by_name_finished() from g_task_return_now() https://bugs.launchpad.net/bugs/2012879 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 2012552] Re: /usr/libexec/accounts-daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now
This bug was fixed in the package gnome-control-center - 1:44.0-1ubuntu2 --- gnome-control-center (1:44.0-1ubuntu2) lunar; urgency=medium * Drop (again) update_region() call with NULL argument (LP: #2012552) -- Gunnar Hjalmarsson Wed, 22 Mar 2023 23:43:31 +0100 ** Changed in: gnome-control-center (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/2012552 Title: /usr/libexec/accounts- daemon:11:g_dbus_method_invocation_return_value_internal:check_auth_cb:g_simple_async_result_complete:check_authorization_cb:g_task_return_now Status in accountsservice package in Ubuntu: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding accountsservice. This problem was most recently seen with package version 22.08.8-1ubuntu4, the problem page at https://errors.ubuntu.com/problem/8aec6774e070650ea5d4ded3cd3d4c0ebdbf9335 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2012552/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
This bug was fixed in the package gnome-shell-extension-appindicator - 53-1 --- gnome-shell-extension-appindicator (53-1) experimental; urgency=medium * New upstream release * appIndicator: Wait for style change if no stage is set * appIndicator: Reuse already imported namespaces * appIndicator Use Clutter to load RGBA Pixmap textures natively * appIndicator: Simplify loading of custom image files (LP: #784055, #1973358) * dbusMenu: Use more dbus async methods * interfaces-xml: Comment out the signal definitions (avoids gjs signals) * dbusMenu: Do not update menu items while the menu is closed * Util: Do not recreate the default theme each time * appIndicator: Only update icon size when it matters * appIndicator: Only perform updating actions if we're fully ready * appIndicator: Ensure St.Icon loading icon size matches theme and preferences * appIndicator: return the previous GIcon if something failed * appIndicator: Refactor named icons lookup and loading * appIndicator: Use correct update frequency on signals accumulator * appIndicator: Ensure that property emissions are queued together * dbusMenu: Use cancellable's to handle subsequent requests * dbusMenu: Populate menus in chunked idles * statusNotifierWatcher: Properly handle null services * dbusUtil: Filter introspectable bus by interfaces if provided * dbusUtils: Use more reasonable timeout for introspection * util: Use a recursive async generator to get introspection results * statusNotifierWatcher: Remove idle promise on bus seeking * debian/patches: Drop applied upstream -- Marco Trevisan (Treviño) Mon, 13 Mar 2023 20:21:32 +0100 ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell from accountsservice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: accountsservice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==
[Dx-packages] [Bug 1966905] Re: Valgrind memory errors in gnome-shell from accountsservice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1966905 Title: Memory access errors in gnome-shell from accountsservice Status in accountsservice: New Status in accountsservice package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Valgrind memory errors in gnome-shell 42 from accountsservice: ==60511== Invalid read of size 8 ==60511==at 0x4D207FA: g_type_check_instance_cast (gtype.c:4120) ==60511==by 0x1E421CA2: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511==by 0x4D9CC23: UnknownInlinedFun (gmain.c:3417) ==60511==by 0x4D9CC23: g_main_context_dispatch (gmain.c:4135) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:562) ==60511==by 0x1E428ECA: UnknownInlinedFun (act-user.c:557) ==60511==by 0x1E428ECA: _act_user_update_from_object_path (act-user.c:1346) ==60511==by 0x1E42966F: fetch_user_incrementally (act-user-manager.c:1789) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511== Block was alloc'd at ==60511==at 0x4848899: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4DA5718: g_malloc (gmem.c:125) ==60511==by 0x4DBCB64: g_slice_alloc (gslice.c:1072) ==60511==by 0x4DBD1CD: g_slice_alloc0 (gslice.c:1098) ==60511==by 0x4D24E61: g_type_create_instance (gtype.c:1911) ==60511==by 0x4D0BF4C: g_object_new_internal (gobject.c:2011) ==60511==by 0x4D0D1AC: g_object_new_with_properties (gobject.c:2181) ==60511==by 0x4D0DCB0: g_object_new (gobject.c:1821) ==60511==by 0x1E422792: create_new_user (act-user-manager.c:706) ==60511==by 0x1E429BD8: act_user_manager_get_user (act-user-manager.c:1879) ==60511==by 0x68ADE2D: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511==by 0x68AA492: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==60511== ==60511== Invalid read of size 8 ==60511==at 0x4D206E9: g_type_check_instance_is_fundamentally_a (gtype.c:4091) ==60511==by 0x4D06E9A: g_object_set_data (gobject.c:3982) ==60511==by 0x1E421CB6: free_fetch_user_request (act-user-manager.c:1708) ==60511==by 0x1E4298E7: on_find_user_by_name_finished (act-user-manager.c:1187) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C298BA: reply_cb (gdbusproxy.c:2576) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0E0A: UnknownInlinedFun (gtask.c:1300) ==60511==by 0x4BC0E0A: g_task_return (gtask.c:1256) ==60511==by 0x4C2107E: g_dbus_connection_call_done (gdbusconnection.c:5895) ==60511==by 0x4BC0C08: g_task_return_now (gtask.c:1230) ==60511==by 0x4BC0C4C: complete_in_idle_cb (gtask.c:1244) ==60511== Address 0x185b5110 is 0 bytes inside a block of size 64 free'd ==60511==at 0x484B27F: free (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==60511==by 0x4D1F7D4: g_type_free_instance (gtype.c:2008) ==60511==by
[Dx-packages] [Bug 1999698] Re: Dodgy looking patch applied to our build.
This bug was fixed in the package accountsservice - 22.08.8-1ubuntu4 --- accountsservice (22.08.8-1ubuntu4) lunar; urgency=medium * debian/patches/0010-set-language.patch: - Fix code ambiguity causing compiler warning (LP: #1999698). -- Gunnar Hjalmarsson Wed, 14 Dec 2022 23:36:32 +0100 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1999698 Title: Dodgy looking patch applied to our build. Status in accountsservice package in Ubuntu: Fix Released Bug description: When building accountsservice we apply patches, among of which is `0010-set-language.patch` which raises concerns. It will not compile without warnings: At the very least contains misleading indentation. ``` [92/99] Compiling C object src/accounts-daemon.p/user.c.o ../src/user.c: In function ‘user_HOME_available’: ../src/user.c:1753:27: warning: this ‘else’ clause does not guard... [-Wmisleading-indentation] 1753 | } else | ^~~~ ../src/user.c:1755:33: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘else’ 1755 | break; | ^ ``` The code: ``` } else g_free (path_to_entry); break; ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1999698/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1989296] Re: cannot exit snap-store
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: notify-osd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1989296 Title: cannot exit snap-store Status in notify-osd package in Ubuntu: Confirmed Bug description: system tells me to exit snap-store to allow a pending update, but nobody told me how anyway organizing of all that is 'snap' is Canonical's responsibility and not mine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: notify-osd 0.9.35+20.04.20191129-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Sep 12 09:20:41 2022 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Yaru' IconTheme: 'ubuntu-mono-dark' InstallationDate: Installed on 2021-01-14 (605 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 003: ID 0592:0002 Powerware Corp. UPS (X-Slot) Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=usbfs, 1.5M |__ Port 5: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro RelatedPackageVersions: xserver-xorg 1:7.7+19ubuntu14 libgl1-mesa-glx N/A libdrm2 2.4.107-8ubuntu1~20.04.2 xserver-xorg-video-intel 2:2.99.917+git20200226-1 xserver-xorg-video-ati 1:19.1.0-1 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:skuL1G76AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1989296/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1987920] Re: indicator-datetime fails to build with default gcc (gcc-12)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1987920 Title: indicator-datetime fails to build with default gcc (gcc-12) Status in indicator-datetime package in Ubuntu: Confirmed Status in indicator-datetime source package in Kinetic: Confirmed Bug description: indicator-datetime fails to build from source in Kinetic with the default compiler, gcc/g++-12 To allow the package to build so that we can complete the evolution- data-server 3.45 transition, I switched the package to build with gcc/g++-11. I suggest switching to the Ayatana Indicators (ayatana-indicator- datetime) which are maintained and are able to build successfully with the default compiler. See https://launchpad.net/bugs/1983374 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1987920/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseeffects (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1948882 Title: PulseEffects does not properly initialize on startup Status in d-conf package in Ubuntu: Confirmed Status in pulseeffects package in Ubuntu: Confirmed Bug description: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
This bug was fixed in the package accountsservice - 22.07.5-2ubuntu2 --- accountsservice (22.07.5-2ubuntu2) kinetic; urgency=medium [ Marc Deslauriers ] * SECURITY UPDATE: accountsservice incorrect privilege dropping (LP: #1974250) - debian/patches/0009-language-tools.patch: updated to not reset effective uid, and migrate root-owned .pam_environment file. - This change was originally known as CVE-2020-16126 and got reverted by mistake in 0.6.55-3ubuntu1. - CVE-2022-1804 * Fix FTBFS with a newer python-dbusmock package: - debian/patches/adduser_invocation.patch: fix invocation of AddUser in tests/dbusmock/accounts_service.py. - debian/patches/setlocked_signature.patch: fix the signature for the SetLocked call in tests/dbusmock/accounts_service.py. -- Gunnar Hjalmarsson Tue, 24 May 2022 19:53:07 +0200 ** Changed in: accountsservice (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Fix Released Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1192081] [NEW] Previews for applications are really slow to display anything
You have been subscribed to a public bug: I'm seeing rightly on forums and generally the Internet that 100scopes previews are slow, combined with the fact that we now have the left click showing the preview by default frustrate a lot of users. On my beefy machine (i7, 8G of rams), the preview for an application takes 3/4s to show, you can't do anything meanwhile as there is no button to launch the application (because you didn't double click, just left click and thought "argh, I should have double click"). Because of this, we are making the 1st landing of 100 scopes experience bad and we should fix it (at least, in that applicatoin lens) by either preloading the software-center-dbus (/usr/share/software- center/software-center-dbus) daemon (we can't have it always running as it's taking over 100MB of memory) when hovering an app lens result, or when it's the first result (so can be directly triggered by pressing [Enter]) ** Affects: unity-lens-applications (Ubuntu) Importance: Medium Status: Confirmed ** Affects: software-center (Ubuntu) Importance: Critical Status: Won't Fix ** Tags: 100scopes scopes-s u1-notrack -- Previews for applications are really slow to display anything https://bugs.launchpad.net/bugs/1192081 You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1972129] [NEW] user account show different users than "Users and Groups"
You have been subscribed to a public bug: upgraded from 21.10 to 22.04. Upgrade seemed to require creating a new (admin) id, which I did. When I now login the new account name is displayed but I have to list other users to be able to login with my pre-upgrade account. Going to system settings -> User Accounts shows only the new account. Once logged in, invoking "Users & Groups" shows both new id and pre-upgrade user account. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 8 16:30:27 2022 InstallationDate: Installed on 2020-07-18 (659 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago) VarLogDistupgradeTermlog: ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug dist-upgrade jammy -- user account show different users than "Users and Groups" https://bugs.launchpad.net/bugs/1972129 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 245.4-4ubuntu3.16 --- systemd (245.4-4ubuntu3.16) focal; urgency=medium [ Dan Streetman ] * d/p/lp1946388-sd-journal-don-t-check-namespaces-if-we-have-no-name.patch: Avoid journalctl segfault (LP: #1946388) [ Jeremy Szu ] * Add a allowlist to unblock intel-hid on new HP machines (LP: #1955997) Author: Jeremy Szu File: debian/patches/lp1955997-add-a-allowlist-to-unblock-intel-hid-on-HP-mach.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=88a859eaddb6c9a611fcbc44edab441aef4c4355 [ Nick Rosbrook ] * Prevent arguments from being overwritten with defaults at shutdown (LP: #1958284) File: debian/patches/lp1958284-core-move-reset_arguments-to-the-end-of-main-s-finish.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e61052bd1f20bcc54e7417542c6d445cf5040f56 [ Lukas Märdian ] * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) Author: Lukas Märdian File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 -- Nick Rosbrook Wed, 23 Mar 2022 09:29:33 -0400 ** Changed in: systemd (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 248.3-1ubuntu8.5 --- systemd (248.3-1ubuntu8.5) impish; urgency=medium * debian/tests/boot-and-services: Ignore failed snap mount units in test_no_failed (LP: #1967576) systemd (248.3-1ubuntu8.4) impish; urgency=medium [ Lukas Märdian ] * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) Author: Lukas Märdian File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f79535077473902bad911dc2652a2fff4066fa30 * Don't override Ubuntu's default sysctl values (LP: #1962038) Author: Lukas Märdian File: debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3ba2764d8f77e616461c9722923f685fad79f8c6 systemd (248.3-1ubuntu8.3) impish; urgency=medium [ Jeremy Szu ] * Add a allowlist to unblock intel-hid on new HP machines (LP: #1955997) Author: Jeremy Szu File: debian/patches/lp1955997-add-a-allowlist-to-unblock-intel-hid-on-HP-mach.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=554d46e6a6ab80befd424ead7ffa8e6f993b5f66 -- Nick Rosbrook Fri, 01 Apr 2022 16:39:25 -0400 ** Changed in: systemd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: Fix Released Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Merge proposal linked: https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/417577 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: New Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: New Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
This bug was fixed in the package systemd - 249.10-0ubuntu2 --- systemd (249.10-0ubuntu2) jammy; urgency=medium * Fix deadlock between pid1 and dbus-daemon (LP: #1871538) File: debian/patches/pid1-set-SYSTEMD_NSS_DYNAMIC_BYPASS-1-env-var-for-dbus-da.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=100a7bfc2d0f82c3afbede04a022c655529cffac * Don't override Ubuntu's default sysctl values (LP: #1962038) File: debian/patches/debian/UBUNTU-Don-t-override-Ubuntu-s-default-sysctl-values-LP-1962038.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b10cdb7da3539b3a3c3e619b470a75c83e46ef11 -- Lukas Märdian Tue, 08 Mar 2022 14:58:00 +0100 ** Changed in: systemd (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Invalid Status in gnome-shell source package in Focal: Invalid Status in systemd source package in Focal: New Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Invalid Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Won't Fix Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Invalid Status in gnome-shell source package in Impish: Invalid Status in systemd source package in Impish: New Status in accountsservice source package in Jammy: Invalid Status in dbus source package in Jammy: Invalid Status in gnome-shell source package in Jammy: Invalid Status in systemd source package in Jammy: Fix Released Bug description: [Impact] * There's currently a deadlock between PID 1 and dbus-daemon: in some cases dbus-daemon will do NSS lookups (which are blocking) at the same time PID 1 synchronously blocks on some call to dbus-daemon (e.g. `GetConnectionUnixUser` DBus call). Let's break that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon, which will disable synchronously blocking varlink calls from nss-systemd to PID 1. * This can lead to delayed boot times * It can also lead to dbus-daemon being killed/re-started, taking down other services with it, like GDM, killing user sessions on the way (e.g. on installing updates) [Test Plan] * This bug is really hard to reproduce, as can be seen from the multi-year long discussion at https://github.com/systemd/systemd/issues/15316 * Canonical's CPC team has the ability to reproduce this issue (with a relatively high probability) in their Azure test environment, due to the specific setup they are using * So our test plan is to ask CPC (@gjolly) for confirmation if the issue is fixed. [Where problems could occur] * This fix touches the communication between systemd and dbus daemon, especially the NSS lookup, so if something is broken the (user-)name resolution could be broken. * As a workaround dbus-daemon could be replaced by dbus-broker, which never showed this issue or the behaviour could be changed back by using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this: #/etc/systemd/system/dbus.service.d/override.conf [Service] Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0 [Other Info] * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552 === Original Description === This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system):
[Dx-packages] [Bug 1950484] Re: Adding an admin user a Gnome Control Center should set the right groups
This bug was fixed in the package accountsservice - 0.6.55-3ubuntu4 --- accountsservice (0.6.55-3ubuntu4) jammy; urgency=medium * debian/patches/git_new_meson.patch: - include git patch to fix the build with the new meson -- Sebastien Bacher Tue, 25 Jan 2022 11:20:15 +0100 ** Changed in: accountsservice (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1950484 Title: Adding an admin user a Gnome Control Center should set the right groups Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Jammy: Fix Released Bug description: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1950484/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1950484] [NEW] Adding an admin user a Gnome Control Center should set the right groups
You have been subscribed to a public bug: Currently when installing Ubuntu , the default admin belongs to several essential groups : adm cdrom sudo dip plugdev lpadmin lxd sambashare But when adding a user from GCC , the new admin user will only belong to : sudo This leads that the second admin cannot add printers and so on... This is observed on a clean 20.04.3 install ** Affects: accountsservice (Ubuntu) Importance: High Assignee: Sebastien Bacher (seb128) Status: Fix Committed ** Affects: accountsservice (Ubuntu Jammy) Importance: High Assignee: Sebastien Bacher (seb128) Status: Fix Committed -- Adding an admin user a Gnome Control Center should set the right groups https://bugs.launchpad.net/bugs/1950484 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1948882] [NEW] PulseEffects does not properly initialize on startup
You have been subscribed to a public bug: In KUbuntu 21.10, PulseEffects no longer initializes its effects chain on startup. I usually use only Equalizer, so when I log into KDE, this equalizer does not get activated. To ativate it I need (i) start PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This is rarher annoying sequence that I have to repeat each time I login. Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just worked immediately after logging in, without any additional actions. I would expect the same behaviour in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseeffects 4.8.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Oct 27 02:56:47 2021 InstallationDate: Installed on 2017-04-03 (1667 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: pulseeffects UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago) ** Affects: d-conf (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish third-party-packages -- PulseEffects does not properly initialize on startup https://bugs.launchpad.net/bugs/1948882 You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1945969] Re: Update Vala to 0.52.6 in Impish
This bug was fixed in the package libunity - 7.1.4+19.04.20190319-6 --- libunity (7.1.4+19.04.20190319-6) unstable; urgency=medium * debian/control: - use a maintainer email which isn't a moderated mailinglist (Closes: #988294) [ Lukas Märdian ] * Fix FTBFS with new valac 0.52 (LP: #1945969) * remove debian/patches for real, it isn't used by the current packaging -- Sebastien Bacher Wed, 13 Oct 2021 17:20:37 +0200 ** Changed in: libunity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1945969 Title: Update Vala to 0.52.6 in Impish Status in libunity package in Ubuntu: Fix Released Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: In Progress Status in vala source package in Impish: Fix Released Bug description: The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1555181] Re: indicator-application 12.10.1 don't is displayed in the notification bar
[Expired for indicator-application (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-application (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1555181 Title: indicator-application 12.10.1 don't is displayed in the notification bar Status in indicator-application package in Ubuntu: Expired Bug description: no applications indicator is displayed in the notification bar ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-application 12.10.1+14.04.20140407-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-62.83~14.04.1-generic 3.16.7-ckt23 Uname: Linux 3.16.0-62-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: MATE Date: Wed Mar 9 16:14:46 2016 InstallationDate: Installed on 2016-01-21 (47 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS i386 (20150323) SourcePackage: indicator-application UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1555181/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1772657] Re: Indicator Applet Complete always crashes when you log into Ubuntu Mate 18.04 and 20.04
[Expired for indicator-applet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-applet (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1772657 Title: Indicator Applet Complete always crashes when you log into Ubuntu Mate 18.04 and 20.04 Status in Ubuntu MATE: Expired Status in indicator-applet package in Ubuntu: Expired Bug description: Every time I log into my account in Ubuntu Linux MATE 18.04 The indicator applet complete crashes (Screen saving of the crash and applet included). Its a minor bug if you choose "Reload" the applet reappears and works just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1772657/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1772657] Re: Indicator Applet Complete always crashes when you log into Ubuntu Mate 18.04 and 20.04
[Expired for Ubuntu MATE because there has been no activity for 60 days.] ** Changed in: ubuntu-mate Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1772657 Title: Indicator Applet Complete always crashes when you log into Ubuntu Mate 18.04 and 20.04 Status in Ubuntu MATE: Expired Status in indicator-applet package in Ubuntu: Expired Bug description: Every time I log into my account in Ubuntu Linux MATE 18.04 The indicator applet complete crashes (Screen saving of the crash and applet included). Its a minor bug if you choose "Reload" the applet reappears and works just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1772657/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1798508] Re: indicator applet complete - logout button fails with multiple users
[Expired for indicator-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-session (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1798508 Title: indicator applet complete - logout button fails with multiple users Status in Ubuntu MATE: Expired Status in indicator-session package in Ubuntu: Expired Bug description: install new ubuntu mate 18.04 enable mutiny in mate tweaks setup 4 users login as one user switch users via indicator applet complete switch back to first user via indicator applet complete log out first user log in as any other user logout button in indicator applet complete no longer works for this user -also logged out users appear to be still logged via a checkbox beside the logged out user name using a system menu does work only way to restore correct behavior of logout button is to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1798508/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1798508] Re: indicator applet complete - logout button fails with multiple users
[Expired for Ubuntu MATE because there has been no activity for 60 days.] ** Changed in: ubuntu-mate Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1798508 Title: indicator applet complete - logout button fails with multiple users Status in Ubuntu MATE: Expired Status in indicator-session package in Ubuntu: Expired Bug description: install new ubuntu mate 18.04 enable mutiny in mate tweaks setup 4 users login as one user switch users via indicator applet complete switch back to first user via indicator applet complete log out first user log in as any other user logout button in indicator applet complete no longer works for this user -also logged out users appear to be still logged via a checkbox beside the logged out user name using a system menu does work only way to restore correct behavior of logout button is to reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1798508/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1043574] Re: cinnamon support feature request
[Expired for indicator-applet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-applet (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1043574 Title: cinnamon support feature request Status in Indicator Applet: Incomplete Status in indicator-applet package in Ubuntu: Expired Bug description: I have some doubts on gnome fallback mode long term support in future gnome versions, and cinnamon and/or mate seems like sensible alternative. Except it has no global app menu i'm so used to. Hence i hope for indicator-applet / indicator-applet-appmenu to be ported to cinnamon. Judging by several easily googled out threads, i'm far from only one missing out mac style menu on panel in cinnamon. Can it be added? To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1043574/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1406687] Re: Missing icon for mouse battery power
[Expired for indicator-power (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-power (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1406687 Title: Missing icon for mouse battery power Status in indicator-power package in Ubuntu: Expired Bug description: I am using Ubuntu MATE 14.04. have a Logitech wireless mouse. The battery icon for the mouse is missing in the panel. It shows up as a white rectangle with a red circle. I have attached screenshots. Admittedly, this might not be a MATE buA as this bug report shows: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1144504 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1406687/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1739908] Re: Ubuntu Software Center has low contrast with some themes
[Expired for gtk2-engines (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtk2-engines (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to human-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1739908 Title: Ubuntu Software Center has low contrast with some themes Status in gtk2-engines package in Ubuntu: Expired Status in human-theme package in Ubuntu: Expired Status in mate-themes package in Ubuntu: Expired Status in software-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS with MATE DE 2. Set theme which you like (for example, BlackMATE, DarkRoom, High Contrast Inverse, High Contrast, Human Clearlooks, Human) 3. Launch Ubuntu Software Center and start search for application Expected results: Ubuntu Software Center is usable, its interface has normal contrast (user can read text, click buttons and so on) Actual results: Ubuntu Software Center is unusable, its interface has very low contrast (user can not read text, click buttons and so on) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center 16.01+16.04.20160420 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CurrentDesktop: MATE Date: Sat Dec 23 22:46:18 2017 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. PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1739908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1739908] Re: Ubuntu Software Center has low contrast with some themes
[Expired for software-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: software-center (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to human-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1739908 Title: Ubuntu Software Center has low contrast with some themes Status in gtk2-engines package in Ubuntu: Expired Status in human-theme package in Ubuntu: Expired Status in mate-themes package in Ubuntu: Expired Status in software-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS with MATE DE 2. Set theme which you like (for example, BlackMATE, DarkRoom, High Contrast Inverse, High Contrast, Human Clearlooks, Human) 3. Launch Ubuntu Software Center and start search for application Expected results: Ubuntu Software Center is usable, its interface has normal contrast (user can read text, click buttons and so on) Actual results: Ubuntu Software Center is unusable, its interface has very low contrast (user can not read text, click buttons and so on) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center 16.01+16.04.20160420 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CurrentDesktop: MATE Date: Sat Dec 23 22:46:18 2017 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. PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1739908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1739908] Re: Ubuntu Software Center has low contrast with some themes
[Expired for human-theme (Ubuntu) because there has been no activity for 60 days.] ** Changed in: human-theme (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to human-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1739908 Title: Ubuntu Software Center has low contrast with some themes Status in gtk2-engines package in Ubuntu: Expired Status in human-theme package in Ubuntu: Expired Status in mate-themes package in Ubuntu: Expired Status in software-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS with MATE DE 2. Set theme which you like (for example, BlackMATE, DarkRoom, High Contrast Inverse, High Contrast, Human Clearlooks, Human) 3. Launch Ubuntu Software Center and start search for application Expected results: Ubuntu Software Center is usable, its interface has normal contrast (user can read text, click buttons and so on) Actual results: Ubuntu Software Center is unusable, its interface has very low contrast (user can not read text, click buttons and so on) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center 16.01+16.04.20160420 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CurrentDesktop: MATE Date: Sat Dec 23 22:46:18 2017 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. PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1739908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1739908] Re: Ubuntu Software Center has low contrast with some themes
[Expired for mate-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to human-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1739908 Title: Ubuntu Software Center has low contrast with some themes Status in gtk2-engines package in Ubuntu: Expired Status in human-theme package in Ubuntu: Expired Status in mate-themes package in Ubuntu: Expired Status in software-center package in Ubuntu: Expired Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS with MATE DE 2. Set theme which you like (for example, BlackMATE, DarkRoom, High Contrast Inverse, High Contrast, Human Clearlooks, Human) 3. Launch Ubuntu Software Center and start search for application Expected results: Ubuntu Software Center is usable, its interface has normal contrast (user can read text, click buttons and so on) Actual results: Ubuntu Software Center is unusable, its interface has very low contrast (user can not read text, click buttons and so on) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center 16.01+16.04.20160420 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CurrentDesktop: MATE Date: Sat Dec 23 22:46:18 2017 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. PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1739908/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
[Expired for ubuntu-mate-settings (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in indicator-application package in Ubuntu: Invalid Status in mate-indicator-applet package in Ubuntu: Expired Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Expired Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: 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. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 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 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1754458/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1754458] Re: nm-applet symbol not displayed on mate (18.04)
[Expired for mate-indicator-applet (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mate-indicator-applet (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-application in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in indicator-application package in Ubuntu: Invalid Status in mate-indicator-applet package in Ubuntu: Expired Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Expired Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: 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. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 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 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1754458/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1936736] Re: User switching does not work: my_switch_to_username: assertion 'p->dm_seat != NULL' failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1936736 Title: User switching does not work: my_switch_to_username: assertion 'p->dm_seat != NULL' failed Status in indicator-session package in Ubuntu: Confirmed Bug description: Actual behavior: Switching users from the indicator menu does nothing. Only this is logged in /var/log/syslog: Jul 17 23:11:01 cherna indicator-sessi[5227]: my_switch_to_username: assertion 'p->dm_seat != NULL' failed Expected behavior upon selecting another user in the indicator menu: Switches to a screen with a A password prompt. Ubuntu 20.04.2 LTS indicator-session 17.3.20+19.10.20190921-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-session 17.3.20+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119 Uname: Linux 5.4.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Jul 17 23:34:43 2021 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-29 (2910 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) SourcePackage: indicator-session UpgradeStatus: Upgraded to focal on 2021-07-10 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1936736/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubuntu-seeds/+git/platform/+merge/408418 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in D-Bus: Unknown Status in systemd: New Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Incomplete Status in gnome-shell source package in Focal: Invalid Status in accountsservice source package in Groovy: Invalid Status in dbus source package in Groovy: Incomplete Status in gnome-shell source package in Groovy: Invalid Status in accountsservice source package in Hirsute: Invalid Status in dbus source package in Hirsute: Incomplete Status in gnome-shell source package in Hirsute: Invalid Status in accountsservice source package in Impish: Invalid Status in dbus source package in Impish: Incomplete Status in gnome-shell source package in Impish: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service:
[Dx-packages] [Bug 1503930] Re: zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zeitgeist (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to zeitgeist in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1503930 Title: zeitgeist-datahub "Freezing of tasks failed after 20.005 seconds" Status in zeitgeist package in Ubuntu: Confirmed Bug description: My system no longer properly goes to sleep. The logs are filled with variants of: [114631.282599] PM: Syncing filesystems ... done. [114631.328752] PM: Preparing system for mem sleep [114631.896631] Freezing user space processes ... [114651.913199] Freezing of tasks failed after 20.005 seconds (1 tasks refusing to freeze, wq_busy=0): [114651.913321] zeitgeist-datah D 88033fc33180 0 4659 4142 0x0004 [114651.913325] 8802d6a05aa8 0086 8802f3c4c800 8802d6a05fd8 [114651.913328] 00013180 00013180 8802f3c4c800 88032a3bbe28 [114651.913330] 8800b0366000 8802d6a05ad0 88032a3bbf08 88032a3bbe28 [114651.91] Call Trace: [114651.913340] [] schedule+0x29/0x70 [114651.913345] [] __fuse_request_send+0x115/0x280 [114651.913350] [] ? prepare_to_wait_event+0x100/0x100 [114651.913352] [] fuse_request_send+0x12/0x20 [114651.913355] [] fuse_dentry_revalidate+0x194/0x350 [114651.913360] [] lookup_fast+0x26d/0x2c0 [114651.913363] [] link_path_walk+0x1a3/0x880 [114651.913365] [] ? enqueue_entity+0x2ad/0xbb0 [114651.913368] [] path_lookupat+0x5b/0x790 [114651.913372] [] ? ttwu_do_wakeup+0x19/0xc0 [114651.913376] [] ? kmem_cache_alloc+0x35/0x1e0 [114651.913378] [] ? getname_flags+0x4f/0x190 [114651.913381] [] filename_lookup+0x2b/0xc0 [114651.913384] [] user_path_at_empty+0x54/0x90 [114651.913388] [] ? from_kgid_munged+0x12/0x20 [114651.913390] [] ? cp_new_stat+0x13d/0x160 [114651.913393] [] user_path_at+0x11/0x20 [114651.913395] [] vfs_fstatat+0x50/0xa0 [114651.913397] [] SYSC_newstat+0x1f/0x40 [114651.913400] [] SyS_newstat+0xe/0x10 [114651.913403] [] system_call_fastpath+0x1a/0x1f [114651.913432] [114651.913433] Restarting tasks ... done. and the occasional [46466.515860] INFO: task zeitgeist-datah:4659 blocked for more than 120 seconds. [46466.515868] Tainted: P OX 3.13.0-63-generic #103-Ubuntu [46466.515870] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [46466.515873] zeitgeist-datah D 88033fc33180 0 4659 4142 0x0004 [46466.515880] 8802d6a05aa8 0086 8802f3c4c800 8802d6a05fd8 [46466.515886] 00013180 00013180 8802f3c4c800 88032a3bbe28 [46466.515890] 8800b0366000 8802d6a05ad0 88032a3bbf08 88032a3bbe28 [46466.515895] Call Trace: [46466.515906] [] schedule+0x29/0x70 [46466.515913] [] __fuse_request_send+0x115/0x280 [46466.515922] [] ? prepare_to_wait_event+0x100/0x100 [46466.515926] [] fuse_request_send+0x12/0x20 [46466.515932] [] fuse_dentry_revalidate+0x194/0x350 [46466.515939] [] lookup_fast+0x26d/0x2c0 [46466.515944] [] link_path_walk+0x1a3/0x880 [46466.515949] [] ? enqueue_entity+0x2ad/0xbb0 [46466.515954] [] path_lookupat+0x5b/0x790 [46466.515960] [] ? ttwu_do_wakeup+0x19/0xc0 [46466.515966] [] ? kmem_cache_alloc+0x35/0x1e0 [46466.515971] [] ? getname_flags+0x4f/0x190 [46466.515976] [] filename_lookup+0x2b/0xc0 [46466.515981] [] user_path_at_empty+0x54/0x90 [46466.515988] [] ? from_kgid_munged+0x12/0x20 [46466.515992] [] ? cp_new_stat+0x13d/0x160 [46466.515997] [] user_path_at+0x11/0x20 [46466.516001] [] vfs_fstatat+0x50/0xa0 [46466.516005] [] SYSC_newstat+0x1f/0x40 [46466.516010] [] SyS_newstat+0xe/0x10 [46466.516015] [] system_call_fastpath+0x1a/0x1f 6831104 Oct 6 16:57 activity.sqlite 3271680 Sep 17 2014 activity.sqlite.bck 163840 Oct 7 17:15 activity.sqlite-shm 288943064 Oct 7 17:15 activity.sqlite-wal 322 Nov 10 2013 datasources.pickle 4096 Oct 7 14:03 fts.index Going to settings and selecting "Clear usage data" and "All time" resulted in no change of file sizes and no improvement to suspend. Turning "record file and usage" to "off" left the zeitgeist-datahub running. A "kill -9" of the datahub process results in no change (the task does not die) # ps -F 4659 UIDPID PPID CSZ RSS PSR STIME TTY STAT TIME CMD xx 4659 4142 0 105023 11872 1 Oct06 ?D 0:33 zeitgeist-datahub See also http://linuxaria.com/howto/how-to-remove-zeitgeist-in-ubuntu-and-why To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1503930/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net
[Dx-packages] [Bug 1697412] Re: "Show my name" is no longer working in 17.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-tweak-tool (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1697412 Title: "Show my name" is no longer working in 17.04 Status in Unity Tweak Tool: New Status in indicator-session package in Ubuntu: Confirmed Status in unity-tweak-tool package in Ubuntu: Confirmed Bug description: The panel option "Show my name" in unity-tweak-tool is not working in Ubuntu 17.04 "gsettings set com.canonical.indicator.session show-real-name-on-panel true" which is afaik what utt is doing also has no effect. Same goes for the "Show my login name in the menu bar" option in the system settings. Last time when I was using it in 16.04 it was working so I guess something has changed since then. I'm using the latest version of utt 0.0.7ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-tweak-tool/+bug/1697412/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1697412] Re: "Show my name" is no longer working in 17.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1697412 Title: "Show my name" is no longer working in 17.04 Status in Unity Tweak Tool: New Status in indicator-session package in Ubuntu: Confirmed Status in unity-tweak-tool package in Ubuntu: Confirmed Bug description: The panel option "Show my name" in unity-tweak-tool is not working in Ubuntu 17.04 "gsettings set com.canonical.indicator.session show-real-name-on-panel true" which is afaik what utt is doing also has no effect. Same goes for the "Show my login name in the menu bar" option in the system settings. Last time when I was using it in 16.04 it was working so I guess something has changed since then. I'm using the latest version of utt 0.0.7ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity-tweak-tool/+bug/1697412/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1888934] Re: Indicator is shown twice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1888934 Title: Indicator is shown twice Status in indicator-bluetooth package in Ubuntu: Confirmed Bug description: See the screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 12:03:34 2020 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1888934/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1924594] Re: libgmock-dev build dependency needed
This bug was fixed in the package indicator-power - 12.10.6+17.10.20170829.1-0ubuntu7 --- indicator-power (12.10.6+17.10.20170829.1-0ubuntu7) hirsute; urgency=medium * Add libgmock-dev build dependency (LP: #1924594) -- Heather Ellsworth Thu, 15 Apr 2021 16:21:03 + ** Changed in: indicator-power (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1924594 Title: libgmock-dev build dependency needed Status in indicator-power package in Ubuntu: Fix Released Bug description: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1924594/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1924594] Re: libgmock-dev build dependency needed
** Branch linked: lp:indicator-power -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1924594 Title: libgmock-dev build dependency needed Status in indicator-power package in Ubuntu: Fix Committed Bug description: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1924594/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1924594] Re: libgmock-dev build dependency needed
** Merge proposal linked: https://code.launchpad.net/~hellsworth/ubuntu/+source/indicator-power/+git/indicator-power/+merge/401240 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1924594 Title: libgmock-dev build dependency needed Status in indicator-power package in Ubuntu: New Bug description: indicator-power no longer builds. make[3]: *** No rule to make target 'tests/gmock/libgmock_main.a', needed by 'tests/test-notify'. Stop. The build failure: https://launchpadlibrarian.net/532498126 /buildlog_ubuntu-hirsute-amd64.indicator- power_12.10.6+17.10.20170829.1-0ubuntu6_BUILDING.txt.gz If you install libgmock-dev in the build environment first, it fixes the build problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1924594/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1908051] Re: error: Argument 7: Cannot convert from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
[Expired for libunity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: libunity (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libunity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1908051
Title:
error: Argument 7: Cannot convert from `void
Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
Status in libunity package in Ubuntu:
Expired
Bug description:
make returns:
unity-protocol.vapi:242.4-242.43: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint
view_type) throws GLib.IOError;
unity-launcher.vala:61.5-61.42: warning: DBus methods are recommended to
throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public HashTable query ()
^^
unity-scope-channel.vala:312.33-312.50: error: Argument 7: Cannot convert
from `void Unity.Internal.ScopeChannel.OwnerWatcher.owner_changed
(GLib.DBusConnection, string, string, string, string, GLib.Variant)' to `void
GLib.DBusSignalCallback (GLib.DBusConnection, string?, string, string, string,
GLib.Variant)'
DBusSignalFlags.NONE, this.owner_changed);
^^
unity-scope-channel.vala:269.9-269.52: warning: Access to possible `null'.
Perform a check or use an unsafe cast.
(transfer_model as DiffModel).commit_changes ();
unity-synchronizer.vala:93.5-93.18: warning: `GLib.HashTable.add' has been
deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:434.7-434.28: warning:
`GLib.HashTable.add' has been deprecated since vala-0.26. Use GenericSet.add
unity-aggregator-scope-private.vala:606.7-606.72: warning: Access to possible
`null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByField).map_subscope_categories
(scope_id, proxy.categories_model);
^^
unity-aggregator-scope-private.vala:1308.7-1308.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
scope_id);
unity-aggregator-scope-private.vala:1352.7-1352.66: warning: Access to
possible `null'. Perform a check or use an unsafe cast.
(category_merger as CategoryMergerByScope).add_scope_mapping (owner,
master_scope_id);
unity-scope-loader.vala:41.49-41.69: warning: `GLib.ModuleFlags.BIND_LAZY'
has been deprecated since vala-0.46. Use LAZY
unity-sound-menu-mpris.vala:475.5-475.27: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void raise() throws IOError{
^^^
unity-sound-menu-mpris.vala:580.5-580.32: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void play_pause() throws IOError
unity-sound-menu-mpris.vala:585.5-585.26: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void next() throws IOError
^^
unity-sound-menu-mpris.vala:590.5-590.30: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void previous() throws IOError
^^
unity-sound-menu-mpris.vala:709.5-709.39: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async void activate_playlist (ObjectPath playlist_id) throws
IOError
^^^
unity-sound-menu-mpris.vala:714.5-714.48: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public async PlaylistDetails[] get_playlists (uint32 index,
unity-sound-menu-mpris.vala:407.5-407.55: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnableTrackSpecificItems (ObjectPath
object_path, string desktop_id) throws IOError;
^^^
unity-sound-menu-mpris.vala:408.5-408.56: warning: DBus methods are
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void EnablePlayerSpecificItems
[Dx-packages] [Bug 1268210] Re: unity-scopes-runner: Typo in package description: "scoped"
This bug was fixed in the package libunity - 7.1.4+19.04.20190319-5 --- libunity (7.1.4+19.04.20190319-5) unstable; urgency=medium * debian/control: - fix typo in the Conflicts keyword * extras,src/Makefile.am: - set --shared-library valac option so the generated gir which is needed for the correct depends to be created * remove debian/patches which isn't use by the current packaging, it was an indication of the changes applied to the source but those are commited directly to the vcs now -- Sebastien Bacher Mon, 01 Feb 2021 18:01:36 +0100 ** Changed in: libunity (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1268210 Title: unity-scopes-runner: Typo in package description: "scoped" Status in Package Descriptions for Ubuntu: Triaged Status in libunity: Fix Committed Status in libunity package in Ubuntu: Fix Released Bug description: Package: unity-scopes-runner Version: 7.1.3+14.04.20131106-0ubuntu1 Hello, The package description contains a small typo, I think: The scope runner is a handy tool for wrapping on a desktop the various scoped installed on the system. Should be: The scope runner is a handy tool for wrapping on a desktop the various scopes installed on the system. in the string #16945 https://translations.launchpad.net/ddtp-ubuntu/trusty/+pots/ddtp-ubuntu-main/fr/16945 Regards, Pascal To manage notifications about this bug go to: https://bugs.launchpad.net/ddtp-ubuntu/+bug/1268210/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
This bug was fixed in the package libappindicator - 12.10.1+18.04.20200408.1-0ubuntu1 --- libappindicator (12.10.1+18.04.20200408.1-0ubuntu1) bionic; urgency=medium [ Paul G ] * app-indicator: Don't pass unexpected parameter to ::new-icon-theme-path signal (LP: #1867996) [ Ash Holland ] * app-indicator: Only check for item numbers when iterating array (LP: #1867996) -- Marco Trevisan (Treviño) Wed, 08 Apr 2020 18:59:25 + ** Changed in: libappindicator (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Released Status in libappindicator source package in Bionic: Fix Released Bug description: [ Impact ] Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1910521] Re: libappindicator breaks left-mouse actions for most applications
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libappindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1910521 Title: libappindicator breaks left-mouse actions for most applications Status in libappindicator package in Ubuntu: Confirmed Bug description: Hello, because GTK will drop tray icon support in version 4, many projects switch to libappindicator instead. Some are network-manager-applet, blueman-tray and electron (affecting all electron apps). The latter 2 automatically use libappindicator if it's available in the system. For most applications, with libappindicator the tray icon behavior is broken (at least on archlinux with xfce4 and libappindicator-gtk3): * left mouse button triggers the context menu rather than the left-mouse-button action * the context menu is located beneath the mouse button, so when the mouse is released, the action is performed (in most cases "exit application"). Since the web is full of issue reports about this, I'm, pretty sure it's an issue in libappindicator itself than in every single application that uses it. IMO this is a critical issue, especially for a library that provides tray support to applications. Kind regards, Michael. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1910521/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1901690] Re: Ubuntu20.04 system permissions problem of networkmanager
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz-plugins-main (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1901690 Title: Ubuntu20.04 system permissions problem of networkmanager Status in compiz-plugins-main package in Ubuntu: Confirmed Bug description: [Issue description] When module restart or laptop restart then trying to connecting to modem through UI which sometimes will encounter can’t connection modem successful (Internet APN message had sent to modem correctly and we didn’t see any fail message on that), we suspect this is Ubuntu 20.04 OS causing this issue as below screenshot due to Ubuntu 20.04 OS may merge some kind of authority management on thatThis issue can be using re-creative an internet APN way to resolve then do not use original internet APN and we only faced 2~3 times until now under “ONLY” Ubuntu 20.04 OS [Issue Happening OS version] Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz-plugins-main/+bug/1901690/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ayatana-indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1766108 Title: Battery indicator crashes when unchecking "Show Percentage in Menu Bar" Status in Ubuntu MATE: New Status in ayatana-indicator-power package in Ubuntu: Confirmed Status in indicator-power package in Ubuntu: Confirmed Status in mate-indicator-applet package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Click on the battery indicator. 2. Click "Show Percentage on Menu Bar" to enable it. 3. Do it again to disable it. 4. Battery indicator disappears Output from dmesg: [ 613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000] [ 749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000] [ 775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000] [ 816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000] [ 841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1766108/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu12~20.04.2 --- accountsservice (0.6.55-0ubuntu12~20.04.2) focal; urgency=medium * debian/patches/0010-set-language.patch: - Don't dismiss C.UTF-8 as an invalid locale name (LP: #1873678) -- Gunnar Hjalmarsson Sat, 10 Oct 2020 21:31:00 +0200 ** Changed in: accountsservice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1873678 Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Released Bug description: [Impact] accountsservice includes a function for checking the validity of locales, and it incorrectly considers "C.UTF-8" to be invalid. It leads to incorrect behavior under certain conditions and also a crash if the function was triggered from language-selector-gnome. Even if this only makes a difference in special corner cases, it happens often enough to justify this SRU: https://errors.ubuntu.com/?release=Ubuntu%2020.04=language- selector=year (It's the top ranked crash type in the list.) The version in focal-proposed fixes the issue. [Test case] Make a fresh install of Ubuntu 20.04 (a VM works fine) Once logged in: * Install accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed * Open /etc/default/locale for editing, replace its contents with the single line: LANG=C.UTF-8 and reboot. Open Language Support and change language (drag any language above the "English" item) Open ~/.pam_environment and find that e.g. LANG is now the locale representing the language you selected, while e.g. LC_TIME is set to "C.UTF-8". [Regression risk] This is a oneliner which white list "C.UTF-8" as a valid locale name. I can't think of a case where this would cause unexpected behavior. [Original description] USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1891740] Re: Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1891740 Title: Indicator Applet Crashes with unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Bug description: # Problem When the calendar is synced to a Google calendar that contains "task" entries, the indicator applet crashes. These entries are not shown in evolution/gnome-calendar either, so this issue might originate in some library code. # Error Message The date-time indicator crashes with the following error message when started in the terminal: Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-SpDTj1/indicator-datetime-15.10+20.04.20200217/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) # Steps to reproduce - Create a "task" in your Google calendar - Sync the Google account with the calendar using the Online Accounts application - the indicator applet will crash as soon as the data is synced # Version I am using the indicator applet version 15.10+20.04.20200217-0ubuntu1 on Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1891740/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1873678] Re: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu13 --- accountsservice (0.6.55-0ubuntu13) groovy; urgency=medium * debian/patches/0010-set-language.patch: - Don't dismiss C.UTF-8 as an invalid locale name (LP: #1873678) -- Gunnar Hjalmarsson Fri, 09 Oct 2020 15:08:15 +0200 ** Changed in: accountsservice (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1873678 Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: In Progress Bug description: [Impact] accountsservice includes a function for checking the validity of locales, and it incorrectly considers "C.UTF-8" to be invalid. It leads to incorrect behavior under certain conditions and also a crash if the function was triggered from language-selector-gnome. Even if this only makes a difference in special corner cases, it happens often enough to justify this SRU: https://errors.ubuntu.com/?release=Ubuntu%2020.04=language- selector=year (It's the top ranked crash type in the list.) The version in focal-proposed fixes the issue. [Test case] Make a fresh install of Ubuntu 20.04 (a VM works fine) Once logged in: * Install accountsservice, gir1.2-accountsservice-1.0 and libaccountsservice0 from focal-proposed * Open /etc/default/locale for editing, replace its contents with the single line: LANG=C.UTF-8 and reboot. Open Language Support and change language (drag any language above the "English" item) Open ~/.pam_environment and find that e.g. LANG is now the locale representing the language you selected, while e.g. LC_TIME is set to "C.UTF-8". [Regression risk] This is a oneliner which white list "C.UTF-8" as a valid locale name. I can't think of a case where this would cause unexpected behavior. [Original description] USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1873678/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1798508] [NEW] indicator applet complete - logout button fails with multiple users
You have been subscribed to a public bug: install new ubuntu mate 18.04 enable mutiny in mate tweaks setup 4 users login as one user switch users via indicator applet complete switch back to first user via indicator applet complete log out first user log in as any other user logout button in indicator applet complete no longer works for this user -also logged out users appear to be still logged via a checkbox beside the logged out user name using a system menu does work only way to restore correct behavior of logout button is to reboot ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- indicator applet complete - logout button fails with multiple users https://bugs.launchpad.net/bugs/1798508 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1873678] [NEW] gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name
You have been subscribed to a public bug: USB live disk (20.04 beta) ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.203 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Sun Apr 19 17:07:26 2020 ExecutablePath: /usr/bin/gnome-language-selector InterpreterPath: /usr/bin/python3.8 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gnome-language-selector ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonArgs: ['/usr/bin/gnome-language-selector'] PythonDetails: N/A SourcePackage: language-selector Title: gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo ** Affects: accountsservice (Ubuntu) Importance: Medium Assignee: Gunnar Hjalmarsson (gunnarhj) Status: Fix Committed ** Tags: amd64 apport-crash focal -- gnome-language-selector crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.Accounts.Error.Failed: 'C.UTF-8' is not a valid locale name https://bugs.launchpad.net/bugs/1873678 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1898477] Re: Old indicator items are not removed, just hidden
** Branch linked: lp:~mitya57/indicator-applet/fix-duplicate-icons.focal -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1898477 Title: Old indicator items are not removed, just hidden Status in indicator-applet package in Ubuntu: Fix Released Status in indicator-applet source package in Focal: New Bug description: [Impact] In Focal the indicator-applet (12.10.2+20.04.20200409-0ubuntu1) contains a bug that can cause duplicate icons to appear in the applet. When an application which creates a notification item is closed, then the indicator applet will just hide its item and not remove it. If the application is started again, a new item will be added to the applet, but the old item is still present (just hidden). When the panel is moved or otherwise refreshed, then all items will be made visible again, causing many duplicates. The required fix is included in https://bazaar.launchpad.net /~indicator-applet-developers/indicator- applet/trunk.14.04/revision/451 and needs to be back ported into the new SRU release. For more details see this merge request: https://code.launchpad.net/~lanoxx/indicator-applet/fix-duplicate-icons/+merge/390344 [Test Case] 1. Open an application which adds a notification item to the indicator applet. Examples for such an applications are VLC, Network Manager Applet, or Skype. 2. Close the application and reopen it. 3. Hold Alt key, then move the panel which has the indicator applet to an different edge of the screen. 4. Observe that new two icons of the respective application are visible (e.g. to VLC icons). [Regression Potential] * The regression potential is minimal. The only user of this package are the GNOME Flashback packages. The biggest impact this change could have is that indicator applet items behave incorrectly, which is not worse than the current situation. * I have tested this patch for several weeks now and not found any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1898477/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1890012] [NEW] Could not install 'systemd-shim'
You have been subscribed to a public bug: The upgrade will continue but the 'systemd-shim' package may not be in a working state. Please consider submitting a bug report about it. installed systemd-shim package post-removal script subprocess returned error exit status 2 Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Upgrade complete The upgrade has completed but there were errors during the upgrade process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Aug 2 01:05:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2020-07-17 (15 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 R2 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=744ad588-c7b1-4684-b3e5-fc7ffaef78ea ro access=v1 quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2017 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-78LMT-USB3 R2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: sex dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3R2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3R2:rvrsex:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 R2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Sat Jul 18 01:11:31 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputCypress Sem PS2/USB Browser Combo Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: systemd-shim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- Could not install 'systemd-shim' https://bugs.launchpad.net/bugs/1890012 You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1787272] Re: Administrators are not added to adm group
[Expired for accountsservice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: accountsservice (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1787272 Title: Administrators are not added to adm group Status in accountsservice package in Ubuntu: Expired Bug description: Currently administrators are only added to the sudo group. This was fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/810907, but there has likely been a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1787272/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
[Expired for dbus (Ubuntu Focal) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu Focal) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Expired Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught
[Dx-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
[Expired for dbus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: dbus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm Status in accountsservice package in Ubuntu: Invalid Status in dbus package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Invalid Status in accountsservice source package in Focal: Invalid Status in dbus source package in Focal: Expired Status in gnome-shell source package in Focal: Invalid Bug description: This morning I found my computer on the login screen. But not the one of the screen log, no a new one - so something must have crashed. Logging in again confirmed that all apps were gone and the gnome shell was brought down what seems like triggered by a background update o accountsservice. As always things are not perfectly clear :-/ The following goes *back* in time through my logs one by one. Multiple apps crashed at 06:09, but we will find later that this is a follow on issue of the underlying gnome/X/... recycling. -rw-r- 1 paelzer whoopsie 52962868 Apr 8 06:09 _usr_bin_konversation.1000.crash -rw-r- 1 paelzer whoopsie 986433 Apr 8 06:09 _usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash rdkit was failing fast and giving up (that will be a different bug, it just seems broken on my system): Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called chroot. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped privileges. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited resources. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: Resource temporarily unavailable Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time threads. Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process exited, code=exited, status=1/FAILURE Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=> Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request repeated too quickly. Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with result 'exit-code'. Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53 But that already was only triggered by a gnome restart that kicked of earlier: Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on Wayland. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session is initialized. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland Session. Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session (session: gnome-login). X was recycleing before: Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11... ... Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) systemd-logind: ReleaseControl failed: Unknown object '/org/freedesktop/login1/session/_32'. Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server terminated successfully (0). Closing log file. It seems like some internal service broke and everything that followed was a secondary issue to that: Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ... Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting. Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error response from GetNameOwner(): Connection terminated Apr 08 06:09:19 Keschdeichel ModemManager[1308]: Caught signal,
[Dx-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libical3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1848969 Title: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Status in indicator-datetime package in Ubuntu: Confirmed Status in libical3 package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 19.10, indicator-datetime 15.10+19.10.20190819.1-0ubuntu1 crashes right from the start: $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized TZID: 'Etc/Utc' (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized TZID: 'Etc/Utc' (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.457: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed [...] (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libecal-CRITICAL **: 01:46:35.458: e_cal_component_datetime_get_value: assertion 'dt != NULL' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: assertion 'I_CAL_IS_TIME (tt)' failed ** Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) Bail out! Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1807514] Re: installed systemd-shim package post-removal script subprocess returned error exit status 2
[Expired for systemd-shim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd-shim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1807514 Title: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd-shim package in Ubuntu: Expired Bug description: installed systemd-shim package post-removal script subprocess returned error exit status 2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Dec 8 17:13:53 2018 DistUpgraded: 2018-12-08 17:07:42,953 DEBUG /openCache(), new cache size 61306 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Cedar [Radeon HD 5000/6000/7350/8350 Series] [1682:3030] InstallationDate: Installed on 2014-02-15 (1757 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) MachineType: Dell Inc. Dell DXP051 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=e3337e9d-4116-4f99-b96f-8019182e5c07 ro Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-08 (0 days ago) dmi.bios.date: 01/08/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0YC523 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDXP051:pvr:rvnDellInc.:rn0YC523:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell DXP051 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-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 xserver.bootTime: Sun Nov 4 10:33:25 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1807514/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1827411] Re: With nemo-desktop it spams syslog
This bug was fixed in the package indicator-appmenu - 15.02.0+20.10.20200617.2-0ubuntu1 --- indicator-appmenu (15.02.0+20.10.20200617.2-0ubuntu1) groovy; urgency=medium [ Dmitry Shachnev ] * Depend on bamfdaemon, it is needed to fetch windows paths. (LP: #1883423) [ Khurshid Alam ] * Fix deprecation warnings; do not track menus for desktop windows. (LP: #1827411) -- Dmitry Shachnev Wed, 17 Jun 2020 15:11:51 + ** Changed in: indicator-appmenu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1827411 Title: With nemo-desktop it spams syslog Status in indicator-appmenu package in Ubuntu: Fix Released Bug description: Whenever I click desktop, it continuously posts messages to syslog window_menu_model_new: assertion 'BAMF_IS_APPLICATION(app)' failed track_menus: assertion 'IS_WINDOW_MENU(menus)' failed I am using Ubuntu 19.04 Ubuntu Unity session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1827411/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1883423] Re: no menu bar in LibreOffice
This bug was fixed in the package indicator-appmenu - 15.02.0+20.10.20200617.2-0ubuntu1 --- indicator-appmenu (15.02.0+20.10.20200617.2-0ubuntu1) groovy; urgency=medium [ Dmitry Shachnev ] * Depend on bamfdaemon, it is needed to fetch windows paths. (LP: #1883423) [ Khurshid Alam ] * Fix deprecation warnings; do not track menus for desktop windows. (LP: #1827411) -- Dmitry Shachnev Wed, 17 Jun 2020 15:11:51 + ** Changed in: indicator-appmenu (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1883423 Title: no menu bar in LibreOffice Status in indicator-appmenu package in Ubuntu: Fix Released Bug description: In Ubuntu 20.04 with GNOME Flashback session, the top menu bar (File, View etc.) is not present in LibreOffice applications (in regular GNOME Shell, the menu is present OK). There seems to be no way to make the menu appear, except of uninstalling libreoffice-gtk3 package, but then all styling from the GNOME theme is lost and LibreOffice has the "raw" X toolkit look. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1883423/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu12~20.04.1 --- accountsservice (0.6.55-0ubuntu12~20.04.1) focal; urgency=medium * Backport from groovy to focal. accountsservice (0.6.55-0ubuntu12) groovy; urgency=medium * Cherry-pick from unstable. * Add patch to not crash in the library when the daemon goes away (Closes: #948228) (LP: #1843982) -- Iain Lane Tue, 05 May 2020 17:05:26 +0100 ** Changed in: accountsservice (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() Status in accountsservice: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Fix Released Status in accountsservice package in Debian: Confirmed Bug description: [ Description ] When accountsservice's daemon is restarted - particularly when there is a user configured for auto login - it can cause code using its library to crash. This is bad because gnome-shell is one of those users which crashes. [ QA ] Configure a user for automatic login in gnome-shell. Update to this SRU, and then *restart your system*. The crash is in the library part, and so you will still see it if programs loaded the buggy version. Restarting is the easiest way to make sure you're not on it. Restart accounts-daemon.service (sudo systemctl restart accounts- daemon.service) a few times, leaving several seconds between each attempt. See that it crashes if you don't have this SRU, and doesn't if you do have it. --- Test that fast user switching still works properly. --- Take a look at the error reports listed below and hopefully see them not occurring (barring the usual noise) with the SRU. [ Regression potential ] We think this is safe - it tells clients that the daemon is away when it quits, and is back when it comes back. They should get appropriate signals to indicate this. Nevertheless, these signals are sent when they weren't before now, so that could cause problems. Watch out for errors creeping up with this SRU. We wondered upstream whether some more protections might be needed. I'm thinking that those should be *additional* safety rails around this fix, but it could actually be that more is needed and this fix isn't complete. [ Original report ] https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 14 10:29:16 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-05-24 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1883423] [NEW] no menu bar in LibreOffice
You have been subscribed to a public bug: In Ubuntu 20.04 with GNOME Flashback session, the top menu bar (File, View etc.) is not present in LibreOffice applications (in regular GNOME Shell, the menu is present OK). There seems to be no way to make the menu appear, except of uninstalling libreoffice-gtk3 package, but then all styling from the GNOME theme is lost and LibreOffice has the "raw" X toolkit look. ** Affects: indicator-appmenu (Ubuntu) Importance: Undecided Assignee: Dmitry Shachnev (mitya57) Status: New -- no menu bar in LibreOffice https://bugs.launchpad.net/bugs/1883423 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1878775] [NEW] gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_gra
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/ef271ce6e134d51dbb0fde393051bdcce3f16cf8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- gnome-shell crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from g_autoptr_cleanup_generic_gfree() from _systemd_session_is_graphical() from _find_graphical_systemd_session() https://bugs.launchpad.net/bugs/1878775 You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1874723] Re: MATE battery icon disappears when deselect "Show Time in Menu Bar"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1874723 Title: MATE battery icon disappears when deselect "Show Time in Menu Bar" Status in Ubuntu MATE: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: In the new Ubuntu MATE 20.04, with the default installation, right clicking on the battery icon in the upper right on the panel, and select either (or both) "Show Time in Menu Bar" or "Show Percentage in Menu Bar". Then, deselect the option, and the entire battery icon (not just the time or percentage) disappears from the tray/panel and can not be replaced. Or, I can not figure out how to replace it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1874723/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()
This bug was fixed in the package accountsservice - 0.6.55-0ubuntu12 --- accountsservice (0.6.55-0ubuntu12) groovy; urgency=medium * Cherry-pick from unstable. * Add patch to not crash in the library when the daemon goes away (Closes: #948228) (LP: #1843982) -- Iain Lane Tue, 05 May 2020 17:00:20 +0100 ** Changed in: accountsservice (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1843982 Title: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user() Status in accountsservice: New Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Focal: Triaged Status in accountsservice package in Debian: Confirmed Bug description: [ Description ] When accountsservice's daemon is restarted - particularly when there is a user configured for auto login - it can cause code using its library to crash. This is bad because gnome-shell is one of those users which crashes. [ QA ] Configure a user for automatic login in gnome-shell. Restart accounts-daemon.service (sudo systemctl restart accounts- daemon.service) a few times, leaving several seconds between each attempt. See that it crashes if you don't have this SRU, and doesn't if you do have it. --- Test that fast user switching still works properly. --- Take a look at the error reports listed below and hopefully see them not occurring (barring the usual noise) with the SRU. [ Regression potential ] We think this is safe - it tells clients that the daemon is away when it quits, and is back when it comes back. They should get appropriate signals to indicate this. Nevertheless, these signals are sent when they weren't before now, so that could cause problems. Watch out for errors creeping up with this SRU. We wondered upstream whether some more protections might be needed. I'm thinking that those should be *additional* safety rails around this fix, but it could actually be that more is needed and this fix isn't complete. [ Original report ] https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781 https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7 ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 14 10:29:16 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-05-24 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1843982/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1670507] Re: why is hud-service using so much memory?
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hud (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1670507 Title: why is hud-service using so much memory? Status in hud package in Ubuntu: Confirmed Bug description: When inspecting why my computer was sluggish I found hud-service using a lot of memory: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3142 sarnold 20 0 1208.1m 515.9m 9.9m S 0.0 3.3 1:44.69 hud-service Why are menus I never use taking over five hundred megabytes of my memory and so much CPU time? Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: hud 14.10+16.04.20160415-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 6 14:43:07 2017 InstallationDate: Installed on 2012-10-18 (1600 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: hud UpgradeStatus: Upgraded to xenial on 2016-04-30 (310 days ago) upstart.hud.log: [31mvoid DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)[0m: "No such interface 'com.canonical.dbusmenu' on object at path /org/ayatana/bamf/window/44040199" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1670507/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
This bug was fixed in the package libappindicator - 12.10.1+20.04.20200408.1-0ubuntu1 --- libappindicator (12.10.1+20.04.20200408.1-0ubuntu1) focal; urgency=medium [ Paul G ] * app-indicator: Don't pass unexpected parameter to signal emissions (LP: #1867996) [ Ash Holland ] * app-indicator: Only check for item numbers when iterating array (LP: #1867996) -- Marco Trevisan (Treviño) Wed, 08 Apr 2020 18:58:49 + ** Changed in: libappindicator (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Released Status in libappindicator package in Arch Linux: New Bug description: [ Impact ] Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Branch linked: lp:~ci-train-bot/libappindicator/libappindicator- ubuntu-focal-4007 -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in appmenu-qt5 package in Ubuntu: Fix Released Status in libappindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Released Status in libappindicator source package in Xenial: Fix Released Status in qtbase-opensource-src source package in Xenial: Confirmed Status in sni-qt source package in Xenial: Fix Released Bug description: Snaps that use the app indicator area via Qt can't display their icon there. Steps to reproduce and screenshot: https://github.com/nuttyartist/notes/pull/77 Some research: - Uses http://doc.qt.io/qt-5/qsystemtrayicon.html - The indicator icon is created under /tmp under a randomly generated directory name didrocks mentions also: 1. The application says "this is my menu, and here is my icon at that address", the address being /tmp/blablabla 2. appindicator receives the bus messages 3. and says "let's have a look at this icon at that address" 4. BUT! /tmp in the snap is different form system /tmp SRU bug for libappindicator: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/FpEvQYGN and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run gtk3-appindicator An indicator should open (with proper icon), then if you select "Set icon with Full Path" and/or "Enable Local Theme" from its menu, you should see a proper icon. When snaps are generated in non updated systems, the icon will be still missing. [Regression potential] If $SNAP is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for appmenu-qt5: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/KeZ1udjW and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt5-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible SRU bug for sni-qt: [Impact] Indicator icons pointing to a position inside the snap aren't properly found by unity, that shows a "missing icon" emblem [Test case] * Download this yaml file http://pastebin.com/raw/EZjQS5CH and save it as snapcraft.yaml in any folder you want * Run: - snapcraft prime - sudo snap try prime - snap run qt4-systray An indicator should open, with the proper icon showin. From the window you can change the icon type, and all the types should work. When snaps are generated in non updated systems, the icons (except the Themed one) will be still missing. [Regression potential] If $SNAP env variable is defined for an app not running in snap confinement the icons couldn't be properly visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1600136/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
** Branch linked: lp:~ci-train-bot/libappindicator/libappindicator- ubuntu-bionic-4009 ** Branch linked: lp:~ci-train-bot/libappindicator/libappindicator- ubuntu-focal-4007 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Committed Status in libappindicator package in Arch Linux: New Bug description: [ Impact ] Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) [ Test case ] - Run discord application - It must not crash in ubuntu (or when indicators are enabled) [ Regression potential ] Very low, icons might not appear in some cases, if any. - This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
** Branch linked: lp:~ci-train-bot/libappindicator/libappindicator- ubuntu-focal-4007.1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Fix Committed Status in libappindicator package in Arch Linux: New Bug description: Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
** Branch linked: lp:libappindicator -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Confirmed Status in libappindicator package in Arch Linux: New Bug description: Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1497490] Re: escape key bindings with or without modifiers do not work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compizconfig-settings-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to compizconfig-settings-manager in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1497490 Title: escape key bindings with or without modifiers do not work Status in compiz package in Ubuntu: Confirmed Status in compizconfig-settings-manager package in Ubuntu: Confirmed Bug description: All the bugs that are related to older versions of compiz are being closed. Since the bug still exists and it was closed due to it being old, then I need to re-create it. If it isn't going to be fixed for some philosophical reason, I'd like to see it posted here and that's fine. The bug is that no binding in compiz that includes the Escape key will work. Evidently that is by design at some level, but Alt-Ctrl-Esc is a handy binding to have. Simply put, if you try to bind any function to the Escape key by itself or with Shift/Alt/Super/Ctrl, the 'Grab' button will allow you to assign it, but the assignment will not work and there is no error reported. Not in the interface, nor in a logfile (that I can see yet). cf. older reports and comments: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/176195 https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/158855 http://forums.linuxmint.com/viewtopic.php?f=47=24397 http://ubuntu.5.x6.nabble.com/No-Ctrl-Alt-Esc-with-Compiz-td892450.html Ubuntu 15.04 Vivid Compiz Version: 1:0.9.12.1+15.04.20150410.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1497490/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1869501] [NEW] Bluetooth status in the Unity menu bar does not always match status in system settings
You have been subscribed to a public bug: When no Bluetooth device is connected and I turn off Bluetooth with the switch in the menu of the notification icon, the Bluetooth status in System Settings app is still "on" however Bluetooth seems to be off. Also, when Bluetooth is turned on, the status of a paired device may show "connection on" in the notification icon menu when it is actually not connected, as System Settings do show correctly. In this case I have to switch off and on again if I want to activate the connection. Also, I can not switch the connection to a paired device on or off with the System Settings app. The switches are grey and I can not click them, however they do always show the correct status. Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop Info: unity: 7.5.0+19.10.20190924-0ubuntu1 unity-control-center: 15.04.0+19.10.20190921-0ubuntu1 service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago Docs: man:bluetoothd(8) Main PID: 1035 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) Memory: 3.5M CGroup: /system.slice/bluetooth.service └─1035 /usr/lib/bluetooth/bluetoothd Mär 28 14:17:39 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:49:02 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:50:08 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through rfkill (0x12) Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect Mär 28 16:59:25 Abook bluetoothd[1035]: /org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready Bluetooth device: T: Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=8087 ProdID=0029 Rev=00.01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 28 16:53:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2020-01-20 (68 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug eoan -- Bluetooth status in the Unity menu bar does not always match status in system settings https://bugs.launchpad.net/bugs/1869501 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1851154] Re: libindicator ftbfs: G_ADD_PRIVATE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1851154 Title: libindicator ftbfs: G_ADD_PRIVATE Status in libindicator package in Ubuntu: Confirmed Bug description: libindicator fails to build with this error: ../../libindicator/indicator-object.c: In function ‘indicator_object_init’: ../../libindicator/indicator-object.c:307:13: error: G_ADD_PRIVATE [-Werror] 307 | IndicatorObjectPrivate * priv = G_TYPE_INSTANCE_GET_PRIVATE (self, INDICATOR_OBJECT_TYPE, IndicatorObjectPrivate); | ^~~ g_type_class_add_private was deprecated See attached full build log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1851154/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libappindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1867996 Title: Segfault in app_indicator_set_icon_full [patch attached] Status in libappindicator package in Ubuntu: Confirmed Status in libappindicator package in Arch Linux: New Bug description: Discord and several other applications using libappindicator are widely reported to have been crashing for several years. See: https://github.com/flathub/com.discordapp.Discord/issues/30 (and others) This is the backtrace: (gdb) bt full #0 0x7fe1d5d2e00e in () at /app/lib/libappindicator.so #1 0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0 #2 0x7fe1f5a813d2 in () at /lib/libgobject-2.0.so.0 #3 0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0 #4 0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0 #5 0x7fe1d5d2ed4f in app_indicator_set_icon_full () at /app/lib/libappindicator.so #6 0x0077851a in () #7 0x01de7123 in () #8 0x01e4bd4e in () #9 0x01e6e34c in () #10 0x01e6e668 in () #11 0x01e6e9cb in () #12 0x01df971a in () #13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0 #14 0x7fe1f354b430 in () at /lib/libglib-2.0.so.0 #15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0 #16 0x01df9606 in () #17 0x01e6e0e7 in () #18 0x01e29570 in () #19 0x00c37ec8 in () #20 0x00c37d15 in () #21 0x00c1da7d in () #22 0x00a9282e in () #23 0x007892d4 in () #24 0x007896e0 in () #25 0x03b830a3 in main () Happens in all versions of libappindicator built from latest sources available on launchpad. I ran into the issue yesterday when installing Discord for the first time. I have tracked the problem down to libappindicator passing in an extra vararg item to g_signal_emit that the signal's definition in libappindicator was not declaring, causing the crash you see above in gobject's g_signal dispatch machinery. Patch is attached. I am presuming this is 'upstream' for libappindicator, whatever that may mean for what appears to be an unmaintained project. If it is not, and since it is an Ubuntu/Canonical-sourced project originally, I respectfully request that you assist in upstreaming it since this bug is causing severe breakage for users across all distros. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1867996/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1363277] Re: Indicator not shown in fallback mode when a subdir/file with the same name of icon exists in current work dir
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libappindicator (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libappindicator in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1363277
Title:
Indicator not shown in fallback mode when a subdir/file with the same
name of icon exists in current work dir
Status in libappindicator:
New
Status in libappindicator package in Ubuntu:
Confirmed
Bug description:
Take the attached python script and execute it in a non-unity desktop
which does not support appindicators but can show gtk_status_icon (see
at the end of the post under the "Tested on" paragraph).
The attached script will fallback correctly to the old gtk_status_icon
and will show the "battery-good" indicator icon on the system tray.
Now exit from the script (with ^C).
In your current directory create a subdir named "battery-good".
Do not change directory and relaunch the script.
The fallback mechanism will be unable to find the icon, and now the
indicator will not be shown.
The problem could be in app-indicator.c, near line 1641
if (g_file_test(icon_name, G_FILE_TEST_EXISTS)) {
gtk_status_icon_set_from_file(icon, icon_name);
}
This code will find the subdir "battery-good" you created, and it will
try to load it as a icon. But if it fails, as it does, it will never
load an icon for your indicator.
Tested on xubuntu 14.04.1 64bit without indicator panel element and
with indicator application removed from autostart. Tested also on
Fedora 20 64bit with XFCE.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libappindicator/+bug/1363277/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1532440] Re: touchpad setting missing when using a wireless keyboard with touchpad
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: d-conf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1532440 Title: touchpad setting missing when using a wireless keyboard with touchpad Status in d-conf package in Ubuntu: Confirmed Bug description: 1. Plug in a wireless keyboard with a built-in trackpad (I have the logitech K400 Plus). 2. open dconf-editor 3. go to org > gnome > settings-daemon > peripherals 4. see that there is no "touchpad" entry My laptop has a touchpad entry that allows me to adjust touchpad-specific parameters. I would expect these to show up with the wireless keyboard/touchpad. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dconf-cli 0.24.0-2 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jan 9 14:41:02 2016 InstallationDate: Installed on 2015-09-30 (100 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) JournalErrors: No journal files were found. -- No entries -- SourcePackage: d-conf UpgradeStatus: Upgraded to wily on 2015-11-01 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1532440/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mono (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: humanity-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adwaita-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to humanity-icon-theme in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
