[Bug 2023572] Re: SRU gjs 1.72.4 to jammy
You still get The following packages have been kept back: gjs (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) libgjs0g (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) all the time. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037235] [NEW] 45.0: vsync broken in many games, with dual monitors
Public bug reported: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3035 https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037235 Title: 45.0: vsync broken in many games, with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037235/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
I was distracted by https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 so I haven't had time to test this as much... ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3035 https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
It's very easy to reproduce for me, it happens very quickly every time when I put a fullscreen window on the second monitor. I can probably get a some logs later... But perhaps wait until the updated mutter & gnome-shell are out of Proposed? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Still happens when I have only MUTTER_DEBUG_KMS_THREAD_TYPE=user. TRIPLE_BUFFERING=never seems to be the only workaround. Hope we can get a new snapshot in Mantic soon then! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
I have been running with MUTTER_DEBUG_TRIPLE_BUFFERING=never as my only debug option since last I wrote and haven't been able to reproduce it. So I'll try the KMS_THREAD_TYPE now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
I got it again now with $HOME/.config/environment.d/debug.conf : MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 MUTTER_DEBUG_FORCE_KMS_MODE=simple Of course, all the triple buffering patches are still there. Haven't tried vanilla mutter/gnome-shell yet. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
Now this happened again with MUTTER_DEBUG_FORCE_KMS_MODE=simple set. I'm going to try to disable extensions instead... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
This happened to me with both Nvidia and AMD graphics. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
I tested MUTTER_DEBUG_TRIPLE_BUFFERING=never first and it made no difference. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: [Lunar] Irregular FPS with Path of Exile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016990] Re: [Lunar] Irregular FPS with Path of Exile
If I set CLUTTER_PAINT=disable-dynamic-max-render-time it fixes the issue! I only had that variable set during the test. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: [Lunar] Irregular FPS with Path of Exile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016990] [NEW] [Lunar] Irregular FPS with Path of Exile
Public bug reported: I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: [Lunar] Irregular FPS with Path of Exile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2016990/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 953202] Re: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:273: poll_for_event: Försäkran \"!xcb_xlib_threads_sequence_lost\" falsk.
** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/953202 Title: gnome-settings-daemon assert failure: gnome-settings-daemon: ../../src/xcb_io.c:273: poll_for_event: Försäkran \"!xcb_xlib_threads_sequence_lost\" falsk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/953202/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info
Seems like there was a follow up problem? https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2655 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988256] Re: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info
Cherry pick fixes to 22.04? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988256 Title: gnome-shell crashed with SIGSEGV in meta_get_first_subsurface_node() from pointer_can_grab_surface() from meta_wayland_pointer_can_grab_surface() from meta_wayland_seat_get_grab_info() from token_can_activate() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1988256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
I'm also seeing this. eglinfo ends with: Device platform: eglinfo: eglInitialize failed es2_info says: EGL_CLIENT_APIS: OpenGL OpenGL_ES GL_VERSION: OpenGL ES 3.2 Mesa 22.0.0 GL_RENDERER: Mesa Intel(R) UHD Graphics 620 (WHL GT2) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1966418/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1918033] Re: gnome-shell crashes when clearing notifications
It happened to me when I cleared notifications and there was a Firefox media notification plus other notifications. A Firefox media notification alone was not enough to trigger the bug. I think I uploaded a crash with id 02e64840-7e78-11eb-941e-fa163ee63de6 but I have no idea how to find it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1918033 Title: gnome-shell crashes when clearing notifications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918033/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
@zaf Yes, please ppa-purge my ppa when the fix is merged to the ubuntu
main repo.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
I've put the fix in my ppa:
https://launchpad.net/~ernstp/+archive/ubuntu/gnome
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
It should definitively be visible here... https://errors.ubuntu.com/?release=Ubuntu%2020.04=gnome-shell=week -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866256] Re: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking
This is still happening to me. Enabling animations again solved it. Could it be related to Yaru GTK theme or Yaru shell theme? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866256 Title: Disabled animations breaks lock screen and other dialogs, reveals information from the screen without unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866256/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1719985] Re: flatpak software is not shown in gnome-software
It's not showing any updates for me in 19.10, and hasn't for quite some
time.
19:59:08:0937 Gs autogenerating unique-id for com.spotify.Client.desktop
19:59:08:0937 GsPluginFlatpak com.spotify.Client has a downloaded update
8b984d9a880fc4a894fc3c8199347ac88062c712dbb2e50abc2ad6262bf8->d3b733de029f89e31939f8b5c27df7d203cbea6a6212468d93a42e1d08fbd3a3
19:59:08:0937 Gs not adding duplicate
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable as
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable already exists
19:59:08:0938 Gs searching appstream for
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable
19:59:08:0938 Gs no app with ID
system/flatpak/flathub/desktop/com.spotify.Client.desktop/stable found in
system appstream
19:59:08:0938 Gs no AppStream match for {pkgname}
app/com.spotify.Client/x86_64/stable
19:59:08:0938 GsPluginFlatpak chose GsFlatpak-system-default using ID
19:59:08:0938 Gs installable update 1.1.10.546 [0]
19:59:08:0938 Gs installable update 1.1.5.153 [0]
19:59:08:0938 Gs installable update 1.1.0.237 [0]
19:59:08:0938 Gs installable update 1.0.98.78 [0]
19:59:08:0938 Gs installable update 1.0.96.181 [0]
19:59:08:0938 Gs installable update 1.0.94.262 [0]
19:59:08:0938 Gs installable update 1.0.92.390 [0]
19:59:08:0938 Gs installable update 1.0.89.313 [0]
19:59:08:0938 GsPluginFlatpak com.spotify.Client is not installed, so ignoring
version of 1.1.10.546
19:59:08:0938 GsPluginFlatpak skipping reading metadata
19:59:08:0939 GsPluginFlatpak chose GsFlatpak-system-default using ID
19:59:08:0939 Gs installable update 1.1.10.546 [0]
19:59:08:0939 Gs installable update 1.1.5.153 [0]
19:59:08:0939 Gs installable update 1.1.0.237 [0]
19:59:08:0939 Gs installable update 1.0.98.78 [0]
19:59:08:0939 Gs installable update 1.0.96.181 [0]
19:59:08:0939 Gs installable update 1.0.94.262 [0]
19:59:08:0939 Gs installable update 1.0.92.390 [0]
19:59:08:0939 Gs installable update 1.0.89.313 [0]
19:59:08:0939 GsPluginFlatpak com.spotify.Client is not installed, so ignoring
version of 1.1.10.546
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1719985
Title:
flatpak software is not shown in gnome-software
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1719985/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] Re: Extensions are disabled after unlocking the screen
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1800477] Re: Extensions are disabled after unlocking the screen
I think I have this problem too. I also have this in my session log: oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: == Stack trace for context 0x55f6851611c0 == oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #0 7ffc4b206740 b resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7fd1489cc040 @ 25) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #1 55f697d100f0 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:416 (7fd116ba3dc0 @ 20) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #2 7ffc4b2076e0 b self-hosted:261 (7fd1489c1dc0 @ 223) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #3 55f697d10038 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:415 (7fd116ba3d30 @ 172) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #4 7ffc4b2087f0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fd1489b0b80 @ 71) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #5 55f697d0ff58 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/theming.js:235 (7fd116ba39d0 @ 102) oct. 29 12:06:20 sark org.gnome.Shell.desktop[6838]: #6 7ffc4b209760 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7fd1489b0b80 @ 71) .. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1800477 Title: Extensions are disabled after unlocking the screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800477/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1777115] [NEW] gnome-shell crashed with stacktrace
Public bug reported: Gnome-shell looked like it crashed, I got the traditional blinking of the window manager etc. However I still have 4580 ernsjo20 0 5822836 2,164g 109184 S 1,7 6,9 309:41.18 gnome-shell in top, so it looks like it didn't really crash (high memory usage and long running time). gnome-shell 3.28.1-0ubuntu2 jun 15 11:15:00 edesk evolution-alarm[2240]: GtkDialog mapped without a transient parent. This is discouraged. jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: Object St.BoxLayout (0x560373857b10), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroye jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: == Stack trace for context 0x5603268604b0 == jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #0 0x560326d19e48 i resource:///org/gnome/shell/ui/popupMenu.js:717 (0x7fed9ae262b8 @ 22) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #1 0x7ffef656d740 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #2 0x7ffef656ded0 b resource:///org/gnome/shell/ui/popupMenu.js:735 (0x7fed9ae26560 @ 23) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #3 0x7ffef656df30 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #4 0x560326d19dc0 i /home/ernsjo/.local/share/gnome-shell/extensions/sensory-percept...@harlemsquirrel.github.io/extension.js:100 (0x7fed6a59f6f8 @ 4 jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #5 0x7ffef656eb30 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #6 0x7ffef656f2d0 b self-hosted:915 (0x7fedc40f12b8 @ 367) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #7 0x7ffef656f3c0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7fedc40d3230 @ 386) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #8 0x560326d19d38 i resource:///org/gnome/shell/ui/panelMenu.js:194 (0x7fed9ae7a230 @ 94) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #9 0x7ffef6570030 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7fedc40b5de0 @ 71) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #10 0x560326d19cc0 i /home/ernsjo/.local/share/gnome-shell/extensions/sensory-percept...@harlemsquirrel.github.io/extension.js:276 (0x7fed6a59fe68 @ jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #11 0x560326d19c00 i resource:///org/gnome/shell/ui/extensionSystem.js:82 (0x7fed9ae5a120 @ 431) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #12 0x560326d19b78 i resource:///org/gnome/shell/ui/extensionSystem.js:184 (0x7fed9ae5a340 @ 18) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #13 0x560326d19ac0 i resource:///org/gnome/shell/ui/extensionSystem.js:199 (0x7fed9ae5a3c8 @ 81) jun 15 11:15:00 edesk org.gnome.Shell.desktop[4580]: #14 0x560326d19a20 i resource:///org/gnome/shell/ui/extensionSystem.js:299 (0x7fed9ae5a808 @ 76) jun 15 11:15:00 edesk gnome-software[5173]: State change on user/*/*/shell-extension/sensory-perception_HarlemSquirrel.github.io/* from installed to available is not OK jun 15 11:15:00 edesk gnome-software[5173]: State change on user/*/*/shell-extension/sensory-perception_HarlemSquirrel.github.io/* from available to installed is not OK jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed jun 15 11:15:00 edesk gnome-software[5173]: State change on user/*/*/shell-extension/mediaplayer_patapon.info/* from installed to available is not OK jun 15 11:15:00 edesk gnome-software[5173]: State change on user/*/*/shell-extension/mediaplayer_patapon.info/* from available to installed is not OK jun 15 11:15:00 edesk gnome-shell[4580]: g_signal_handler_disconnect: assertion 'handler_id > 0' failed
[Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
apt-cache depends libegl1 libegl1 Depends: libc6 Depends: libglvnd0 |Depends: libegl-mesa0 Depends: libegl-mesa0 libnvidia-gl-390 For some reason libnvidia-gl-390 existed on my system (no nvidia hardware in this system). That caused libegl-mesa0 to not be installed and that broke my system. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
Thanks Eugene, that finally solved it for me. Happened when I upgraded my Intel-only system to Bionic just now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709667] Re: Missing desktop scaling slider in system settings
2x scaling used to be configured automatically for 4k screens, wasn't it? Also, the new control center panel for monitors has a monitor scale that you can set to 200% but that doesn't seem to do anything. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1709667 Title: Missing desktop scaling slider in system settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1709667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome
Got it: sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming Keyboard: failed to receive: timeout sep 15 19:39:45 mammut fwupd[2591]: failed to open: failed to ping G15 Gaming Keyboard: failed to send: failed to write: wrote -1 of 7 r Uninstalling fwupd solves it. Now let's see how to fix this properly... ** Package changed: gnome-shell (Ubuntu) => fwupd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome
Ok more clues. My keyboard is a Logitech G15 Gaming keyboard. It has lots of features, which present themselves to Linux as various devices. The regression somewhere around that. And it's a userspace regression, the same kernel with Ubuntu 17.04 works fine. If I connect a very plain USB keyboard that works fine, it's only the G15 that's giving problems. So here's xinput from a Ubuntu where it works: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Razer Razer DeathAdder Chroma id=10 [slave pointer (2)] ⎜ ↳ Razer Razer DeathAdder Chroma id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ G15 Gaming Keyboard id=8[slave keyboard (3)] ↳ G15 Gaming Keyboard id=9[slave keyboard (3)] ↳ Razer Razer DeathAdder Chroma id=12 [slave keyboard (3)] ↳ G15 GamePanel LCD id=13 [slave keyboard (3)] ↳ Eee PC WMI hotkeysid=14 [slave keyboard (3)] ** Summary changed: - [artful] Keyboard doesn't work after logging in to gnome + [artful] Keyboard Logitech G15 doesn't work after logging in to gnome -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] Re: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome
xinput when it's broken: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Razer Razer DeathAdder Chroma id=10 [slave pointer (2)] ⎜ ↳ Razer Razer DeathAdder Chroma id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ G15 Gaming Keyboard id=8[slave keyboard (3)] ↳ G15 Gaming Keyboard id=9[slave keyboard (3)] ↳ Razer Razer DeathAdder Chroma id=12 [slave keyboard (3)] ↳ G15 GamePanel LCD id=13 [slave keyboard (3)] ↳ Eee PC WMI hotkeysid=14 [slave keyboard (3)] ↳ Razer Razer DeathAdder Chroma id=15 [slave keyboard (3)] -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard Logitech G15 doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] Re: [artful] Keyboard doesn't work after logging in to gnome
Damn, I was certain that it was solved exactly when toggling Slow Keys, but next time that didn't work. It's interesting that the problem remains after logging out, so I can't type my password anymore and log in a second time. Suggests it's outside the user session somehow... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] Re: [artful] Keyboard doesn't work after logging in to gnome
Also it doesn't matter if I use Gnome Xorg or Wayland or Ubuntu Xorg or Wayland. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717340] [NEW] [artful] Keyboard doesn't work after logging in to gnome
Public bug reported: After I type my password in GDM and come to the gnome desktop, no keys are working. Not even caps lock toggling. However, I found out that if I toggle "Slow keys" in the accessibility settings, it starts working again! To clarify, Slow keys and all other accessibility is disabled from start, but turning Slow keys on and off again makes my keyboard work. I seem to have to do this once after every _reboot_. This is on a system that has upgraded to Artful. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu5 Uname: Linux 4.13.0-rc2+ x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 14 21:04:46 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-08-29 (16 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1717340 Title: [artful] Keyboard doesn't work after logging in to gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717340/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C
Could this be why I sometimes get no keyboard input at all in my user sessions in Artul...? (Can type password in GDM, but then all keyboard input is lost until reboot.) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1710637/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1314556] Re: Unable to mount Android MTP device
None of my MTP Android phones are detected by the desktop at all, worked perfectly in 12.04. Sony Xperia ZR for example. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1314556 Title: Unable to mount Android MTP device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1314556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296275] Re: PTP Cameras not working on 14.04, works flawlessly on 12.04
Mounting my android phone with mtp worked flawlessly in 12.04 but not in 14.04. It seems that was not fixed by this change. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1296275 Title: PTP Cameras not working on 14.04, works flawlessly on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1296275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1171943] Re: Shut down and logout dialog not show
It was simply a case of org.gnome.gnome-session.logout-prompts dconf key being set to false! ** Changed in: gnome-session (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1171943 Title: Shut down and logout dialog not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1171943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1171943] Re: Shut down and logout dialog not show
It was simply a case of org.gnome.gnome-session.logout-prompts dconf key being set to false! ** Changed in: indicator-session (Ubuntu) Status: Confirmed = Invalid ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1171943 Title: Shut down and logout dialog not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1171943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1171943] Re: Shut down and logout dialog not show
** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: indicator-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1171943 Title: Shut down and logout dialog not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1171943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1171943] Re: Shut down and logout dialog not show
Also if I choose logout it doesn't show the confirmation dialog either, it simply logs out directly! ** Summary changed: - Shut down dialog not show, restarts instead + Shut down and logout dialog not show -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1171943 Title: Shut down and logout dialog not show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1171943/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1171943] [NEW] Shut down dialog not show, restarts instead
Public bug reported: This started when I upgraded to Raring. When I select shut down, I don't get the shut down dialog. Instead, the desktop exits immediately and then the computer reboots instead of shutting down!! I ran annotate-output tail -f .xsession-errors on another VT and this is what it captured after choosing shut down. I'm running Swedish locale. 19:18:13 O: error : string is not in UTF-8 19:18:13 O: encoding error : output conversion failed due to conv error, bytes 0xF6 0x73 0x74 0x72 19:18:13 O: I/O error : encoder error 19:18:13 O: error : string is not in UTF-8 19:18:13 O: encoding error : output conversion failed due to conv error, bytes 0xF6 0x73 0x74 0x72 19:18:13 O: I/O error : encoder error 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (gnome-settings-daemon:2364): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying to remove a child that doesn't believe we're its parent. 19:18:13 O: 19:18:13 O: (Pidgin:2409): LIBDBUSMENU-GLIB-WARNING **: Trying
[Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
I think a goal should be to avoid forcing users to do unclean shutdowns with the power button etc. If I'm logged in but not at home and my wife wants to turn off the computer, she should be able to even though she's not an admin. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1068668] Re: Contact photos icons are too big
*** This bug is a duplicate of bug 1049598 *** https://bugs.launchpad.net/bugs/1049598 ** Changed in: empathy (Ubuntu) Status: Incomplete = Confirmed ** This bug has been marked a duplicate of bug 1049598 Cannot change avatar size in contact list -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1068668 Title: Contact photos icons are too big To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1068668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1049598] Re: Cannot change avatar size in contact list
This is from the duplicate: #1068668 ** Attachment added: empathy_12_10.jpg https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1049598/+attachment/3409225/+files/empathy_12_10.jpg ** Changed in: empathy (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1049598 Title: Cannot change avatar size in contact list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1049598/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
Why are you talking about notifications and password prompts, the computer should shut down (by default) of course! It could prompt and say X is logged in, are you really sure you want to shut down? but nothing more. If an admin wants to disable it there should be a way to do that instead. Let's say I'm logged in but I'm not at home and my wife wants to shut down the computer. Of course she should be allowed to! Therefore I think setting org.freedesktop.consolekit.system.stop- multiple-users to allow_active=yes is a great and correct solution. What's missing there is a local override solution so and admin of a multi-seat server could turn it off for example without having it overwritten everytime policykit updates. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 855556] Re: Restart and Shut Down don't work if anyone else is logged in
The temporary workaround is to edit /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy (every time it's updated) and in org.freedesktop.consolekit.system.restart-multiple-users and org.freedesktop.consolekit.system.stop-multiple-users set allow_activeyes/allow_active -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/86 Title: Restart and Shut Down don't work if anyone else is logged in To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/86/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 975157] Re: Can't reboot/shutdown with two user logged in
This could be policy-kit related. Can't find any error messages about the problem in /var/log ** Also affects: policykit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/975157 Title: Can't reboot/shutdown with two user logged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/975157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 975157] Re: Can't reboot/shutdown with two user logged in
** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/975157 Title: Can't reboot/shutdown with two user logged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/975157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 828756] Re: getting connection is untrusted warnings
I haven't seen this problem in a very long time now! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/828756 Title: getting connection is untrusted warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/828756/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 942131] [NEW] Sometimes I have to select logout/shut down twice before it has effect
Public bug reported: Sometimes I have to select logout/shut down twice before it has effect. I can wait a long time after the first try but nothing happens. On the second try I log out immediately. It doesn't happen all the time. Any tips what I could debug, check logs from, to solve this? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session 3.2.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.93-0ubuntu2 Architecture: amd64 Date: Mon Feb 27 18:38:20 2012 PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-02-07 (20 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/942131 Title: Sometimes I have to select logout/shut down twice before it has effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/942131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 942131] Re: Sometimes I have to select logout/shut down twice before it has effect
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/942131 Title: Sometimes I have to select logout/shut down twice before it has effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/942131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 942131] Re: Sometimes I have to select logout/shut down twice before it has effect
This is not a recent regression, I had this problem in Oneiric also, but probably not before that. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/942131 Title: Sometimes I have to select logout/shut down twice before it has effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/942131/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 535168] Re: yelp crashed with signal 5 in _XError()
I don't think this happens anymore? ** Changed in: yelp (Ubuntu) Status: Triaged = Invalid ** Changed in: yelp (Ubuntu Lucid) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/535168 Title: yelp crashed with signal 5 in _XError() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/535168/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 28828] Re: gstreamer0.10-plugins-ugly has inadequate documentation and package description.
** Changed in: gst-plugins-ugly0.10 (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gst-plugins-ugly0.10 in Ubuntu. https://bugs.launchpad.net/bugs/28828 Title: gstreamer0.10-plugins-ugly has inadequate documentation and package description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-ugly0.10/+bug/28828/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 546578]
I'm pretty sure this is fixed now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/546578 Title: black screen after a few user switches To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/546578/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475090] Re: Karmic, Lucid: /etc/gdm/Xsession fails to source ~/.xsessionrc or apply ~/.Xresources
** Tags added: regression-potential -- Karmic, Lucid: /etc/gdm/Xsession fails to source ~/.xsessionrc or apply ~/.Xresources https://bugs.launchpad.net/bugs/475090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 523949] Re: the csd changes make some desktop applications hog the cpu
You can quickly test this with the gtkperf tool. gtk+2.0 2.19.5-1ubuntu2: 5 - 5:30 secs gtk+2.0 2.19.5-1ubuntu3: ~9 secs gtk+2.0 2.19.5-1ubuntu4: ~9 secs -- the csd changes make some desktop applications hog the cpu https://bugs.launchpad.net/bugs/523949 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475090] Re: Karmic /etc/gdm/Xsession fails to source ~/.xsessionrc or apply ~/.Xresources
Right so the new GDM runs all the scripts in /etc/X11/Xsession.d/* _BUT_, it doesn't run /etc/X11/Xsession which sets up the USERXSESSIONRC variable. So my workaround was to simply add USERXSESSIONRC=$HOME/.xsessionrc to the beginning of /etc/X11/Xsession.d/40x11-common_xsessionrc -- Karmic /etc/gdm/Xsession fails to source ~/.xsessionrc or apply ~/.Xresources https://bugs.launchpad.net/bugs/475090 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
