[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
** Changed in: accountsservice (Ubuntu) Status: In Progress => Fix Committed -- 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 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/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] Re: /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
*** This bug is a duplicate of bug 2015962 *** https://bugs.launchpad.net/bugs/2015962 ** Package changed: indicator-messages (Ubuntu) => accountsservice (Ubuntu) ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released ** This bug has been marked a duplicate of bug 2015962 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() -- 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/2016312 Title: /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 Status in accountsservice 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/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/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/2016312/+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
Chris, please try to use the upstream version of this extension from https://github.com/ubuntu/gnome-shell-extension-appindicator/ It changes the way we handle indicator-multiload in a way that should improve performance. -- 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: Confirmed 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 725435] Re: notify-osd a memory hog (memory leak?)
** Changed in: libnotify (Ubuntu) Status: New => Invalid -- 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/725435 Title: notify-osd a memory hog (memory leak?) Status in libnotify package in Ubuntu: Invalid Status in notify-osd package in Ubuntu: Triaged Bug description: Binary package hint: notify-osd Noticed this today on my lucid box in top: 2647 myaccount 20 0 1196m 595m 3528 S0 29.7 1:09.68 notify-osd I don't think a simple notifcation daemon should suck up more than a Gig of memory of which half is real memory. It's the first time I noticed this. I don't have too much information at this point. $ dpkg -l notify-osd* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Description +++-=-=-== ii notify-osd0.9.29-0ubuntu2 daemon that displays passive pop-up notifications ii notify-osd-icons 0.6 Notify-OSD icons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/725435/+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 42 from accountsservice
I think this is triggered by valgrind because it leads to slowdowns, but the bug is indeed there. We can handle it in a later upload I think, but due to gslice and the randomness of these memory errors, I wouldn't be shocked if this is actually presenting right now in the wild with a different stack trace. -- 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: Valgrind memory errors in gnome-shell 42 from accountsservice Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: New Status in gnome-shell package in Ubuntu: New 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==
[Dx-packages] [Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
For what it worth that argbToRgba code (which I'd like to move to GdkPixbuf asap) isn't really used in indicator-multiload as it provides the actual icons to show, so the shell has "only" to paint them, and unfortunately this is something that looks somewhat slow. The argbToRgba function is unfortunately a needed thing, but only for indicators providing pixmaps, that are in such format and we don't have access to other C code doing this better right now. -- 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: Confirmed 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 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
The fix is already in 20.04, while for 18.04 you can use the packages in https://launchpad.net/~ci-train-ppa-service/+archive/4009/+packages while the SRU team looks at the fix in queue for some time now. -- 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 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
Both patches have been applied, so no need for further bug. cfr https://bazaar.launchpad.net/~indicator-applet- developers/libappindicator/trunk/revision/295 -- 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 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
** Branch linked: lp:~3v1n0/libappindicator/discord-indicator-crash- fix-18.04 -- 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]
** Description changed: + [ 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. -- 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
[Dx-packages] [Bug 1867996] Re: Segfault in app_indicator_set_icon_full [patch attached]
** Changed in: libappindicator (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: libappindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Importance: Medium => Unknown ** Changed in: mesa Remote watch: freedesktop.org Bugzilla #64202 => gitlab.freedesktop.org/mesa/mesa/issues #727 -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1832865] Re: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user
Not a gnome-shell issue, but an accountsservice one. ** Summary changed: - /usr/bin/gnome-shell:11:g_str_hash:g_hash_table_hash_to_index:g_hash_table_lookup_node:g_hash_table_lookup:update_user + gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Changed in: accountsservice (Ubuntu) Status: New => In Progress ** Changed in: accountsservice (Ubuntu) Status: In Progress => Triaged ** Bug watch added: gitlab.freedesktop.org/accountsservice/accountsservice/issues #55 https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 ** Also affects: accountsservice via https://gitlab.freedesktop.org/accountsservice/accountsservice/issues/55 Importance: Unknown Status: Unknown -- 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/1832865 Title: gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index -> g_hash_table_lookup_node -> g_hash_table_lookup -> update_user Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.32.1-1ubuntu1~19.04.1, the problem page at https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8 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/1832865/+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 1506744] Re: Newly installed applications do not show in the dash
** Changed in: bamf (Ubuntu) Status: In Progress => Triaged -- 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/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Expired Status in bamf package in Ubuntu: Triaged Status in gnome-menus package in Ubuntu: Fix Released Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in gnome-menus source package in Xenial: Fix Released Status in libunity source package in Xenial: Fix Released Bug description: [Impact] I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. [Test case] 1. Install a new applicaiton (using apt-get or the software center) 2. Make sure the application is listed in the Unity Dash [Possible Regressions] Unity fails to list all the applications, not just the newly installed ones. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install)Z To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1773859] Re: upgrades to 18.04 fail
A friend of mine also got this on upgrade (he's not skilled so was quite critical to him): Whole error on further upgrades were (sorry for italian locale): I seguenti pacchetti NUOVI saranno installati: libmsgpackc2 tmate 0 aggiornati, 2 installati, 1 da rimuovere e 1 non aggiornati. 1 non completamente installati o rimossi. È necessario scaricare 0 B/259 kB di archivi. Dopo quest'operazione, verranno occupati 652 kB di spazio su disco. Continuare? [S/n] s (Lettura del database... 402540 file e directory attualmente installati.) Rimozione di systemd-shim (9-1bzr4ubuntu1)... Rimozione di "deviazione di /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service in /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd da systemd-shim" dpkg-divert: errore: la rinomina comprende il sovrascrivere "/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service" con il file "/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd", non consentito dpkg: errore nell'elaborare il pacchetto systemd-shim (--remove): installed systemd-shim package post-removal script subprocess returned error exit status 2 Si sono verificati degli errori nell'elaborazione: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1768610] Re: leftover conffile forces GNOME is software rendering
Tested in a Xenial machine, upgrading packages to: x11-common: Installato: 1:7.7+13ubuntu3.1 Candidato: 1:7.7+13ubuntu3.1 Tabella versione: *** 1:7.7+13ubuntu3.1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu xenial/main amd64 Packages 500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 1:7.7+13ubuntu3 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://it.archive.ubuntu.com/ubuntu xenial/main i386 Packages nux-tools: Installato: 4.0.8+16.04.20180622.2-0ubuntu1 Candidato: 4.0.8+16.04.20180622.2-0ubuntu1 Tabella versione: *** 4.0.8+16.04.20180622.2-0ubuntu1 500 500 http://ppa.launchpad.net/ci-train-ppa-service/3303/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 4.0.8+16.04.20170816-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 4.0.8+16.04.20160209-0ubuntu2 500 500 http://it.archive.ubuntu.com/ubuntu xenial/main amd64 Packages Running unity works propery, after upgrade, nux-tools is kept and file not run... After autoremove, it gets removed and gnome-shell runs properly. ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial ** Tags removed: verification-needed ** Tags added: verification-done ** Changed in: nux (Ubuntu Artful) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Fix Committed Status in nux source package in Artful: Won't Fix Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the
[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Tags removed: verification-needed-artful -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Fix Committed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Won't Fix Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED UNITY ] · remove nux-tools from artful/bionic-release (pre-sru), upgrade, reinstall nux-tools (no prompt) · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall nux-tools (nothing should be prompted) · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) · install nux-tools, upgrade, no prompt You end up with either no /etc/X11/Xsession.d/50_check_unity_support, its new contents or you are asked what to do if you've changed it before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Description changed: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. - [ Test case ] + [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial + · Upgrade (nux-tools) and ensure that unity is still properly running after + a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that - printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running - in an environment with no 3d support (VMs are easy tests) + printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running + in an environment with no 3d support (VMs are easy tests) + + [ Test case - FOR WHO HAS ALREADY UPGRADED TO BIONIC/ARTFUL AND REMOVED + UNITY ] + + · remove nux-tools from artful/bionic-release (pre-sru), upgrade, +reinstall nux-tools (no prompt) + · remove nux-tools from bionic-proposed/updates (sru), upgrade, reinstall +nux-tools (nothing should be prompted) + · modify config file, remove nux-tools, upgrade, reinstall nux-tools (should prompt) + · install nux-tools, upgrade, no prompt + + You end up with either no /etc/X11/Xsession.d/50_check_unity_support, + its new contents or you are asked what to do if you've changed it + before. Never the old content. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case - FOR WHO UPGRADES TO BIONIC/ARTFUL ] · Install xenial · Upgrade (nux-tools) and ensure that unity is still properly running after a logout/login cycle. · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: -
[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
> What's the reason for doing this in preinst rather than postinst configure? Well, I just wanted to make sure this happened as early as possible, since this is not related to what the package installs, I thought it was better to handle this in preinst, so that this can be also just removed at later times. > What about adding a "Breaks"... Done. Agree. -- New debdiff. Updated MPs too. ** Patch added: "xorg.debdiff" https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5154434/+files/xorg.debdiff -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Package changed: mesa (Ubuntu) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: New => In Progress ** Changed in: xorg (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: In Progress Status in nux source package in Xenial: Fix Committed Status in xorg source package in Xenial: Confirmed Status in nux source package in Artful: Fix Committed Status in xorg source package in Artful: Confirmed Status in nux source package in Bionic: Fix Committed Status in xorg source package in Bionic: In Progress Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
Added scripts in in x11-common (debdiff) and nux-tools (see attached MPs) ** Patch added: "xorg.debdiff" https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+attachment/5154156/+files/xorg.debdiff -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
Yeah, I basically did the same too, but honestly I didn't want to change nux again with another SRU (I preferred to fix this with just one on that side); and most importantly in a such way. As it would now include some checks that depends on changes done in other packages, making from my POV things even more hackish and annoy to matain and easy to be broken. Not that other solutions wouldn't involve the other package (say mesa) to act on nux file, but that should be in a way that nux is not aware of that, creating any kind of "inter-dependency" in between them. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
On a 2nd thinking, if that nux-tools reinstall will happen after this nux SRU landed (and of course assuming that this will be after the "fixing-package" containing the maintainer script has ran too), since the content of the config file will mismatch (being deleted), debhelper will ask to reinstall a new version with the classic: Configuration file '/etc/X11/Xsession.d/50_check_unity_support' ==> Deleted (by you or by a script) since installation. ==> Package distributor has shipped an updated version. However, I'm not either a fan of having this around since it's something the distro caused, not the user. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
I've playing with this a bit more to get the fix for the currently affected users who already upgraded to bionic and removed nux-tools, but I don't think there's a solution which works if we keep this marked as a Conffile by dpkg. In fact, using the various rm_conffile or just removing the file from a maintainer script in any other package, then if the user will try to reinstall unity (and then nux-tools), this config file won't be reinstalled, as it's still there according to dpkg. If anyone know a solution in how we can manipulate the dpkg status from a maintainer script, that's the way, otherwise I've no other idea than going back to the solution I proposed in the last night's MPs of removing this conffile from nux-tools itself, storing it in /usr and then symlinking it (with new name) to /etc [1] as mentioned (although for other scenarios) in maintainers guide. So at that point any reinstall will just work, and no purge will affect it. PS: other *ugly* option would be instead to make this other-package (mesa?) to replace in a maintainer script the content of this file with the fixed one, but really I don't want to go in that way. [1] https://bazaar.launchpad.net/~3v1n0/nux/x11-conffile-on-unity- only/revision/893 -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Description changed: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. + + · If running Unity session instead, ensure that + printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running + in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: Fix Committed Status in mesa source package in Artful: New Status in nux source package in Artful: Fix Committed Status in mesa source package in Bionic: New Status in nux source package in Bionic: Fix Committed Bug description: [ Impact ] GNOME shell and other 3D programs run using software rendering after unity removal. This SRU covers only the upgrade case or if nux-tools removal happens after this update, for people who already upgraded and in broken state another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - printenv LIBGL_ALWAYS_SOFTWARE Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. · If running Unity session instead, ensure that printenv LIBGL_ALWAYS_SOFTWARE equals 1 in case that you're running in an environment with no 3d support (VMs are easy tests) [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0,
[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
** Description changed: + [ Impact ] + + GNOME shell and other 3D programs run using software rendering after + unity removal + + [ Test case ] + + · Install xenial + · Upgrade to bionic or artful + (assuming you're using a GNOME session) + · sudo apt remove nux-tools + · log into your session + . From terminal: + - printenv LIBGL_ALWAYS_SOFTWARE + Should print nothing (and return an error) + + Same should happen if you don't remove nux-tools but you change + `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. + + [ Regression Potential ] + + Unity desktops with no 3d support could not start anymore. + + === + After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' - ProblemType: Bug - DistroRelease: Ubuntu 18.04 + ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash - SourcePackage: gnome-session + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bashSourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) ** Description changed: [ Impact ] GNOME shell and other 3D programs run using software rendering after - unity removal + unity removal. + + This SRU covers only the upgrade case or if nux-tools removal happens + after this update, for people who already upgraded and in broken state + another SRU will follow. [ Test case ] · Install xenial · Upgrade to bionic or artful - (assuming you're using a GNOME session) + (assuming you're using a GNOME session) · sudo apt remove nux-tools · log into your session . From terminal: - - printenv LIBGL_ALWAYS_SOFTWARE - Should print nothing (and return an error) + - printenv LIBGL_ALWAYS_SOFTWARE + Should print nothing (and return an error) Same should happen if you don't remove nux-tools but you change `/usr/lib/nux/unity_support_test` not to run properly (replace with a script exiting 1), but you're running a GNOME session. [ Regression Potential ] Unity desktops with no 3d support could not start anymore. === After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: BugDistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate:
[Dx-packages] [Bug 1768610] Re: leftover conffile forces GNOME is software rendering
I'm happy to do it in any package postinst, I was thinking more to keep it somehwere under the desktop team control, as it's something we should care about, while I prefer to have it fixed at least to anyone who has installed ubuntu-desktop. But I agree it's wrong also for other people using desktop under X11 (and who might have just tried unity in the past), so staying lower is fine. If mesa is fine to accept this, I'm happy to do it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: Fix Released Status in mesa source package in Xenial: New Status in nux source package in Xenial: In Progress Status in mesa source package in Artful: New Status in nux source package in Artful: In Progress Status in mesa source package in Bionic: New Status in nux source package in Bionic: In Progress Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Branch linked: lp:~3v1n0/nux/x11-conffile-on-unity-only-ab -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in mesa package in Ubuntu: New Status in nux package in Ubuntu: In Progress Status in mesa source package in Xenial: New Status in nux source package in Xenial: In Progress Status in mesa source package in Artful: New Status in nux source package in Artful: In Progress Status in mesa source package in Bionic: New Status in nux source package in Bionic: In Progress Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1768610/+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 1768610] Re: leftover conffile forces GNOME is software rendering
** Changed in: nux (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1768610 Title: leftover conffile forces GNOME is software rendering Status in nux package in Ubuntu: In Progress Bug description: After an upgrade from 17.10 to 18.04, I noticed that all gnome windows animations were gone. After some digging, it seems that gnome-session incorrectly assumes that my graphics has no acceleration, when in fact it does: it's a i5-2520M CPU @ 2.50GHz with Intel integrated graphics (i915 driver). I've tried this with and without the xserver-xorg-video-intel package (a.k.a. Intel driver) with the same behavior. The output of gnome-session-check-accelerated is: llvmpipe (LLVM 6.0, 256 bits) however the system should have DRM 2.0 capability. GL checks (e.g. glxinfo, glxgears produce the expected output from a working DRM system). mesa-utils and mesa-utils-extra are both installed. I can't find a work around. Perhaps there is something wrong with my install/upgrade? Everything else works fine, although the graphical transitions are no longer smooth. But it would be nice to restore the expected behavior. I have attached the log of 'journalctl -b0' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 2 13:06:00 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (739 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-04-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1768610/+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 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update
Generated Snap with libunity 7.1.4+16.04.20180209.1-0ubuntu1, launcher integration works just fine. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1747814 Title: Snapped applications using ubuntu launcher integration needs desktop update Status in libunity package in Ubuntu: Fix Released Status in libunity source package in Xenial: Fix Committed Bug description: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git cd ubuntu-launcher-integration-snap snapcraft prime snap try prime Then launch those (you might do it from dash/activities to get proper matching): ubuntu-launcher-integration-snap.ubuntu-launcher ubuntu-launcher-integration-snap.ubuntu-launcher-2nd ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747814/+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 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update
Hi Lukasz, While for bug #1747802 this would indeed make sense, for this specific not really, since this affects mostly the snapcrafter's (as these fixes will apply to apps running inside snaps built in a xenial-based distro), and snapcraft isn't supporting artful anyway. -- 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/1747814 Title: Snapped applications using ubuntu launcher integration needs desktop update Status in libunity package in Ubuntu: Fix Released Status in libunity source package in Xenial: Fix Committed Bug description: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git cd ubuntu-launcher-integration-snap snapcraft prime snap try prime Then launch those (you might do it from dash/activities to get proper matching): ubuntu-launcher-integration-snap.ubuntu-launcher ubuntu-launcher-integration-snap.ubuntu-launcher-2nd ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747814/+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 1747814] Re: Snapped applications using ubuntu launcher integration needs desktop update
** Description changed: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] - snap install ubuntu-launcher-integration-snap + git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git + cd ubuntu-launcher-integration-snap + snapcraft prime + snap try prime Then launch those (you might do it from dash/activities to get proper matching): - ubuntu-launcher-integration-snap.ubuntu-launcher - ubuntu-launcher-integration-snap.ubuntu-launcher-2nd - ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded + ubuntu-launcher-integration-snap.ubuntu-launcher + ubuntu-launcher-integration-snap.ubuntu-launcher-2nd + ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate -- 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/1747814 Title: Snapped applications using ubuntu launcher integration needs desktop update Status in libunity package in Ubuntu: Fix Released Bug description: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] git clone https://github.com/3v1n0/ubuntu-launcher-integration-snap.git cd ubuntu-launcher-integration-snap snapcraft prime snap try prime Then launch those (you might do it from dash/activities to get proper matching): ubuntu-launcher-integration-snap.ubuntu-launcher ubuntu-launcher-integration-snap.ubuntu-launcher-2nd ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747814/+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 1737835] Re: libunity fails to build, test failure
** Changed in: libunity (Ubuntu) Status: New => In Progress ** Changed in: libunity (Ubuntu) Importance: Undecided => High ** Changed in: libunity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1737835 Title: libunity fails to build, test failure Status in libunity package in Ubuntu: In Progress Bug description: libunity fails to build from source in current bionic. Full build log at https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861 Build log excerpt = TEST: test-vala... (pid=18081) /Unit/ResultsSynchronizer: OK /Unit/IO/AsyncDesktopFile: OK /Unit/IO/AsyncOpenFromDataDirs: OK /Unit/Utils/AsyncOnce: OK /Unit/Utils/AsyncMutex: OK /Unit/AppInfoManager/Allocation: OK /Unit/AppInfoManager/ClearEmpty: OK /Unit/AppInfoManager/SyncLookupMissing: OK /Unit/AppInfoManager/AsyncLookupMissing: OK /Unit/AppInfoManager/SyncLookupOk: OK /Unit/AppInfoManager/AsyncLookupOk: OK /Unit/Launcher/EmptyEntry: (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1737835/+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 1747814] [NEW] Snapped applications using ubuntu launcher integration needs desktop update
Public bug reported: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] snap install ubuntu-launcher-integration-snap Then launch those (you might do it from dash/activities to get proper matching): ubuntu-launcher-integration-snap.ubuntu-launcher ubuntu-launcher-integration-snap.ubuntu-launcher-2nd ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate ** Affects: libunity (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- 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/1747814 Title: Snapped applications using ubuntu launcher integration needs desktop update Status in libunity package in Ubuntu: In Progress Bug description: [ Impact ] Launching a snapped application with ubuntu launcher icon integration doesn't properly work as the desktop ID does not use the proper namespace. Also, a snapped app could decorate other apps outside the snap scope. [ Test case ] snap install ubuntu-launcher-integration-snap Then launch those (you might do it from dash/activities to get proper matching): ubuntu-launcher-integration-snap.ubuntu-launcher ubuntu-launcher-integration-snap.ubuntu-launcher-2nd ubuntu-launcher-integration-snap.ubuntu-launcher-hardcoded All these apps should get an icon in the launcher with emblems (of different values when they're launched together). [ Regression potential ] Application with SNAP environments could point to wrong desktop-file to decorate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1747814/+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 1737835] Re: libunity fails to build, test failure
Mh, this builds pretty fine here... Might be due to not-properly initialized session bus in headless mode. -- 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/1737835 Title: libunity fails to build, test failure Status in libunity package in Ubuntu: New Bug description: libunity fails to build from source in current bionic. Full build log at https://launchpad.net/~jbicha/+archive/ubuntu/dev/+build/13847861 Build log excerpt = TEST: test-vala... (pid=18081) /Unit/ResultsSynchronizer: OK /Unit/IO/AsyncDesktopFile: OK /Unit/IO/AsyncOpenFromDataDirs: OK /Unit/Utils/AsyncOnce: OK /Unit/Utils/AsyncMutex: OK /Unit/AppInfoManager/Allocation: OK /Unit/AppInfoManager/ClearEmpty: OK /Unit/AppInfoManager/SyncLookupMissing: OK /Unit/AppInfoManager/AsyncLookupMissing: OK /Unit/AppInfoManager/SyncLookupOk: OK /Unit/AppInfoManager/AsyncLookupOk: OK /Unit/Launcher/EmptyEntry: (test-vala:18081): libunity-CRITICAL **: unity-launcher.vala:154: Unable to connect to session bus: Could not connect: Connection refused FAIL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1737835/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Status in nux source package in Xenial: Fix Committed Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1728449] Re: Indicator icons do not appear after upgrade to Ubuntu 17.10
Question is, why indicator-application-service is running in your GNOME session? Are you using some special systemd configuration? As this should not be running in GNOME but only in the Unity session. As for the other issues mentioned here, I think that it's not really an ubuntu bug, but it looks like a misconfiguration on the client part. Having two extensions trying to handle indicators isn't feasible (as they both want the same dbus name), so we can't do much. At least in future it won't be possible to install KSTatusNotificationIcon extension and the ubuntu indicators one together, so the issue will be less visible. ** Changed in: indicator-application (Ubuntu) Status: Confirmed => Incomplete ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1728449 Title: Indicator icons do not appear after upgrade to Ubuntu 17.10 Status in gnome-shell package in Ubuntu: Won't Fix Status in indicator-application package in Ubuntu: Incomplete Bug description: After upgrading from 17.04 to 17.10 all the indicator icons (Steam, InSync, Google Chrome, Hangouts, Slack, etc) are missing. A temporary workaround is to kill indicator-application-service, but this only works until the next reboot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-application 12.10.1+17.04.20161201-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 29 20:45:06 2017 InstallationDate: Installed on 2015-03-28 (946 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: indicator-application UpgradeStatus: Upgraded to artful on 2017-10-07 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728449/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
I've tested indicators-printers version 0.1.7+17.10.20171021-0ubuntu1 and so far no crashes are present. Also given the simplicity of the change, I think we can safely mark this as verified. ** Tags removed: verification-needed verification-needed-artful ** Tags added: verification-done verification-done-artful -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1703046 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() Status in indicator-printers package in Ubuntu: In Progress Status in indicator-printers source package in Artful: Fix Committed Bug description: [ Impact ] indicators-printers crashes, notifying the error to the user. [ Test case ] This was one of the most hit crash in errors.ubuntu.com. Make sure this will no longer happen once the fix is released. The link is https://errors.ubuntu.com/problem/43e6488fd8640c6a0cb8ca237286153b5b547f80 [ Regression potential ] Nothing really possible, other not crashing. Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax PC (0x7fa9166826b5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo ubridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1703046/+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 1703046] Re: indicator-printers-service crashed with SIGSEGV in __GI_____strtol_l_internal()
** Description changed: + [ Impact ] + + indicators-printers crashes, notifying the error to the user. + + + [ Test case ] + + Not clear test case, just indicators-printer could crash when fetching + the printer status from cups. + + [ Regression potential ] + + Nothing really possible, other not crashing. + Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= SegvAnalysis: - Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax - PC (0x7fa9166826b5) ok - source "(%r14)" (0x) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax + PC (0x7fa9166826b5) ok + source "(%r14)" (0x) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: - __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 - () - g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 - g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 + () + g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() UpgradeStatus: Upgraded to artful on 2017-02-14 (143 days ago) UserGroups: adm cdrom dip kismet libvirt lpadmin lxd plugdev sambashare sudo ubridge -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1703046 Title: indicator-printers-service crashed with SIGSEGV in __GI_strtol_l_internal() Status in indicator-printers package in Ubuntu: In Progress Bug description: [ Impact ] indicators-printers crashes, notifying the error to the user. [ Test case ] Not clear test case, just indicators-printer could crash when fetching the printer status from cups. [ Regression potential ] Nothing really possible, other not crashing. Just got this from the recent update ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: indicator-printers 0.1.7+17.04.20170227-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Fri Jul 7 16:55:07 2017 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service InstallationDate: Installed on 2015-12-17 (567 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-printers/indicator-printers-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7fa9166826b5 <__GI_strtol_l_internal+53>: movsbq (%r14),%rax PC (0x7fa9166826b5) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-printers StacktraceTop: __GI_strtol_l_internal (nptr=0x0, endptr=0x0, base=10, group=, loc=0x7fa916a09400 <_nl_global_locale>) at ../stdlib/strtol_l.c:293 () g_type_create_instance () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
[Dx-packages] [Bug 1718615] [NEW] Nux doesn't build proprerly in s390x arch
Public bug reported: This is due to some tests segfaulting because of impossible-to-debug (for me) issues, so it's quite safe to remove it from the archive. libnux-4.0-0 libnux-4.0-dev libunity-core-6.0-9 libunity-core-6.0-dev unity unity-lens-video unity-lens-music unity-lens-files unity-lens-applications unity-china-music-scope ** Affects: nux (Ubuntu) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1718615 Title: Nux doesn't build proprerly in s390x arch Status in nux package in Ubuntu: Fix Released Bug description: This is due to some tests segfaulting because of impossible-to-debug (for me) issues, so it's quite safe to remove it from the archive. libnux-4.0-0 libnux-4.0-dev libunity-core-6.0-9 libunity-core-6.0-dev unity unity-lens-video unity-lens-music unity-lens-files unity-lens-applications unity-china-music-scope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1718615/+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 1664205] Re: Copy-paste and text selection doesn't work when caps-lock is on
** Description changed: + [Impact] + Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on + + [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, -Ctrl+V should paste and Ctrl+X should cut + Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off + + [Possible regression] + Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: Fix Released Bug description: [Impact] Text entry doesn't properly accept Ctrl+[letter] based shortcuts when Caps Lock is on [Test case] 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off [Possible regression] Ctrl+[letter] shortcuts or Ins based shortcuts for text selection handling won't work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
By "fixed version" I meant 13.10.0+14.04.20170403-0ubuntu1 from trusty proposed. No regression so far. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Committed Status in ido source package in Xenial: Fix Released Status in ido source package in Yakkety: Fix Released Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
I'm running fixed version for some weeks in my trusty machine. No crash anymore so far. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Committed Status in ido source package in Xenial: Fix Released Status in ido source package in Yakkety: Fix Released Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()
Otherwise you can just add this ppa: https://launchpad.net/~ci-train- ppa-service/+archive/ubuntu/2689 Packages will be there shortly, and then released to trusty after the SRU process will be finished. Please subscribe to bug https://pad.lv/1506427 and follow the verification steps in order to get this fix delivered. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350821 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press() Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Released Bug description: [Impact] Unity panel service crashes when opening the Calendar menu [Test Case] There's not a way to reproduce this systemically. Just open frequently the calendar menu, but this crash can happen or not. [Regression Potential] None, the code change consists only on protecting against a null pointer (recorded in the stacktraces here), so it's just pretty safe. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 31 13:53:14 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-12-22 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx PC (0x7ffbbaf3b766) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jul 30 18:55:05 2014 xserver.configfile: default xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does
[Dx-packages] [Bug 1350821] Re: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press()
Sorry, the proper fix has not been released to trusty... However you can manually install the fixed .deb from http://packages.ubuntu.com/xenial/libido3-0.1-0 Just pick the one for your architecture and `sudo dpkg -i` it. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1350821 Title: unity-panel-service crashed with SIGSEGV in ido_calendar_menu_item_key_press() Status in ido package in Ubuntu: Fix Released Status in ido source package in Trusty: Fix Released Bug description: [Impact] Unity panel service crashes when opening the Calendar menu [Test Case] There's not a way to reproduce this systemically. Just open frequently the calendar menu, but this crash can happen or not. [Regression Potential] None, the code change consists only on protecting against a null pointer (recorded in the stacktraces here), so it's just pretty safe. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jul 31 13:53:14 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.12, 3.16.0-5-generic, x86_64: installed virtualbox, 4.3.12, 3.16.0-6-generic, x86_64: installed ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-12-22 (221 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: PATH=(custom, user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=23a70067-84b7-4d69-8cbc-11f2fe3f429d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7ffbbaf3b766:mov0x10(%rdx),%ecx PC (0x7ffbbaf3b766) ok source "0x10(%rdx)" (0x0010) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare scanner sudo dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jul 30 18:55:05 2014 xserver.configfile: default xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id
[Dx-packages] [Bug 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user
As I wrote in IRC, unfortunately even using the new zeitgeist --vacuum Would fail in such scenario, as it would return a non-zero value (see [1]), thus my idea of just changing the unit file. Which also is due to the fact that a standalone tool is right to return an error in such cases, while it's up to script to handle these failures. [1] https://cgit.freedesktop.org/zeitgeist/zeitgeist/tree/src/zeitgeist- daemon.vala#n478 -- 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/1666495 Title: [Zesty] No default apps shown on first start in kvm oem end user Status in unity-lens-applications: Invalid Status in zeitgeist package in Ubuntu: In Progress Bug description: STEPS: 1. Install the latest iso in kvm 2. Click on Ubuntu button EXPECTED: I expect to see Thunderbird, rhythmbox, totem, etc. There are normally 5 default apps shown. ACTUAL: I get what you see in the attached screenshot. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-02-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221) Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+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 1666495] Re: [Zesty] No default apps shown on first start in kvm oem end user
** Changed in: unity-lens-applications Status: Incomplete => Invalid ** Also affects: zeitgeist (Ubuntu) Importance: Undecided Status: New ** Changed in: zeitgeist (Ubuntu) Status: New => In Progress ** Changed in: zeitgeist (Ubuntu) Importance: Undecided => High ** Changed in: zeitgeist (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1666495 Title: [Zesty] No default apps shown on first start in kvm oem end user Status in unity-lens-applications: Invalid Status in zeitgeist package in Ubuntu: In Progress Bug description: STEPS: 1. Install the latest iso in kvm 2. Click on Ubuntu button EXPECTED: I expect to see Thunderbird, rhythmbox, totem, etc. There are normally 5 default apps shown. ACTUAL: I get what you see in the attached screenshot. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-02-21 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170221) Package: unity-lens-applications 7.1.0+16.10.20160927-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-applications/+bug/1666495/+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
** Tags removed: verification-needed ** Tags added: verification-done -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Committed Status in libappindicator source package in Xenial: Fix Committed Status in qtbase-opensource-src source package in Xenial: New Status in snapd source package in Xenial: New Status in sni-qt source package in Xenial: Fix Committed 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/qt/+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 1606246] Re: Hard-coded X11 calls cause Unity 8 to fail to run on desktop
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1606246 Title: Hard-coded X11 calls cause Unity 8 to fail to run on desktop Status in appmenu-qt5: Fix Released Status in Mir: Triaged Status in appmenu-qt5 package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: Fix Released Status in appmenu-qt5 source package in Xenial: Fix Committed Status in unity8-desktop-session source package in Xenial: New Bug description: The appmenu-qt5 code has hardcoded Xlib calls that cause Unity 8 (or any other Qt-based applicaiton) to die on startup when run on Mir instead of X11. This library extension should either not hardcode X11 (preferred) or check for the presence of a $DISPLAY environment variable and avoid code paths that assume X11. The Unity 8 desktop currently has a hard-coded check for $QT_QPA_PLATFORMTHEME and unsets it as a workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt5/+bug/1606246/+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
** Description changed: 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 + in any folder you want * Run: - - snapcraft prime - - sudo snap try prime - - snap run qt5-systray + - 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 -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: 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
[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Description changed: 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 -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: 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: -
[Dx-packages] [Bug 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Description changed: 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 + in any folder you want * Run: - - snapcraft prime - - sudo snap try prime - - snap run gtk3-appindicator + - snapcraft prime + - sudo snap try prime + - snap run gtk3-appindicator - An indicator should open (with proper icon), then if you select "Custom - Themed Icon" from its menu, you should see a proper icon. + 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 -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+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 1664205] [NEW] Copy-paste and text selection doesn't work when caps-lock is on
Public bug reported: 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off ** Affects: nux (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1664205 Title: Copy-paste and text selection doesn't work when caps-lock is on Status in nux package in Ubuntu: In Progress Bug description: 0) Set Caps-Lock on in your keyboard 1) Open dash, and write something 2) Ctrl+A should select all the text, Ctrl+C should copy, Ctrl+V should paste and Ctrl+X should cut Currently they don't work unless caps-lock is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1664205/+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
Debdiff updated to backport the patches that have just merged upstream. - https://codereview.qt-project.org/182492 - https://codereview.qt-project.org/182564 ** Patch added: "qdbustrayicon-try-to-save-temp-icons-in-readable-location-v2.debdiff" https://bugs.launchpad.net/snappy/+bug/1600136/+attachment/4814779/+files/qdbustrayicon-try-to-save-temp-icons-in-readable-location-v2.debdiff -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
I'm testing both xenial, yakkety and zesty for months... Crashes just don't happen anymore. There's no a common way to reproduce, but it always happened after some time of uptime and indicators+keyboard usage, and this has been fixed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Status in ido source package in Yakkety: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Status in ido source package in Yakkety: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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
Upstream fix for pure Qt apps (when not including appmenu-qt5) is proposed at https://codereview.qt-project.org/#/c/182307/. Here's the patch for the ubuntu package too. ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => In Progress ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: qt Importance: Undecided Status: New ** Changed in: qt Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: qt Status: New => In Progress ** Patch added: "qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff" https://bugs.launchpad.net/qt/+bug/1600136/+attachment/4803964/+files/qdbustrayicon-try-to-save-temp-icons-in-readable-location.debdiff -- 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 Qt: In Progress Status in Snappy: New 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: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+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 652978] Re: Notifications should be suppressed when indicators open
It's not up to unity to request the notification, but to indicator- sound. However, it can have an idea about what has changed by monitoring unity-panel-service status. Probably this can be done in notify-osd, though... By always delaying pop-ups when an indicator menu is open. ** Changed in: unity (Ubuntu) Status: Confirmed => Invalid ** Changed in: notify-osd (Ubuntu) Status: Invalid => Triaged -- 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/652978 Title: Notifications should be suppressed when indicators open Status in notify-osd package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Bug description: When using the sound menu, the user is immediately visually notified about switching of tracks by the menu itself. + When notifying using Notify-OSD, it covers some parts of sound menu itself. I think Notify-OSD should not be shown when switching tracks using the sound-menu and MAY BE whenever switching manually. Example video: http://dl.dropbox.com/u/275756/out.ogv PS: U1 was not working, so dropbox. :) and yes, I did spend like 10 minutes thinking which songs I should show in the video. :P The equivalent for the volume slider is bug 1389761. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/652978/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
William, I think the problem you mention is unrelated to this bug. Did you get any crash of unity panel service in /var/crash ? -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Status in ido source package in Yakkety: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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
** Changed in: appmenu-qt5 (Ubuntu) Status: Confirmed => In Progress ** Changed in: appmenu-qt5 (Ubuntu) Importance: Undecided => High ** Changed in: appmenu-qt5 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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 Snappy: New Status in appmenu-qt5 package in Ubuntu: In Progress Status in libappindicator package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: In Progress 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 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+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 1600136] Re: App indicator does not show icon for Qt apps or with custom icons
** Also affects: libappindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: libappindicator (Ubuntu) Status: New => In Progress ** Changed in: libappindicator (Ubuntu) Importance: Undecided => High ** Changed in: libappindicator (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: Confirmed => In Progress ** Changed in: snapd (Ubuntu) Importance: Undecided => High ** Changed in: snapd (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1600136 Title: App indicator does not show icon for Qt apps or with custom icons Status in Snappy: New Status in appmenu-qt5 package in Ubuntu: New Status in libappindicator package in Ubuntu: In Progress Status in snapd package in Ubuntu: In Progress Status in sni-qt package in Ubuntu: In Progress 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 To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: Fix Committed Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1641720] Re: Selecting a day does not display all day event for that day
** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => In Progress ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Low ** Branch linked: lp:~3v1n0/indicator-datetime/planner-ignore-previous- day -- 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/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1641726] Re: Tapping a day displays all day event from previous day
** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium ** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => In Progress -- 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/1641726 Title: Tapping a day displays all day event from previous day Status in indicator-datetime package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+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 1641720] Re: Selecting a day does not display all day event for that day
** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete ** No longer affects: unity8 (Ubuntu) -- 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/1641720 Title: Selecting a day does not display all day event for that day Status in indicator-datetime package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed silo #2195 When I select a day from the calendar, I can see events for that day but it does not work with all-day events. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641720/+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 1641726] Re: Tapping a day displays all day event from previous day
I guess this has something to do with the Backend and the timezone... Can you try if you you get the same issue when setting the GMT timezone? ** No longer affects: unity8 (Ubuntu) ** Changed in: indicator-datetime (Ubuntu) Status: New => Incomplete ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1641726 Title: Tapping a day displays all day event from previous day Status in indicator-datetime package in Ubuntu: Incomplete Bug description: bq M10 rc-proposed silo #2195 When I tap on a day there are some events displayed, also from the day before. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641726/+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 1641728] Re: Tapping a day to unselect it shows more events than was there before
Ok, fair enough... This is true when the currentMonth view is visible, and by default we always was resetting to the start of the month, but in this special case we should go back to today. ** No longer affects: unity8 (Ubuntu) ** Package changed: indicator-datetime (Ubuntu) => ubuntu-settings- components (Ubuntu) ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-settings-components (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1641728 Title: Tapping a day to unselect it shows more events than was there before Status in ubuntu-settings-components package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 I tap a day to see events related to day day, the day is selected (color changed to blue). Then I tap that day again to 'unselect' it. The list of events is longer than was before tapping that day in the first place. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641728/+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 1641731] Re: Selecting a day displays more results than expected
Mh, no, the behavior (at least the same we have in unity7 is to show all the events starting from that day. ** Changed in: indicator-datetime (Ubuntu) Status: New => Opinion ** No longer affects: unity8 (Ubuntu) ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Wishlist -- 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/1641731 Title: Selecting a day displays more results than expected Status in indicator-datetime package in Ubuntu: Opinion Bug description: bq M10 rc-proposed silo #2195 When I tap a day I expect to see events for that day only but I can see results from the future too. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1641731/+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 1641724] Re: Tapping the month name has no effect
I guess we can mark the UX side as committed, since the final design wants a combo box for month selection in there. I think this can be a temporary solution, but it will change again. ** No longer affects: unity8 (Ubuntu) ** Package changed: indicator-datetime (Ubuntu) => ubuntu-settings- components (Ubuntu) ** Changed in: ubuntu-ux Status: New => Fix Committed ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => Low -- 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/1641724 Title: Tapping the month name has no effect Status in Ubuntu UX: Fix Committed Status in ubuntu-settings-components package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 I would expect that tapping the month name would display events for that month. Unfortunately the month name is not clickable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1641724/+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 1641722] Re: Tapping a day often results in selecting not the day I wanted to
** No longer affects: indicator-datetime (Ubuntu) ** Package changed: unity8 (Ubuntu) => ubuntu-settings-components (Ubuntu) -- 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/1641722 Title: Tapping a day often results in selecting not the day I wanted to Status in ubuntu-settings-components package in Ubuntu: New Bug description: bq M10 rc-proposed silo #2195 Many times when testing after tapping a day I ended up selecting a day which was below or above the day I was aiming for. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641722/+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 1641721] Re: Tapping on a day near to the screen edge switches to the next month
** No longer affects: indicator-datetime (Ubuntu) ** Package changed: unity8 (Ubuntu) => ubuntu-settings-components (Ubuntu) ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => In Progress -- 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/1641721 Title: Tapping on a day near to the screen edge switches to the next month Status in ubuntu-settings-components package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 Many times when testing after clicking a day on the right hand side (Sundays in my case), the view switched to the next month. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641721/+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 1641719] Re: Opacity for weekend days same as for other days
** Package changed: indicator-datetime (Ubuntu) => ubuntu-settings- components (Ubuntu) ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => Medium -- 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/1641719 Title: Opacity for weekend days same as for other days Status in ubuntu-settings-components package in Ubuntu: In Progress Bug description: bq M10 rc-proposed silo #2195 When I pull down the calendar indicator, I see the opacity (or maybe color) for weekend days is different than for other work days. But when I switch to next month, the opacity is the same for all days. Please see short video with this and other bugs with this silo: https://youtu.be/3vg6AQZmsqE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings-components/+bug/1641719/+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 1639472] Re: Alarm should provide GAction for toggling them
Charles, yes. Basically new desing requires toggalble alarms using a switch from the indicator. So we'd need the backend to do provide an action in order to do that. Devid volunteered to help, but if this is a too big change I can handle that too. -- 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/1639472 Title: Alarm should provide GAction for toggling them Status in indicator-datetime package in Ubuntu: Triaged Bug description: Indicator-datetime should provide a GAaction for toggling the activation of alarms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Please, anyone affected by the leak, could you please run unity-panel- service with debug symbols (for it and indicator-application at least, but all indicators would be better) in massif? -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in Application Menu Indicator: Fix Released Status in Application Menu Indicator 13.10 series: Fix Released Status in The Ubuntu Power Consumption Project: Fix Released Status in Unity: Invalid Status in Ubuntu: Fix Released Status in indicator-appmenu package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in The Saucy Salamander: Fix Released Status in indicator-appmenu source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+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 1639472] [NEW] Alarm should provide GAction for toggling them
Public bug reported: Indicator-datetime should provide a GAaction for toggling the activation of alarms. ** Affects: indicator-datetime (Ubuntu) Importance: Medium Assignee: Devid Antonio Filoni (d.filoni) Status: Triaged -- 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/1639472 Title: Alarm should provide GAction for toggling them Status in indicator-datetime package in Ubuntu: Triaged Bug description: Indicator-datetime should provide a GAaction for toggling the activation of alarms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1506427] Re: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service
I'm not sure if that has happened because the fix was marked as released, however maybe something changed in gtk, but this change is just something right to do, and I'd like to backport it to 16.04, thus the need of fixing it in both. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Status in ido source package in Xenial: New Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1506427] Re: /usr/lib/unity/unity-panel-service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R
** Description changed: + [Impact] + Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. + + [Test Case] + This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. + + [Regression Potential] + Nothing expected, but calendar item in datetime might behave differently on key-presses. + Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. + + === + The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. ** Summary changed: - /usr/lib/unity/unity-panel-service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R + Using calendar with keys might cause Indicator-datetime to crash unity-panel-service -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: Using calendar with keys might cause Indicator-datetime to crash unity-panel-service Status in ido package in Ubuntu: Fix Released Bug description: [Impact] Unity panel service crashes (removing indicators from panel) when calendar menu is opened and there are some key presses. [Test Case] This is a quite random bug that is not easy to reproduce, it happens sometimes that you open the indicator-datetime and after a keypress the panel crashes. [Regression Potential] Nothing expected, but calendar item in datetime might behave differently on key-presses. Although the fix is quite safe since we're just ensuring that we disconnect from parent widget signals on menuitem destruction. === The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1506427] Re: /usr/lib/unity/unity-panel-service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R
** No longer affects: unity (Ubuntu) ** Also affects: ido (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity ** Changed in: ido (Ubuntu) Status: New => In Progress ** Changed in: ido (Ubuntu) Importance: Undecided => Medium ** Changed in: ido (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506427 Title: /usr/lib/unity/unity-panel- service:11:g_type_check_instance_is_a:ido_calendar_menu_item_key_press:_gtk_marshal_BOOLEAN__BOXED:g_closure_invoke:signal_emit_unlocked_R Status in ido package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.3.2+15.10.20151002.2-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/74901303bee889a2ca807616ea267069ad252435 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1506427/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Branch linked: lp:~3v1n0/unity8/calendar-days -- 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/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Also affects: qmenumodel (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings-components (Ubuntu) Importance: Undecided Status: New ** Changed in: qmenumodel (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Status: New => Fix Committed ** Changed in: ubuntu-settings-components (Ubuntu) Status: Fix Committed => In Progress ** Changed in: ubuntu-settings-components (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: qmenumodel (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: indicator-datetime (Ubuntu) Status: New => Invalid ** Changed in: qmenumodel (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-settings-components (Ubuntu) Importance: Undecided => Medium -- 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/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu: In Progress Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1541125] Re: Clicking a date in the new calendar doesn't change the indicator's appointment list
** Changed in: unity8 (Ubuntu) Assignee: Lukáš Tinkl (lukas-kde) => Marco Trevisan (Treviño) (3v1n0) -- 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/1541125 Title: Clicking a date in the new calendar doesn't change the indicator's appointment list Status in Ubuntu UX: New Status in indicator-datetime package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: Now that we've got a calendar in indicator-datetime in Unity 8, there are a few features from Unity 7 that we should decide if/how we're goint to handle in Unity 8. * Show Week Numbers * Highlight days of the month that include appointments * Unity tells indicator-datetime what calendar day has been clicked so that the "upcoming appointments" list can be adjusted accordingly These are currently implemented as fields in a GAction state dictionary and documented in http://bazaar.launchpad.net/~indicator- applet-developers/indicator-datetime/trunk.15.10/view/head:/README ... however that was all done for Unity 7, and IMO it would make sense to improve the unity<->indicator API here so that Unity8 doesn't have to deal with key-variant map GAction states. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1541125/+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 1618886] Re: unity-gtk-module.service is racy
If unity is set as required by ubuntu-session, then stopping unity7 causes the graphical session not to be stopped either... -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+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 1618886] Re: unity-gtk-module.service is racy
More than this unit, it seems related to the fact that it doesn't get deactivated on events such as Xorg being killed. And this is not the only module with this issue. Also gnome-keyring-ssh. In general any script which is on graphical-session doesn't get stopped. And in fact: sudo killall -9 Xorg marco@ubuntu-vmware:~:0$ systemctl --user status graphical-session.target ● graphical-session.target - Current graphical user session Loaded: loaded (/usr/lib/systemd/user/graphical-session.target; static; vendor preset: enabled) Active: active since mer 2016-08-31 13:48:21 CEST; 54s ago Docs: man:systemd.special(7) ago 31 13:48:21 ubuntu-vmware systemd[6159]: Reached target Current graphical user session. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy Status in unity-gtk-module package in Ubuntu: Triaged Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1618886/+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 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
This can't be easily verified, but there are no regressions or crashes. So I'm marking it as verified. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to frame in Ubuntu. https://bugs.launchpad.net/bugs/1350523 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. Status in frame: In Progress Status in compiz package in Ubuntu: Won't Fix Status in frame package in Ubuntu: Fix Released Status in compiz source package in Xenial: Invalid Status in frame source package in Xenial: Fix Committed Bug description: [Impact] Unity might crash on systems with touch screen or multi-gesture supporting touchpads. [Test case] The crash is pretty random, it happens in some cases where unity is locked and after a suspension. Without having to touch any input. [Regression Potential] Regression potential: fix is very safe. We're just removing asserts in code, returning safe values and printing errors instead. Not sure if the cause is running autopilot tests. ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 Signal: 6SourcePackage: compiz StacktraceTop: __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
[Dx-packages] [Bug 1350523] Re: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed.
** Description changed: + [Impact] + + Unity might crash on systems with touch screen or multi-gesture + supporting touchpads. + + [Test case] + + The crash is pretty random, it happens in some cases where unity is + locked and after a suspension. Without having to touch any input. + + [Regression Potential] + + Regression potential: fix is very safe. We're just removing asserts in + code, returning safe values and printing errors instead. + + Not sure if the cause is running autopilot tests. - ProblemType: Crash - DistroRelease: Ubuntu 14.10 + ProblemType: CrashDistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.11+14.10.20140707-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 .tmp.unity.support.test.0: - + .tmp.unity.support.test.1: - + ApportVersion: 2.14.5-0ubuntu1 Architecture: amd64 AssertionMessage: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 30 21:46:07 2014 DistUpgraded: 2014-05-04 22:52:42,676 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: - NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation Device [10de:0491] + NVIDIA Corporation G84GL [Quadro FX 370] [10de:040a] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation Device [10de:0491] InstallationDate: Installed on 2014-02-13 (166 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140211) MachineType: System manufacturer System Product Name ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-6-generic root=UUID=5607f5b0-7033-4580-a503-1d178b40c2b5 ro quiet splash vt.handoff=7 - Signal: 6 - SourcePackage: compiz + Signal: 6SourcePackage: compiz StacktraceTop: - __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 - __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 - frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 - ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 - ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 + __assert_fail_base (fmt=0x7f25565248b0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f2539d8e36f "status == UFStatusSuccess", file=file@entry=0x7f2539d8e364 "device.cpp", line=line@entry=147, function=function@entry=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:92 + __GI___assert_fail (assertion=0x7f2539d8e36f "status == UFStatusSuccess", file=0x7f2539d8e364 "device.cpp", line=147, function=0x7f2539d8e3e0 "float frame_device_get_window_resolution_x(UFDevice)") at assert.c:101 + frame_device_get_window_resolution_x () from /usr/lib/x86_64-linux-gnu/libframe.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 + ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz assert failure: compiz: device.cpp:147: float frame_device_get_window_resolution_x(UFDevice): Assertion `status == UFStatusSuccess' failed. UpgradeStatus: Upgraded to utopic on 2014-05-04 (86 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers dmi.bios.date: 09/13/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd09/13/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1
[Dx-packages] [Bug 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6
** Bug watch added: Debian Bug tracker #833449 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833449 ** Also affects: google-mock (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833449 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to google-mock in Ubuntu. https://bugs.launchpad.net/bugs/1609793 Title: Unity tests crashes when compiling google-mocks with gcc-6 Status in google-mock package in Ubuntu: In Progress Status in google-mock package in Debian: Unknown Bug description: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530 this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/google/googletest/issues/705#issuecomment-235067917 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+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 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6
Here's the debdiff for fixing the ubuntu package ** Patch added: "google-mock-gcc6-action-result-holder-crash-fix.debdiff" https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+attachment/4714016/+files/google-mock-gcc6-action-result-holder-crash-fix.debdiff -- You received this bug notification because you are a member of DX Packages, which is subscribed to google-mock in Ubuntu. https://bugs.launchpad.net/bugs/1609793 Title: Unity tests crashes when compiling google-mocks with gcc-6 Status in google-mock package in Ubuntu: In Progress Bug description: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530 this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/google/googletest/issues/705#issuecomment-235067917 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+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 1609793] Re: Unity tests crashes when compiling google-mocks with gcc-6
** Patch added: "google-mock-gcc6-action-result-holder-crash-fix.patch" https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+attachment/4714014/+files/google-mock-gcc6-action-result-holder-crash-fix.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to google-mock in Ubuntu. https://bugs.launchpad.net/bugs/1609793 Title: Unity tests crashes when compiling google-mocks with gcc-6 Status in google-mock package in Ubuntu: In Progress Bug description: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530 this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/google/googletest/issues/705#issuecomment-235067917 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-mock/+bug/1609793/+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 1609793] [NEW] Unity tests crashes when compiling google-mocks with gcc-6
Public bug reported: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/google/googletest/issues/705#issuecomment-235067917 ** Affects: google-mock (Ubuntu) Importance: Critical Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to google-mock in Ubuntu. https://bugs.launchpad.net/bugs/1609793 Title: Unity tests crashes when compiling google-mocks with gcc-6 Status in google-mock package in Ubuntu: In Progress Bug description: Ubuntu Unity tests fails when using gcc-6, because test-gtest causes a crash. Starting program: /tmp/unity-7.5.0+16.10.20160804/obj-x86_64-linux-gnu/tests/test-gtest [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7fffe0f1d700 (LWP 22778)] [New Thread 0x7fffdbfff700 (LWP 22779)] [New Thread 0x7fffdb7fe700 (LWP 22780)] [==] Running 1637 tests from 105 test cases. [--] Global test environment set-up. [--] 14 tests from TestActionLink [ RUN ] TestActionLink.AligmentCorrectlySetDifferent Thread 1 "test-gtest" received signal SIGSEGV, Segmentation fault. testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 1530 this->UntypedInvokeWith())->GetValueAndDelete(); #0 testing::internal::FunctionMockerBase::InvokeWith(std::tuple<> const&) (args=empty std::tuple, this=0x7fffdb08) at /usr/include/gmock/gmock-spec-builders.h:1530 No locals. #1 testing::internal::FunctionMocker::Invoke() (this=0x7fffdb08) at /usr/include/gmock/gmock-generated-function-mockers.h:76 No locals. #2 unity::dash::ActionLinkMock::QueueDraw (this=0x7fffd3c0) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:43 No locals. #3 0x559ce574 in unity::dash::ActionLink::set_underline (this=0x7fffd3c0, underline=unity::StaticCairoText::NUX_UNDERLINE_NONE) at /tmp/unity-7.5.0+16.10.20160804/tests/../dash/previews/ActionLink.cpp:218 No locals. #4 0x559d53bf in std::function::operator()(unity::StaticCairoText::UnderlineState const&) const (__args#0=, this=0x7fffda00) at /usr/include/c++/6/functional:2136 No locals. #5 nux::RWProperty::Set (this=0x7fffd9c8, value=) at /usr/include/Nux-4.0/NuxCore/Property-inl.h:218 No locals. #6 0x559d0c31 in unity::dash::TestActionLink_UnderlineCorrectlySetDifferent_Test::TestBody (this=) at /tmp/unity-7.5.0+16.10.20160804/tests/test_action_link.cpp:116 A fix is available at https://github.com/goog
[Dx-packages] [Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
What profile are you running? echo $COMPIZ_CONFIG_PROFILE Is lowgfx option enabled in your CCSM settings? gsettings set org.compiz.unityshell:/org/compiz/profiles/unity/plugins/unityshell/ low-graphics-mode false gsettings set org.compiz.unityshell:/org/compiz/profiles/unity/plugins/unityshell/ dash-blur-experimental 2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Marking as verification-needed since a new SRU version has to be landed to fix the crash mentioned above. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Jason, this is bug #1599900, already under our care. Thanks -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
You also have to run unity-control-center with that environment variable: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx unity-control-center This is automatic when this is forced with upstart, otherwise you've to do it by hand. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Ensure that unity-control-center is updated in your machine too. There's a SRU for that too. Also, the lowgfx setting in CCSM isn't enough for doing a full testing. You can also force it by running COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx compiz --replace -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in compiz source package in Xenial: Fix Committed Status in nux source package in Xenial: Fix Committed Status in unity source package in Xenial: Fix Committed Status in unity-control-center source package in Xenial: Fix Committed Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneded redraws
** Description changed: + [Impact] + When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. + + + [Test case] + + This should apply naturally to a (virtual-)machine with no hardware + acceleration or There are multiple ways to force low-gfx mode: + + 1) Add an upstart job such as: + + cat << EOF > ~/.config/upstart/lowgfx.conf + start on starting unity7 + + pre-start script + #initctl set-env --global UNITY_LOW_GFX_MODE=1 + initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 + end script + EOF + + + 2) Run unity with: +COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx + + On login unity should use opaque views (dash, switcher, launcher, + shortcut-dialogs) with no fading and reduced effects. Windows should + also use smaller shadows. + + + [Regression potential] + + Some settings from unity-control-center couldn't be applied to normal + profile. Low graphics mode might be used as normal one. -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Bug description: [Impact] When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. [Test case] This should apply naturally to a (virtual-)machine with no hardware acceleration or There are multiple ways to force low-gfx mode: 1) Add an upstart job such as: cat << EOF > ~/.config/upstart/lowgfx.conf start on starting unity7 pre-start script #initctl set-env --global UNITY_LOW_GFX_MODE=1 initctl set-env --global LIBGL_ALWAYS_SOFTWARE=1 end script EOF 2) Run unity with: COMPIZ_CONFIG_PROFILE=ubuntu-lowgfx On login unity should use opaque views (dash, switcher, launcher, shortcut-dialogs) with no fading and reduced effects. Windows should also use smaller shadows. [Regression potential] Some settings from unity-control-center couldn't be applied to normal profile. Low graphics mode might be used as normal one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneded redraws
** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity-control-center (Ubuntu) Status: New => In Progress ** Changed in: unity-control-center (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: In Progress Status in unity-control-center package in Ubuntu: In Progress Bug description: When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneded redraws
** Branch linked: lp:~3v1n0/unity/upstart-lowgfx-profile ** Branch linked: lp:~3v1n0/unity/lowgfx-mode-less-effects ** Changed in: compiz (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: nux (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: In Progress Status in nux package in Ubuntu: In Progress Status in unity package in Ubuntu: In Progress Bug description: When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] Re: Unity in low-graphics mode has animations and unneded redraws
** Branch linked: lp:~3v1n0/compiz/unity-lowgfx-profile -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: In Progress Status in nux package in Ubuntu: In Progress Status in unity package in Ubuntu: In Progress Bug description: When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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 1598770] [NEW] Unity in low-graphics mode has animations and unneded redraws
Public bug reported: When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. ** Affects: compiz (Ubuntu) Importance: High Status: In Progress ** Affects: nux (Ubuntu) Importance: High Status: In Progress ** Affects: unity (Ubuntu) Importance: High Status: In Progress ** Changed in: unity (Ubuntu) Status: New => In Progress ** Changed in: unity (Ubuntu) Importance: Undecided => High ** Also affects: compiz (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz (Ubuntu) Status: New => In Progress ** Changed in: compiz (Ubuntu) Importance: Undecided => High ** Also affects: nux (Ubuntu) Importance: Undecided Status: New ** Changed in: nux (Ubuntu) Status: New => In Progress ** Changed in: nux (Ubuntu) Importance: Undecided => High ** Branch linked: lp:~3v1n0/nux/support-test-llvmpipe-check ** Branch linked: lp:~hikiko/unity/unity.multimonitor-speed-up -- You received this bug notification because you are a member of DX Packages, which is subscribed to nux in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneded redraws Status in compiz package in Ubuntu: In Progress Status in nux package in Ubuntu: In Progress Status in unity package in Ubuntu: In Progress Bug description: When unity is in Low graphics mode (because of software rendering) there are still window animations and fade effects which we should get rid of. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+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
