[Bug 2037460] Re: gnome-shell crash
there's nothing in /var/crash or in errors.ubuntu.com ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
-b -1 ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704967/+files/prevjournal.txt -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
-b 0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704966/+files/journal.txt -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] [NEW] gnome-shell crash
Public bug reported: gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug? ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 26 11:28:15 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (1502 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015577] Re: middle click to lower window no longer works for xwayland windows
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2778 https://gitlab.gnome.org/GNOME/mutter/-/issues/2778 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2778 Importance: Unknown Status: Unknown ** Also 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/2015577 Title: middle click to lower window no longer works for xwayland windows To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click
looks like https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5070 addresses this in gtk3 apps, can it (and/or the next gtk release) be added to the ubuntu package and the snap package that contains gtk3 (gnome-* snap?) -- 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/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1971744] [NEW] external monitor static image after unlocking session
Public bug reported: Occasionally after unlocking a locked gnome session, the image on my external monitor is "frozen" -- it displays the unlocked desktop as of the lock/unlock time, but does not update (no mouse cursor etc). Started noticing this post-jammy release. Unplugging and replugging the monitor fixes it. Internal laptop display does not have the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 5 09:17:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (992 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (47 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1971744 Title: external monitor static image after unlocking session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1964541] Re: Cannot use Drag and Drop in gnome-shell 42 (Wayland session)
is there a way for users to re-enable wayland / override the DISABLE_WAYLAND=1 setting recently set in the snap? -- 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/1964541 Title: Cannot use Drag and Drop in gnome-shell 42 (Wayland session) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966593] [NEW] gnome session locks when disconnecting external screen
Public bug reported: After upgrade to jammy, noticed that the gnome session locks the screen when I unplug an external screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sun Mar 27 08:49:28 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (953 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-03-18 (8 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1966593 Title: gnome session locks when disconnecting external screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965648] Re: Autorotate initiates, but doesn't reset
One more piece of information in a wayland session: If I fully fold the device into tablet mode, then I can rotate back and forth successfully, it only gets stuck if I go back into laptop mode. -- 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/1965648 Title: Autorotate initiates, but doesn't reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963264] Re: Screencast not recording
I had pipewire-media-session libpipewire-0.3-common installed fine after an upgrade from impish->jammy, but still had to remove the libgstpipewire so, and reinstall the package to get gstreamer to recognize the pipewiresrc element -- 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/1963264 Title: Screencast not recording To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965648] Re: Autorotate initiates, but doesn't reset
The bug does not appear to occur under Xorg sessions: - Ubuntu on Xorg: rotated back and forth numerous times successfully - Ubuntu: rotated back and forth once successfully and then got stuck in portrait mode - Gnome on Xorg: rotated back and forth numerous times successfully - Gnome: rotated back and forth once successfully and then got stuck in portrait mode ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+attachment/5571502/+files/journal.txt ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1965648 Title: Autorotate initiates, but doesn't reset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1965648] [NEW] Autorotate initiates, but doesn't reset
Public bug reported:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape mode. Flipping it around ("left-up") does swap
to the reverse portrait mode, but still can't get back to "normal"
afterward.
running `monitor-sensor` does show the accelerometer orientation change
events (including the "normal" ones) triggering properly, just the
desktop doesn't respond.
Plugging in an external monitor does seem to trigger the desktop to go
back to normal landscape mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:41:42 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
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/1965648
Title:
Autorotate initiates, but doesn't reset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1898080] [NEW] Dsiplay artifacts in groovy when moving windows around
Public bug reported: In a wayland session with fractional scaling (175% on laptop screen), seeing weird visual artifacts around windows when moving them around, see attached video for an example. Also see similar artifacts near terminal prompt, gtk file chooser when mousing over items, and maybe other locations too? artifacts do not appear on external monitor set to 100% scaling, or on laptop screen if scaling is set to 100%, 150%, or 200%. ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Attachment added: "PXL_20201001_164915228.mp4" https://bugs.launchpad.net/bugs/1898080/+attachment/5416237/+files/PXL_20201001_164915228.mp4 -- 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/1898080 Title: Dsiplay artifacts in groovy when moving windows around To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1898080/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1867819] [NEW] Dark theme current line highlight hard to read
Public bug reported: In focal, with a dark theme (adwaita-dark), the current line highlight in almost the same color as the text, making it very hard to read. see screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.0-3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 17 11:28:29 2020 InstallationDate: Installed on 2019-08-17 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: gedit UpgradeStatus: Upgraded to focal on 2020-03-06 (11 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "Screenshot from 2020-03-17 11-28-41.png" https://bugs.launchpad.net/bugs/1867819/+attachment/5338089/+files/Screenshot%20from%202020-03-17%2011-28-41.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1867819 Title: Dark theme current line highlight hard to read To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1867819/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866851] Re: lock screen scaled down backgound image in top left corner
Looks like already reported, linked to existing bug ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2239 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2239 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/1866851 Title: lock screen scaled down backgound image in top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866851] [NEW] lock screen scaled down backgound image in top left corner
Public bug reported: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "IMG_20200310_073917.jpg" https://bugs.launchpad.net/bugs/1866851/+attachment/5335362/+files/IMG_20200310_073917.jpg ** Description changed: - The new lock screen in gnome 3.26 looks strange, as if the blurred + The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) -- 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/1866851 Title: lock screen scaled down backgound image in top left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866851/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
3.34.1+git20191107-1ubuntu1~19.10.1 appears to fix the issue here. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
Have seen it both with the internal laptop keyboard as well as an external USB keyboard -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
Initial testing does make it look like an Xorg session behaves better in this regard than a wayland session (using vanilla gnome sessions in both, fwiw) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1848086] [NEW] Keyboard shortcuts to launch apps sometimes launch twice
Public bug reported: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1848086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844575] Re: Pixelated fonts sometimes
agree that mutter#804 is the upstream issue -- 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/1844575 Title: Pixelated fonts sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845031] [NEW] gnome not remembering numlock state in eoan
Public bug reported: in 3.34, gnome-settings-daemon has removed its handling of numlock state persistence, claiming that mutter should be handling that now (https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f). However, numlock is always off when I start a session, and does not get remembered when I turn it on, log out, and log back in. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 23 11:15:27 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1845031 Title: gnome not remembering numlock state in eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844575] Re: Pixelated fonts sometimes
** Attachment added: "Screenshot from 2019-09-18 12-59-08.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+attachment/5289524/+files/Screenshot%20from%202019-09-18%2012-59-08.png -- 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/1844575 Title: Pixelated fonts sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1844575] [NEW] Pixelated fonts sometimes
Public bug reported: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1844575 Title: Pixelated fonts sometimes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1822846] Re: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock)
looks ok in initial testing on 3.32.1-1ubuntu1~19.04.1 On Mon, May 6, 2019 at 5:41 AM Łukasz Zemczak <1822...@bugs.launchpad.net> wrote: > Hello Julian, or anyone else affected, > > Accepted gnome-shell into disco-proposed. The package will build now and > be available at https://launchpad.net/ubuntu/+source/gnome- > shell/3.32.1-1ubuntu1~19.04.1 in a few hours, and then in the -proposed > repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-disco to verification-done-disco. If it does not fix > the bug for you, please add a comment stating that, and change the tag > to verification-failed-disco. In either case, without details of your > testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: gnome-shell (Ubuntu Disco) >Status: In Progress => Fix Committed > > ** Tags added: verification-needed verification-needed-disco > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1822846 > > Title: > Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not > the ubuntu-dock) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1822846/+subscriptions > ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1822846 Title: Icon disappears from favorites in gnome-shell 3.32 (upstream dock, not the ubuntu-dock) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821427] Re: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe err
Not sure if related, but I do run under wayland (weird that it looks like an X11 error then, especially as evolution runs wayland native?), with fractional zooming on my laptop panel @ 175% and usually have an external, lower resolution screen at 100% scaling. Evolution is usually the first app i open and stays open throughout my session, so has usually been running for days before being closed (and killing the session) -- but sometimes closing it is fine. Haven't seen any other app trigger 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/1821427 Title: gnome-shell crashed with signal 5 when closing evolution, logging "The program 'gnome-shell' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n (Details: serial 333851 error_code 3 r" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821427/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
downgrading to the 1.2.0 bios on xps 9575 appears to be working properly (tested 3 reboots with no issues) -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after boot
Perhaps this is somehow related to the convertible lid hinge. Ordinarily when the laptop is in "tablet" mode (hinge open > 180 degrees), the keyboard and touchpad are disabled. Even more reliably than using an external device, switching into and then back out of tablet mode by opening/closing the hinge seems to restore keyboard/touchpad functionality. Not sure why they appear to work until the gdm screen though, or why sometimes using an external device causes them to work again. -- 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/1822394 Title: [Dell XPS 15 9575] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1820355] Re: Firefox icon is blank in the launcher
appears the logo can disappear again after being restored, and then can be restored again via changing the icon theme again. -- 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/1820355 Title: Firefox icon is blank in the launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot
additionally, forcing gdm to use X11 via `WaylandEnable=false` in /etc/gdm3/custom.conf displays the same bug behavior. -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot
Tests this morning seem to show that the internal devices get enabled right after any input from an external device on the gdm screen. So choice of session isn't influencing anything. -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot
** Attachment added: "allpackages.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+attachment/5251405/+files/allpackages.txt -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot
will try the ubuntu sessions tomorrow. I normally run the gnome (wayland) session, but have keepass2 in startup applications. Believe that it is running via xwayland, and its approximately when keepass2 starts up and/or gains focus that my laptop touchpad/keyboard start working again. -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] Re: laptop keyboard & touchpad not working at gdm screen after boot
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+attachment/5251406/+files/journal.txt -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822394] [NEW] laptop keyboard & touchpad not working at gdm screen after boot
Public bug reported: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results in the laptop touchpad and keyboard working on the gdm screen. Did not see this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had not rebooted in a while, so not sure if bios or package upgrades triggered this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session ** Description changed: - On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and - keyboard are unresponsive at the gdm login screen. Keyboard works to - unlock encrypted harddrive before that though. If I plug in a USB - keyboard or activate my bluetooth mouse, I can use those to log in, and - then after logging in the laptop touchpad and keyboard work again. + On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results + in the laptop touchpad and keyboard working on the gdm screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) ** Description changed: On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard are unresponsive at the gdm login screen. Keyboard works to unlock encrypted harddrive before that though. If I plug in a USB keyboard or activate my bluetooth mouse, I can use those to log in, and then after logging in the laptop touchpad and keyboard work again. Logging out of the desktop results - in the laptop touchpad and keyboard working on the gdm screen. + in the laptop touchpad and keyboard working on the gdm screen. Did not see + this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had + not rebooted in a while, so not sure if bios or package upgrades triggered + this behavior. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 29 17:51:00 2019 InstallationDate: Installed on 2018-09-26 (184 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago) -- 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/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821262] Re: gnome-shell crashes when closing evolution
Reproduced with all extensions disabled, and filed to bug 1821427 -- 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/1821262 Title: gnome-shell crashes when closing evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1821262] [NEW] gnome-shell crashes when closing evolution
Public bug reported: Had this happen a few times now, where closing the main evolution window results in a gnome-shell crash: Mar 21 16:55:18 taplop gnome-shell[2552]: The program 'gnome-shell' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 221715 error_code 3 request_code 18 (core protocol) minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Mar 21 16:55:18 taplop kernel: traps: gnome-shell[2552] trap int3 ip:7fde271ce955 sp:7ffcbe8660a0 error:0 in libglib-2.0.so.0.6000.0[7fde27195000+8] Mar 21 16:55:18 taplop update-notifier[4833]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop seahorse[3088]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop evolution-alarm[2863]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gnome-calendar[3082]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gsd-wacom[2744]: Error reading events from display: Broken pipe Mar 21 16:55:18 taplop gnome-session[2524]: gnome-session-binary[2524]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Mar 21 16:55:18 taplop gnome-session-binary[2524]: WARNING: App 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1 Mar 21 16:55:18 taplop org.gnome.Shell.desktop[2552]: (EE) failed to read Wayland events: Broken pipe Mar 21 16:55:18 taplop polkitd(authority=local)[1283]: Unregistered Authentication Agent for unix-session:2 (system bus name :1.266, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF- Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.Wacom.desktop[20239]: Unable to init server: Could not connect: Connection refused Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.Wacom.desktop[20239]: Cannot open display: Mar 21 16:55:18 taplop gnome-session-binary[2524]: Unrecoverable failure in required component org.gnome.Shell.desktop Mar 21 16:55:18 taplop gnome-session[2524]: gnome-session-binary[2524]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Mar 21 16:55:18 taplop gnome-session-binary[2524]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 5 Mar 21 16:55:18 taplop pulseaudio[2648]: ICE default IO error handler doing an exit(), pid = 2648, errno = 11 Mar 21 16:55:18 taplop org.gnome.SettingsDaemon.MediaKeys.desktop[2734]: xcb_connection_has_error() returned true Mar 21 16:55:18 taplop kernel: rfkill: input handler enabled Mar 21 16:55:18 taplop gsd-clipboard[2742]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-power[2723]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop keepass.desktop[2848]: cli: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-color[2750]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-keyboard[2721]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop at-spi-bus-launcher[2596]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Mar 21 16:55:18 taplop at-spi-bus-launcher[2596]: after 76743 requests (76743 known processed) with 0 events remaining. Mar 21 16:55:18 taplop gsd-xsettings[2754]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop gsd-media-keys[2734]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 21 16:55:18 taplop bluetoothd[1541]: Endpoint unregistered: sender=:1.420 path=/MediaEndpoint/A2DPSource Mar 21 16:55:18 taplop bluetoothd[1541]: Endpoint unregistered: sender=:1.420 path=/MediaEndpoint/A2DPSink Mar 21 16:55:18 taplop gdm-password][2472]: pam_unix(gdm-password:session): session closed for user jbarnett Mar 21 16:55:18 taplop systemd[2491]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Mar 21 16:55:18 taplop systemd[2491]: pulseaudio.service: Failed with result 'exit-code'. Mar 21 16:55:18 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Mar 21 16:55:18 taplop kernel: [drm] UVD and
[Bug 1820355] [NEW] Firefox icon missing
Public bug reported: I have firefox bookmarked in the gnome-shell dash. When starting the shell in disco, the firefox logo is missing and the launcher is a small but clickable blank area. If I use gnome-tweaks to change icon theme, the logo reappears for the rest of the session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 15 14:22:32 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (170 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- 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/1820355 Title: Firefox icon missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating
I'll try to test on an X session in a bit. One thing I have noticed is that while I still get the log messages, the unrotate behavior seems much better when setting the `dc=0` amdgpu module parameter (was also behaving better with the module blacklisted, but not sure about log messages), as per comments in https://gitlab.gnome.org/GNOME/mutter/issues/357 and https://gitlab.gnome.org/GNOME/mutter/issues/365 -- 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/1797174 Title: [Dell XPS 15 9575] gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
And with more testing, it seems like the activities button target is smaller and/or lower under Wayland than it is in Xorg. I can get it to work if i aim for the bottom of the black top bar, vs the middle of it (while aiming for the middle results in the flash, but not activation of the Activites text). -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
Doing a little more testing, it looks like everything works fine under Xorg, but am still seeing the activities button behavior under 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
maybe, although I'm using the vanilla gnome session, so the ubuntu-dock extension shouldn't be involved. -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] Re: gnome-shell activities / application icon touches not fully registering
Disabling extensions in the same session still shows the same behavior.
Logging out and back in again with them still disabled shows the same
behavior on the "Activities" button, but app launchers respond to touch
events appropriately. Re-enabling them in the same session keeps the
same state ("Activities" button bad, app launchers good)
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
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/1797178
Title:
gnome-shell activities / application icon touches not fully
registering
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797178] [NEW] gnome-shell activities / application icon touches not fully registering
Public bug reported: On a dell xps 15 2-in-1 (model 9575), the touchscreen mostly works. However, in gnome-shell, touching the top-left 'Activities' menu results in a quick flash of the menu button, but not the launching of the overview. Once in the overview (via mouse/keyboard/swipe-from-left), touching on an application icon (in either the left tray or the applications grid) results in the application icon flashing, but not activating. A long-touch will bring up a menu in which touching on "new window" works properly. Additionally, touching the "show applications" grid button works, as do other components of the top bar, its only the the "activities" menu button and app icon launchers that are "registering" a touch but not activating properly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:13:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1797178 Title: gnome-shell activities / application icon touches not fully registering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] Re: gnome-shell unrotates immediately after rotating
** Summary changed: - gnome-shell unrotates immeditely after rotating + gnome-shell unrotates immediately after rotating -- 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/1797174 Title: gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797174] [NEW] gnome-shell unrotates immediately after rotating
Public bug reported: on a dell xps 15 2-in-1 (model 9575), I've enabled iio-sensor-proxy functionality by doing: modprobe intel-ish-ipc echo "8086 a135" > /sys/bus/pci/drivers/intel_ish_ipc/new_id This makes `monitor-sensor` display rotation events, and gnome-shell auto-rotate the screen upon receiving them. However, immediately after rotating, the screen rotates back to its normal orientation (unless I quickly lock rotation), displaying the following in journalctl: Oct 10 09:06:19 taplop gnome-shell[2616]: Failed to apply DRM plane transform 1: Invalid argument Oct 10 09:06:20 taplop kernel: [drm] PCIE GART of 256M enabled (table at 0x00F4). Oct 10 09:06:20 taplop kernel: [drm] UVD and UVD ENC initialized successfully. Oct 10 09:06:20 taplop kernel: [drm] VCE initialized successfully. Oct 10 09:06:27 taplop kernel: amdgpu :01:00.0: GPU pci config reset ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 10 09:06:40 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-26 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to cosmic on 2018-09-28 (11 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1797174 Title: gnome-shell unrotates immediately after rotating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795991] Re: Difficulty setting up multimonitor with fractional scaling
** Description changed: I've enabled fractional scaling and set my laptop's 3840x2160 screen to 175% scaling. Upon plugging in an external 1920x1080 monitor, my laptop's screen resets to 200% scaling, and the external screen is set to 100%, to the right of my laptop's screen. If I try to set the laptop screen back to 175%, the Displays panel does not allow me to Apply, and journalctl outputs: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent Putting the external screen on the left or top of the laptop screen allows Apply to work (bottom or right does not work), but immediately reverts to the auto-set settings (200% laptop with 100% external on the right) and then clicking "revert" on the "revert or keep" dialog sets things to the requested scale factor and position (175% laptop with 100% external on the top/left). + I've also seen the settings randomly reset to 200% laptop with 100% + external on the right upon doing things like clicking reply in evolution + to open up a new compose window. + That's a bit long winded, so here's a shorter rundown of bugs description: 1) Upon connecting an external screen, the laptop screen scaling changes 2) Can't set external screen to the bottom or right of laptop screen with fractional scaling 3) Upon Application, the requested settings are reverted, and then reverting the reversion applies them, while "keeping" the change reverts + 4) Certain random actions appear to reset to the undesired settings ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.0-4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 3 15:17:03 2018 InstallationDate: Installed on 2018-09-26 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-09-28 (5 days ago) -- 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/1795991 Title: Difficulty setting up multimonitor with fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1795991] [NEW] Difficulty setting up multimonitor with fractional scaling
Public bug reported: I've enabled fractional scaling and set my laptop's 3840x2160 screen to 175% scaling. Upon plugging in an external 1920x1080 monitor, my laptop's screen resets to 200% scaling, and the external screen is set to 100%, to the right of my laptop's screen. If I try to set the laptop screen back to 175%, the Displays panel does not allow me to Apply, and journalctl outputs: Config not applicable: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Logical monitors not adjecent Putting the external screen on the left or top of the laptop screen allows Apply to work (bottom or right does not work), but immediately reverts to the auto-set settings (200% laptop with 100% external on the right) and then clicking "revert" on the "revert or keep" dialog sets things to the requested scale factor and position (175% laptop with 100% external on the top/left). That's a bit long winded, so here's a shorter rundown of bugs description: 1) Upon connecting an external screen, the laptop screen scaling changes 2) Can't set external screen to the bottom or right of laptop screen with fractional scaling 3) Upon Application, the requested settings are reverted, and then reverting the reversion applies them, while "keeping" the change reverts ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.0-4 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 3 15:17:03 2018 InstallationDate: Installed on 2018-09-26 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-09-28 (5 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1795991 Title: Difficulty setting up multimonitor with fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795991/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721833] Re: Can't type numbers in the evolution search box
I can confirm the same as @sleepingkyoto, that 789 work fine. -- 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/1721833 Title: Can't type numbers in the evolution search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1721833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()
@azzar1, installing the packages from your ppa results in an immediate crash of the session on attempting to login for me. nothing showing up in /var/crash -- 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/1714542 Title: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1721833] [NEW] Can't type numbers in the evolution search box
Public bug reported: Trying to type numeric characters into the evolution search box is not working when using the numeric keys above the letters on the keyboard. Shift+numeric key for a special symbol works, and then numpad keys work, but the "regular" number keys don't appear to do anything. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 6 10:35:25 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (777 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1721833 Title: Can't type numbers in the evolution search box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1721833/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()
I'm happy to help. I've applied the patch from the gnome bug to a local package build. Haven't seen the crash since but only been a day or so (was crashing on the order of once a week prior) -- 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/1714542 Title: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1714542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714542] Re: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint()
This appears to happen much more with the experimental mutter fractional scaling support turned on and scaling set to 150% (and font scaling set to 100%), but also happens without that enabled. Without it enabled, I have scaling set to 100%, but font scaling set to 150%. -- 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/1714542 Title: gnome-shell crashed with SIGSEGV in st_theme_node_reduce_border_radius() from st_theme_node_paint_borders() from st_theme_node_paint() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714540] [NEW] gnome-shell crash in overview
*** This bug is a duplicate of bug 1714542 *** https://bugs.launchpad.net/bugs/1714542 Public bug reported: As of an upgrade to 3.25.91 (last session that did not exhibit this behavior was a 3.24.x session), I've experienced several crashes of the shell in the overview. journalctl shows the following output at the time of the crash: Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8792]: Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54). Sep 01 08:14:41 spiny gnome-shell[8506]: meta_renderer_native_release_onscreen: assertion 'onscreen_native->gbm.next_fb_id == 0' failed Sep 01 08:14:41 spiny gnome-shell[8506]: _cogl_onscreen_free: assertion 'onscreen->winsys == ((void *)0)' failed Sep 01 08:14:41 spiny kernel: gnome-shell[8506]: segfault at 1a0 ip 7fc6008dd296 sp 7fff2df360f0 error 4 in libmutter-1.so.0.0.0[7fc6007f9000+13e000] Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: Fatal server error: Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) failed to read Wayland events: Connection reset by peer Sep 01 08:14:41 spiny org.gnome.Shell.desktop[8506]: (EE) Sep 01 08:14:41 spiny gnome-session[8488]: gnome-session-binary[8488]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 01 08:14:41 spiny gnome-session-binary[8488]: Unrecoverable failure in required component org.gnome.Shell.desktop Sep 01 08:14:41 spiny gnome-session-binary[8488]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 Sep 01 08:14:41 spiny polkitd(authority=local)[1424]: Unregistered Authentication Agent for unix-session:c3 (system bus name :1.868, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disco Sep 01 08:14:41 spiny gsd-media-keys[8610]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. Sep 01 08:14:41 spiny gsd-keyboard[8607]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. Sep 01 08:14:41 spiny gsd-clipboard[8596]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. Sep 01 08:14:41 spiny gsd-power[8613]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. Sep 01 08:14:41 spiny gsd-color[8599]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1024. Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1024" Sep 01 08:14:41 spiny org.a11y.atspi.Registry[8529]: after 21 requests (21 known processed) with 0 events remaining. Sep 01 08:14:41 spiny gdm-launch-environment][8400]: pam_unix(gdm-launch-environment:session): session closed for user gdm Sep 01 08:14:41 spiny systemd-logind[1376]: Removed session c3. Sep 01 08:14:41 spiny systemd[1]: Stopping User Manager for UID 121... Sep 01 08:14:41 spiny systemd[8432]: Stopping Accessibility services bus... Sep 01 08:14:41 spiny systemd[8432]: Stopping Sound Service... Sep 01 08:14:41 spiny systemd[8432]: Stopped target Default. Sep 01 08:14:41 spiny systemd[8432]: Stopping D-Bus User Message Bus... Sep 01 08:14:41 spiny systemd[8432]: Stopping sandboxed app permission store... Sep 01 08:14:41 spiny systemd[8432]: Stopped sandboxed app permission store. Sep 01 08:14:41 spiny systemd[8432]: Stopped D-Bus User Message Bus. Sep 01 08:14:41 spiny systemd[8432]: Stopped Accessibility services bus. Sep 01 08:14:41 spiny systemd[8432]: Stopped Sound Service. Sep 01 08:14:41 spiny systemd[8432]: Stopped target Basic System. Sep 01 08:14:41 spiny systemd[8432]: Stopped target Paths. Sep 01 08:14:41 spiny systemd[8432]: Stopped target Timers. Sep 01 08:14:41 spiny systemd[8432]: Stopped target Sockets. Sep 01 08:14:41 spiny systemd[8432]: Closed D-Bus User Message Bus Socket. Sep 01 08:14:41 spiny systemd[8432]: Closed Sound System. Sep 01 08:14:41 spiny systemd[8432]: Reached target Shutdown. Sep 01 08:14:41 spiny systemd[8432]: Starting Exit the Session... Sep 01 08:14:41 spiny systemd[8432]: Received SIGRTMIN+24 from PID 8854 (kill). Sep 01 08:14:41 spiny systemd[1]: Stopped User Manager for UID 121. Sep 01 08:14:41 spiny systemd[1]: Removed slice User Slice of gdm. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 1 08:15:50 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (742 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-sh
[Bug 1709064] Re: evince doesn't start in artful beta
*** This bug is a duplicate of bug 1710487 *** https://bugs.launchpad.net/bugs/1710487 ** This bug has been marked a duplicate of bug 1710487 evince silently crashes with apparmor error on artful -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709064] Re: evince doesn't start in artful beta
I haven't seen it work without manually applying andy's change to /etc/apparmor.d/usr.bin.evince -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1709064] Re: evince doesn't start in artful beta
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827335 makes this look like its apparmor related ** Bug watch added: Debian Bug tracker #827335 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827335 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1631980] [NEW] Steam not able to see network in yakkety
Public bug reported: Steam is unable to see the network in yakkety. Downloads stall and don't do anything; and trying to update steam results in a "Fatal Error: Steam needs to be online to update. Please confirm your network connection and try again" dialog box. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: steam:i386 1:1.0.0.52-5ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 10 07:43:55 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (416 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) PackageArchitecture: i386 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: steam UpgradeStatus: Upgraded to yakkety on 2016-09-29 (10 days ago) ** Affects: steam (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 yakkety ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1631980 Title: Steam not able to see network in yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1631980/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1573061] [NEW] gnome-software wants to upgrade held packages
Public bug reported: I have a held package, and gnome-software keeps popping up the "upgrades are available" notification. Looking at it what it wants to upgrade, there is only the held package. I haven't clicked 'install' to see if it will actually do so, but held packages should not be upgraded by gnome-software. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160419.2.b8d2e40.ubuntu-xenial-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 21 07:10:17 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (243 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: Upgraded to xenial on 2016-02-16 (64 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages xenial -- 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/1573061 Title: gnome-software wants to upgrade held packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1573061/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492318] Re: evolution crashed with signal 5 in g_object_new_valist()
hmm after reupgrading, it appears to work again -- i'll get a gdb backtrace if it happens again though. -- 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/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492318] Re: evolution crashed with signal 5 in g_object_new_valist()
note this happens every time i try to send an email, downgrading back to evolution 3.16.3 works, but the current 3.16.5 package is pretty much unusable -- 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/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492318] [NEW] evolution crashed with signal 5 in g_object_new_valist()
Public bug reported: on sending an email, evolution crashed with signal 5 in g_object_new_valist() for some reason, the crash report is not being uploaded to launchpad via apport or ubuntu-bug /var/crash/_usr_bin_evolution.1000.crash, but i'll attach the .crash file here ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- 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/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492318] Re: evolution crashed with signal 5 in g_object_new_valist()
** Attachment added: "_usr_bin_evolution.1000.crash" https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+attachment/4457358/+files/_usr_bin_evolution.1000.crash -- 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/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1473154] Re: keyboard lag since this morning's gnome3-staging upgrade
upgraded gnomedesktop packages and haven't seen the lag again. still have gnome-control-center packages held, so adding that as package ** Project changed: ubuntu-gnome => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Milestone: wily => None -- 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/1473154 Title: keyboard lag since this morning's gnome3-staging upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1473154/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
** Changed in: ubuntu-gnome Status: Confirmed => Fix Released ** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged => Fix Released -- 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/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463901] Re: closing lid no longer suspends
*** This bug is a duplicate of bug 1427877 *** https://bugs.launchpad.net/bugs/1427877 ** This bug has been marked a duplicate of bug 1427877 Media, brightness and volume keys don't work with GNOME 3.15.90 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1463901 Title: closing lid no longer suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1463901/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463901] Re: closing lid no longer suspends
the workaround in #1427877 (disabling the wacom gnome-settings-daemon plugin) appears to also fix this ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1463901 Title: closing lid no longer suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1463901/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
my initial tests show that disbling the wacom plugin fixes the issue with hotkeys, volume keys, and even brightness keys (previously even the restart didn't fix brightness keys for me even though it fixed hotkeys and volume keys). -- 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/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1463901] [NEW] closing lid no longer suspends
Public bug reported: after installing gnome3-staging PPA on vivid (ie, gnome 3.16), closing my laptop's lid no longer results in the system suspending. journalctl shows that the lid close event is detected: Jun 08 16:57:23 leafy systemd-logind[947]: Lid closed. but nothing actually happens. only way to suspend seems to be to ALT+Click the power button in the right side gnome shell top panel menu, which seems not terribly discoverable for normal users. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-power-manager 3.14.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jun 10 09:20:59 2015 InstallationDate: Installed on 2014-02-24 (470 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to vivid on 2015-02-04 (125 days ago) ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3-ppa third-party-packages vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1463901 Title: closing lid no longer suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1463901/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1427877] Re: Media, brightness and volume keys don't work with GNOME 3.15.90
I tried rebuilding gnome-settings-daemon from the ppa sources, but deleted all the debian/patches files. then restarted gnome-settings- daemon and gnome-shell, but still had the same problem with keyboard shortcuts not working (and actually it didn't fix itself with a gsd /gnome-shell restart until i reinstalled the ppa package directly). I may not be doing things correctly though. -- 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/1427877 Title: Media, brightness and volume keys don't work with GNOME 3.15.90 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1427877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1428712] Re: Screen turns green and locks out during apt full-upgrade
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1428712 Title: Screen turns green and locks out during apt full-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1428712/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1430903] [NEW] Can't get plantronics headset buttons to work
Public bug reported: Instructions for ubuntu 13.10 in http://www.helplinux.ru/wiki/en:kb :ubuntu-plantronics worked great in utopic, but has stopped working since upgrading to vivid. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-4ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 59-plantronics.rules Date: Wed Mar 11 09:33:40 2015 InstallationDate: Installed on 2014-02-24 (379 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) MachineType: Apple Inc. MacBookPro11,3 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed root=UUID=135fd833-3282-4f3b-8802-0a27ec2765b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-04 (34 days ago) dmi.bios.date: 10/18/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP112.88Z.0138.B02.1310181745 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-2BD1B31983FE1663 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,3 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-2BD1B31983FE1663 dmi.modalias: dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B02.1310181745:bd10/18/2013:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663: dmi.product.name: MacBookPro11,3 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1430903 Title: Can't get plantronics headset buttons to work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
** Also affects: gnome-control-center-signon (Ubuntu) Importance: Undecided Status: New -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
I'm thinking this is related to ubuntu-online-accounts, which I can't get to authenticate to my google apps account. If i try to add through control center -> ubuntu online accounts, i get "An error occured while loading the authentication page" but can't figure out more details. what package provieds the ubuntu online accounts control panel? should i link it to this bug? -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044120] Re: empathy-chat crashes when opening a window for a specific contact
yes it still happens every time. I cannot report via apport as reported above, the window never opens, even if i apport the crash file explicitly. the .crash file is attached above. ** Changed in: empathy (Ubuntu) Status: Invalid => New -- 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/1044120 Title: empathy-chat crashes when opening a window for a specific contact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044120] Re: empathy-chat crashes when opening a window for a specific contact
probably not, is probably data dependent. ** Changed in: empathy (Ubuntu) Status: Incomplete => New -- 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/1044120 Title: empathy-chat crashes when opening a window for a specific contact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
** Changed in: empathy (Ubuntu) Status: Incomplete => Opinion ** Changed in: empathy (Ubuntu) Status: Opinion => New -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
hmm, send to pastebin look incomplete, here is full log: http://pastebin.com/a9DdS4Pn -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] Re: can't connect to google apps gchat account "account requires authorisation"
yes i can reproduce it. logs at http://pastebin.com/J7WdFUhk -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1064113] [NEW] can't connect to google apps gchat account "account requires authorisation"
Public bug reported: I have a google apps gtalk jabber account configured in empathy that refuses to connect after upgrading to quantal. Error message "account requires authorisation" appears in the contact list. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: empathy 3.6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 8 16:02:38 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to quantal on 2012-10-05 (3 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- 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/1064113 Title: can't connect to google apps gchat account "account requires authorisation" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1064113/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044120] Re: empathy-chat crashes when opening a window for a specific contact
yes i can reproduce this 100% of the time by trying to open a window for a specific client, with latest up to date system ** Changed in: empathy (Ubuntu) Status: Incomplete => New -- 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/1044120 Title: empathy-chat crashes when opening a window for a specific contact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044120] Re: empathy-chat crashes when opening a window for a specific contact
crash file ** Attachment added: "_usr_lib_empathy_empathy-chat.1000.crash" https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+attachment/3284770/+files/_usr_lib_empathy_empathy-chat.1000.crash -- 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/1044120 Title: empathy-chat crashes when opening a window for a specific contact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1044120] [NEW] empathy-chat crashes when opening a window for a specific contact
Public bug reported: every time i open a chat window for a specific contact, empathy crashes. for some reason, apport doesn't send the crash report, but silently exits, so attaching the /var/crash file to this manually filed bug ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- 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/1044120 Title: empathy-chat crashes when opening a window for a specific contact To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1044120/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 959506] [NEW] ssh keys no longer getting added to ssh agent upon login
Public bug reported: Not sure if this is in gnome-session/lightdm/ssh-agent/pam/something else, but my ssh keys in .ssh are no longer unlocked/added to the ssh- agent launched by gnome-session upon login in precise, launching a gnome-shell session from lightdm. running ssh-add and entering in my login password works, but this used to be done automatically upon login in every previous release. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session 3.2.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 10:13:19 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to precise on 2012-03-06 (13 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/959506 Title: ssh keys no longer getting added to ssh agent upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/959506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 959506] Re: ssh keys no longer getting added to ssh agent upon login
-- 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/959506 Title: ssh keys no longer getting added to ssh agent upon login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/959506/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831624] Re: AIM account "Connection can't be established" error
still seeing this with latest 12.04 package (empathy 3.3.5) when it happens, can usually get it to connect by killing telepathy-haze and reconnecting a bunch of times, but sometimes takes longer than others. ** 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/831624 Title: AIM account "Connection can't be established" error To manage notifications about this bug go to: https://bugs.launchpad.net/adium/+bug/831624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 949210] Re: mouse scroll wheel not working in gnome-terminal
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/949210 Title: mouse scroll wheel not working in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/949210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 949210] [NEW] mouse scroll wheel not working in gnome-terminal
Public bug reported: upgraded to precise yesterday, and today noticed that the mouse scroll wheel is not working in gnome-terminal windows, but work properly in other gtk3 applications. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-terminal 3.3.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Wed Mar 7 09:33:50 2012 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to precise on 2012-03-06 (1 days ago) ** Affects: gnome-terminal (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-terminal in Ubuntu. https://bugs.launchpad.net/bugs/949210 Title: mouse scroll wheel not working in gnome-terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/949210/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897930] Re: conversation window contact->block contact doesn't actually add to the blocked contacts list
Actually looks like even the edit->blocked contacts entry doesn't seem to work. basically, I get the spam ims from the same yahoo user every day. I have not been able to block that user. -- 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/897930 Title: conversation window contact->block contact doesn't actually add to the blocked contacts list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/897930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897930] [NEW] conversation window contact->block contact doesn't actually add to the blocked contacts list
Public bug reported: was receiving spam ims from the same im name every few days, and conversation window's contact->block contact was not helping. then noticed contact list has edit->blocked contacts, which did not include that im name. just added it, hopefully will actually block that user. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.22-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Nov 29 15:45:40 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (139 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- 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/897930 Title: conversation window contact->block contact doesn't actually add to the blocked contacts list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/897930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 897930] Re: conversation window contact->block contact doesn't actually add to the blocked contacts 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/897930 Title: conversation window contact->block contact doesn't actually add to the blocked contacts list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/897930/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 811291] Re: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration
fixed with latest 1.29.16-0ubuntu2 gjs + 3.1.3-0ubuntu4 ** Changed in: gjs (Ubuntu) Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/811291 Title: Weird inconsistent behavior/lack of syncrhonization with empathy messaging integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/811291/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831341] Re: can't open empathy chat windows
seems to be fixed by 3.1.5.1 ** Changed in: empathy (Ubuntu) Status: Confirmed => Fix Released -- 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/831341 Title: can't open empathy chat windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831624] Re: AIM account "Connection can't be established" error
possibly related to bug #828756 ? -- 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/831624 Title: AIM account "Connection can't be established" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831624] Re: AIM account "Connection can't be established" error
-- 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/831624 Title: AIM account "Connection can't be established" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831624] [NEW] AIM account "Connection can't be established" error
Public bug reported: starting today, getting red box with "Connection can't be established" for my AIM account debug logs show SSL Cert error: Chain is VALID Checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US Also checking for a CA with DN=OU=Class 3 Public Primary Certification Authority,O="VeriSign, Inc.",C=US haze_notify_message: error: SSL Certificate Error haze_notify_message: Unable to validate certificate haze_notify_message: The certificate for api.screenname.aol.com could not be validated. The certificate chain presented is invalid. Failed to verify certificate for api.screenname.aol.com Connection error on 0x1532d40 (reason: 0 description: Error requesting https://api.screenname.aol.com/auth/clientLogin: Unable to connect to api.screenname.aol.com: SSL peer presented an invalid certificate) connecting using pidgin works fine. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 13:42:56 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (40 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- 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/831624 Title: AIM account "Connection can't be established" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831624/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831341] Re: can't open empathy chat windows
just noticed a crash dialog i closed before clicking 'submit bug' here's contents of .crash file ** Attachment added: "_usr_lib_empathy_empathy-chat.1000.crash" https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+attachment/2299847/+files/_usr_lib_empathy_empathy-chat.1000.crash -- 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/831341 Title: can't open empathy chat windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831341] Re: can't open empathy chat windows
-- 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/831341 Title: can't open empathy chat windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 831341] [NEW] can't open empathy chat windows
Public bug reported: as of relatively recently in oneiric, empathy chat dialogs no longer open. double clicking a contact in the contact list opens a gnome-shell message tray bubble, but clicking on that bubble doesn't open an empathy chat dialog. there appears to be no way to enter a group chat, and clicking on room -> group chat name does nothing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.12-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Mon Aug 22 08:13:26 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Release Candidate amd64 (20100419.1) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-07-13 (39 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- 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/831341 Title: can't open empathy chat windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/831341/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
