[Desktop-packages] [Bug 2061165] [NEW] Could not play camera stream
Public bug reported:
Running snapshot, I get a UI error message "could not play camera
stream", a black window, and the following log messages:
2024-04-12T16:32:17.738325Z INFO snapshot::application::imp: Snapshot
(org.gnome.Snapshot)
2024-04-12T16:32:17.738340Z INFO snapshot::application::imp: Version: 46.0
2024-04-12T16:32:17.738346Z INFO snapshot::application::imp: Datadir:
/usr/share/snapshot
(snapshot:923479): Adwaita-WARNING **: 09:32:17.773: Using
GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported.
Please use AdwStyleManager:color-scheme instead.
2024-04-12T16:32:18.266073Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-04-12T16:32:18.270673Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-04-12T16:32:18.272590Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
stream error: error output enum formats: Invalid argument
Some("../src/gst/gstpipewiresrc.c(689): on_state_changed ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
2024-04-12T16:32:18.272628Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
Internal data stream error.
Some("../libs/gst/base/gstbasesrc.c(3175): gst_base_src_loop ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir:\nstreaming
stopped, reason not-negotiated (-4)")
Running the flatpak org.gnome.Snapshot version of the app, everything
works ok, fwiw
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gnome-snapshot 46.0-1ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Fri Apr 12 09:31:36 2024
InstallationDate: Installed on 2019-08-17 (1701 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-snapshot
UpgradeStatus: Upgraded to noble on 2024-03-23 (20 days ago)
** Affects: gnome-snapshot (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-snapshot in Ubuntu.
https://bugs.launchpad.net/bugs/2061165
Title:
Could not play camera stream
Status in gnome-snapshot package in Ubuntu:
New
Bug description:
Running snapshot, I get a UI error message "could not play camera
stream", a black window, and the following log messages:
2024-04-12T16:32:17.738325Z INFO snapshot::application::imp: Snapshot
(org.gnome.Snapshot)
2024-04-12T16:32:17.738340Z INFO snapshot::application::imp: Version: 46.0
2024-04-12T16:32:17.738346Z INFO snapshot::application::imp: Datadir:
/usr/share/snapshot
(snapshot:923479): Adwaita-WARNING **: 09:32:17.773: Using
GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported.
Please use AdwStyleManager:color-scheme instead.
2024-04-12T16:32:18.266073Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-04-12T16:32:18.270673Z ERROR aperture::viewfinder: Could not start
camerabin: Element failed to change its state
2024-04-12T16:32:18.272590Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
stream error: error output enum formats: Invalid argument
Some("../src/gst/gstpipewiresrc.c(689): on_state_changed ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
2024-04-12T16:32:18.272628Z ERROR aperture::viewfinder: Bus Error from
Some("/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir")
Internal data stream error.
Some("../libs/gst/base/gstbasesrc.c(3175): gst_base_src_loop ():
/GstCameraBin:camerabin0/GstWrapperCameraBinSrc:camerasrc/GstAutoVideoSrc:camerasrc-real-src/GstPipeWireSrc:camerasrc-real-src-actual-src-pipewir:\nstreaming
stopped, reason not-negotiated (-4)")
Running the flatpak org.gnome.Snapshot version of the app, everything
works ok, fwiw
ProblemType: Bug
DistroRelease: Ubuntu 24.04
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2037460 Title: gnome-shell crash Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2015577 Title: middle click to lower window no longer works for xwayland windows Status in Mutter: Unknown Status in mutter package in Ubuntu: New Status in xwayland package in Ubuntu: New Bug description: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015577] [NEW] middle click to lower window no longer works for xwayland windows
Public bug reported: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2015577 Title: middle click to lower window no longer works for xwayland windows Status in xwayland package in Ubuntu: New Bug description: i have titlebar middle-click set to lower windows in Tweaks. In kinetic, this works for xwayland windows, while in lunar it no longer does. (native wayland gtk3 and gtk4 apps do appear to work though, which was a long time coming!) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xwayland 2:22.1.8-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Apr 7 08:54:02 2023 InstallationDate: Installed on 2019-08-17 (1329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xwayland UpgradeStatus: Upgraded to lunar on 2023-04-05 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2015577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2015493] [NEW] file chooser / screen share portal not observing dark theme
Public bug reported: I have dark theme variant set, but the file chooser / screen share portal displayed by firefox (snap) use the light theme. In kinetic it was using the dark theme but started to display light theme in lunar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Apr 6 08:43:40 2023 InstallationDate: Installed on 2019-08-17 (1328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-05 (0 days ago) ** Affects: xdg-desktop-portal-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gnome in Ubuntu. https://bugs.launchpad.net/bugs/2015493 Title: file chooser / screen share portal not observing dark theme Status in xdg-desktop-portal-gnome package in Ubuntu: New Bug description: I have dark theme variant set, but the file chooser / screen share portal displayed by firefox (snap) use the light theme. In kinetic it was using the dark theme but started to display light theme in lunar. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xdg-desktop-portal-gnome 44~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu Apr 6 08:43:40 2023 InstallationDate: Installed on 2019-08-17 (1328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: xdg-desktop-portal-gnome UpgradeStatus: Upgraded to lunar on 2023-04-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gnome/+bug/2015493/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top
i think this is maybe fixed in lunar? seems better at least with initial testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997480] Re: maximized xwayland windows shift by 1 pixel when on top vs/ not on top
I've also noticed that the crash in https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 gets triggered by the 1pixel shift, even when sharing the full desktop screen. ** Bug watch added: Mozilla Bugzilla #1790496 https://bugzilla.mozilla.org/show_bug.cgi?id=1790496 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1997480] [NEW] maximized xwayland windows shift by 1 pixel when on top vs/ not on top
Public bug reported: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1997480 Title: maximized xwayland windows shift by 1 pixel when on top vs/ not on top Status in xwayland package in Ubuntu: New Bug description: on kinetic with a gnome wayland session, maximized X apps on the secondary screen run through xwayland appear to move position by ~ 1 pixel when they are on top vs/ not on top. running w/ 2 monitors, primary @ 175% scaling, secondary @ 100% scaling minimal example: maximize xterm and have it be the top window on secondary screen. open another window on the primary screen. drag it over to the secondary screen to overlap the xterm and see the window border jump by ~1 pixel actual example that is more noticable: maximize an intellij/pycharm/other jetbrains product and have it be the top window on the secondary screen. hover over something that creates a popup (eg a folder in the left project tree pane with a name long enough to get cut off) and see the whole IDE dance around. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xwayland 2:22.1.3-2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Nov 22 10:50:47 2022 InstallationDate: Installed on 2019-08-17 (1193 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xwayland UpgradeStatus: Upgraded to kinetic on 2022-09-22 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1997480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) if configured via middle-click Status in GTK+: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1986861] [NEW] pulseaudio stops accepting connections
Public bug reported: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1986861 Title: pulseaudio stops accepting connections Status in pulseaudio package in Ubuntu: New Bug description: After a while, pulseaudio clients get connections refused and are unable to play audio / receive microphone input. journalctl shows lots of messages like: Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Expected 1 memfd fd to be received over pipe; got 0 Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] native-common.c: Did we reach our open file descriptors limit? Aug 17 13:00:17 taplop pulseaudio[2244465]: [pulseaudio] protocol-native.c: protocol error, kicking client as well as Aug 17 13:03:52 taplop pulseaudio[2244465]: [pulseaudio] protocol- native.c: Warning! Too many connections (64), dropping incoming connection. killing the pulseaudio daemon makes audio work for a little while until the same thing repeats. not sure what's triggering it though, or how to best find out. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 Uname: Linux 5.17.0-051700drmtip20220329-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2265029 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Wed Aug 17 14:13:56 2022 InstallationDate: Installed on 2019-08-17 (1096 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (152 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1986861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1971744 Title: external monitor static image after unlocking session Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1971744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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) Status in Mozilla Firefox: New Status in Mutter: Unknown Status in firefox package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) A similar behavior can also be observed in gedit, nautilus and other GNOME applications whether they are confined or not (while snapped ones seems to underline the issue more) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
seeing the same behavior with the -non-free version too, does it need a separate rebuild? ** Also affects: intel-media-driver-non-free (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Status in intel-media-driver package in Ubuntu: Fix Committed Status in intel-media-driver-non-free package in Ubuntu: New Status in mesa package in Ubuntu: Invalid Bug description: I noticed that it upgraded mesa to 22.x and now video acceleration is not working due to: ❯ vainfo libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit ~/Desktop ❯ inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Device-2: Generalplus GENERAL WEBCAM type: USB driver: snd-usb-audio,uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 3840x2160~60Hz OpenGL: renderer: Mesa Intel UHD Graphics P630 (CML GT2) v: 4.6 Mesa 22.0.0 I tried rebuilding the i965-va-driver, and it's still the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mesa-vdpau-drivers 22.0.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 27 10:37:41 2022 DistUpgraded: 2022-01-18 23:59:55,390 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtl88x2bu/5.8.7.1, 5.15.0-18-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-22-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.15.0-23-generic, x86_64: installed rtl88x2bu/5.8.7.1, 5.17.0-xanmod1, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9bc6] (rev 05) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8694] InstallationDate: Installed on 2021-10-05 (172 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=018d5b69-accd-451b-a6f7-2027f791ea0e ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to jammy on 2022-01-18 (67 days ago) dmi.bios.date: 07/08/2021 dmi.bios.release: 23.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2301 dmi.board.asset.tag: Default string dmi.board.name: Pro WS W480-ACE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/08/2021:br23.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSW480-ACE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.0-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966593 Title: gnome session locks when disconnecting external screen Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965968] [NEW] post jammy update, black/flickering screen on boot
Public bug reported: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1965968 Title: post jammy update, black/flickering screen on boot Status in plymouth package in Ubuntu: New Bug description: After initial jammy upgrade things were working fine, but after a recent update the machine boots to a blank screen. There are occasional purplish flickers that seem to correspond with keypresses, but even blindly typing the encrypted disk password doesn't appear to advance the boot process to gdm. Plugging in an external monitor does fix the issue and allow boot to proceed, but obviously doesn't help if not near an external monitor. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: plymouth 0.9.5+git20211018-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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Mar 22 09:22:26 2022 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2019-08-17 (948 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) MachineType: Dell Inc. XPS 15 9575 ProcCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=UUID=83cade14-7628-437d-8517-36ad82f00d20 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-gnome-text/ubuntu-gnome-text.plymouth UpgradeStatus: Upgraded to jammy on 2022-03-18 (3 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1965968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates, but doesn't reset
Status in mutter package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1963264 Title: Screencast not recording Status in gnome-shell package in Ubuntu: Invalid Bug description: When I press Ctrl+Shift+Alt+R, screencast indicator appears in the indicator menu but disappears in about 2 seconds. No file is even created under the Videos folder. journalctl shows: Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:29 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Activating service name='org.gnome.Shell.Screencast' requested by ':1.62' (uid=1000 pid=3311 comm="/usr/libexec/gsd-media-> Mar 02 09:10:31 Development dbus-daemon[2962]: [session uid=1000 pid=2962] Successfully activated service 'org.gnome.Shell.Screencast' Mar 02 09:10:32 Development gjs[5825]: JS LOG: Failed to create pipeline: Gst.ParseError: no element "pipewiresrc" The issue is the Gst.ParseError. Before upgrading to jammy (22.04), it used to work fine. Also, when testing under qemu/KVM it works properly. It just doesn't work when running directly on the PC. What other logs can I provide? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 3 15:41:44 2022 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-12 (660 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 41.3-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates, but doesn't reset
Status in mutter package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964541] Re: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions
I do occasionally get crashes when attempting to rearrange tabs as well. The crashes happen both in .deb & snap versions of firefox though? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1964541 Title: Cannot rearrange Firefox (snap) browser tabs in Wayland sessions Status in firefox package in Ubuntu: Confirmed Bug description: Since 42~beta-1ubuntu1, and still present in 42~beta-1ubuntu2, attempting to re-arrange tabs in Firefox fails. Click and drag the tab and release, nothing changes. The next click to the tab is ignored. syslog has the following: Mar 11 13:06:47 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:48 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:50 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. Mar 11 13:06:51 desktop firefox[2192]: Attempting to add a widget with type GtkWindow to a container of type GtkWindow, but the widget is already inside a container of type GtkWindow, please remove the widget from its existing container first. gnome-shell 42~beta-1ubuntu2 Firefox Snap 98.0-3 (1073) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1964541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965647] Re: pulseaudio gets stuck after launching firefox
seems like pulse was fighting with pipewire; not sure what I did to clean it up but appears to be working better now -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1965647 Title: pulseaudio gets stuck after launching firefox Status in pulseaudio package in Ubuntu: New Bug description: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1965647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates, but doesn't reset
Status in mutter package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1965648/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965647] [NEW] pulseaudio gets stuck after launching firefox
Public bug reported: after updating to jammy, pulseaudio appears to get stuck after opening firefox. I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" killing pulseaudio (and having systemd user session restart it) restores sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out "Audio device got stuck!" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 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 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: jbarnett 3283 F wireplumber - /dev/snd/controlC0: jbarnett 3283 F wireplumber - jbarnett 7684 F pulseaudio - /dev/snd/seq:jbarnett 3278 F pipewire + USERPID ACCESS COMMAND + /dev/snd/controlC1: jbarnett 3283 F wireplumber + /dev/snd/controlC0: jbarnett 3283 F wireplumber + jbarnett 7684 F pulseaudio + /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Description changed: after updating to jammy, pulseaudio appears to get stuck after opening firefox. - I can play an audio file using mplayer fine, then I open firefox (either snap or deb version), then it fails to play the same audio file and prints out + I can play an audio file using mplayer fine, then I open firefox, then it fails to play the same audio file and prints out "Audio device got stuck!" + + killing pulseaudio (and having systemd user session restart it) restores + sound in mplayer ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jbarnett 3283 F wireplumber /dev/snd/controlC0: jbarnett 3283 F wireplumber jbarnett 7684 F pulseaudio /dev/snd/seq:jbarnett 3278 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Sat Mar 19 15:29:11 2022 InstallationDate:
[Desktop-packages] [Bug 1965638] [NEW] Can't drag to reorder tabs
Public bug reported: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.6.86 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:365 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=98.0.1/20220313140707 (Out of date) RunningIncompatibleAddons: False Snap.Changes: ID Status Spawn Ready Summary 495 Done2022-03-19T13:27:26-07:00 2022-03-19T13:30:56-07:00 Remove "firefox" snap 496 Done2022-03-19T13:33:19-07:00 2022-03-19T13:34:07-07:00 Install "firefox" snap SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-03-18 (0 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr:sku080D: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1965638 Title: Can't drag to reorder tabs Status in firefox package in Ubuntu: New Bug description: After upgrading from impish to jammy, seeing the following behavior in firefox when trying to reorder tabs by clicking and dragging them: 1) in the .deb firefox, firefox will crash most of the time, but sometimes reorder successfully 2) in the snap firefox, firefox will not register the drag (nothing will happen). Following attempting to drag the tab, the next click in firefox is discarded/ignored and things like mouse wheel scrolls don't work until firefox is clicked in ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 97.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 92319 F pulseaudio BuildID: 20220216172458 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 19 13:37:18 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (945 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000
[Desktop-packages] [Bug 1945518] [NEW] The WidevineCdm plugin has crashed
*** This bug is a duplicate of bug 1945100 *** https://bugs.launchpad.net/bugs/1945100 Public bug reported: Watching Widevine content (eg netflix, hbomax, etc) on the .deb package of firefox in impish has recently stopped working. Get a "The WidevineCdm plugin has crashed" message at the top of the browser window. Get the same thing when running in --safe-mode as well. Appears to work fine on the snap package though. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 92.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 52134 F pulseaudio BuildID: 20210922161155 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Wed Sep 29 10:56:50 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (774 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.240 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:358 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=92.0.1/20210922161155 RebootRequiredPkgs: Error: path contained symlinks. RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-09-16 (13 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:sku080D:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** This bug has been marked a duplicate of bug 1945100 Widevine violates the sandbox and crashes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1945518 Title: The WidevineCdm plugin has crashed Status in firefox package in Ubuntu: New Bug description: Watching Widevine content (eg netflix, hbomax, etc) on the .deb package of firefox in impish has recently stopped working. Get a "The WidevineCdm plugin has crashed" message at the top of the browser window. Get the same thing when running in --safe-mode as well. Appears to work fine on the snap package though. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: firefox 92.0.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 52134 F pulseaudio BuildID: 20210922161155 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Wed Sep 29 10:56:50 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (774 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.240 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @
[Desktop-packages] [Bug 1936955] [NEW] firefox 90 stopped remembering window size
Public bug reported: since upgrading to firefox 90, all newly opened firefox windows are very small and need to be manually resized to a usable size. prior to firefox 90, new windows would be the same size as the last opened window. running on gnome on wayland with fractional scaling enabled, if that matters. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2823 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Jul 20 09:23:39 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (703 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.25 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-07-08 (11 days ago) dmi.bios.date: 03/25/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd03/25/2021:br1.15:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1936955 Title: firefox 90 stopped remembering window size Status in firefox package in Ubuntu: New Bug description: since upgrading to firefox 90, all newly opened firefox windows are very small and need to be manually resized to a usable size. prior to firefox 90, new windows would be the same size as the last opened window. running on gnome on wayland with fractional scaling enabled, if that matters. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 90.0+build1-0ubuntu0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2823 F pulseaudio BuildID: 20210705185941 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Jul 20 09:23:39 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (703 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.25 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=90.0/20210705185941 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs:
[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
ok that makes sense, I think opening links from slack (electron/x11) was likely the culprit that "poisoned" the running firefox instance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: In Progress Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1921931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
Thanks Olivier. That bug report looks related but seems more like it never works, vs/ works for a little while and then stops working? But adding the MOZ_DBUS_REMOTE flag that it mentions seems to fix the issue when running with MOZ_ENABLE_WAYLAND in limited testing so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: New Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1921931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921931] Re: Opening links results in "Firefox is already running, but is not responding"
Yes, commenting out the MOZ_ENABLE_WAYLAND line appears to fix the issue. With MOZ_ENABLE_WAYLAND=1, initial link requests work, but after a short while start getting the firefox is running but not responding dialog. Without it, link requests work even after a while. ** Changed in: firefox (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in firefox package in Ubuntu: New Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1921931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921931] [NEW] Opening links results in "Firefox is already running, but is not responding"
Public bug reported: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=87.0/20210318103112 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-76c5697a-ecec-48ea-b09a-9db310190506 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to hirsute on 2021-02-23 (34 days ago) dmi.bios.date: 07/15/2020 dmi.bios.release: 1.13 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd07/15/2020:br1.13:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1921931 Title: Opening links results in "Firefox is already running, but is not responding" Status in firefox package in Ubuntu: New Bug description: Since the latest package release enabling wayland, I often get the "Firefox is already running, but is not responding. To use Firefox, you must first close the existing Firefox process, restart your device, or use a different profile." message when trying to open links from other applications (eg geary, slack) instead of having the link open in the existing firefox window. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 87.0+build3-0ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 829438 F pulseaudio BuildID: 20210318103112 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: GNOME Date: Tue Mar 30 09:14:13 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2019-08-17 (591 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) IpRoute: default via 192.168.4.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/22 dev wlp2s0 proto kernel scope link src 192.168.4.89 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-76c5697a-ecec-48ea-b09a-9db310190506 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 PrefSources:
[Desktop-packages] [Bug 1906283] Re: Scroll wheel stopped working on message contents in Geary
seems to have fixed itself somehow. ** Changed in: geary (Ubuntu) Status: New => Invalid ** Changed in: webkit2gtk (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1906283 Title: Scroll wheel stopped working on message contents in Geary Status in geary package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Invalid Bug description: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1906283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906283] [NEW] Scroll wheel stopped working on message contents in Geary
Public bug reported: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) ** Affects: geary (Ubuntu) Importance: Undecided Status: New ** Affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages wayland-session ** Also affects: webkit2gtk (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Scroll wheel stopped working on message contents + Scroll wheel stopped working on message contents in Geary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1906283 Title: Scroll wheel stopped working on message contents in Geary Status in geary package in Ubuntu: New Status in webkit2gtk package in Ubuntu: New Bug description: Recently in groovy, using the mouse scroll wheel while hovering over a message in geary stopped scrolling the message. hovering over the header or the scrollbar still works. possibly related to webkit2gtk update? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: geary 3.38.0.1-3 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 30 09:03:17 2020 InstallationDate: Installed on 2019-08-17 (471 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: geary UpgradeStatus: Upgraded to groovy on 2020-09-28 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geary/+bug/1906283/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1898080 Title: Dsiplay artifacts in groovy when moving windows around Status in mutter package in Ubuntu: New Bug description: 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%. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1898080/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884126] Re: Trying to add google account fails with AUTH-1140
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues #126
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
** Also affects: gnome-online-accounts via
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/issues/126
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1884126
Title:
Trying to add google account fails with AUTH-1140
Status in gnome-online-accounts:
Unknown
Status in gnome-online-accounts package in Ubuntu:
New
Bug description:
Trying to add a google account that redirects to another site for sign
in results in a window with the following error:
{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1884126/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884126] [NEW] Trying to add google account fails with AUTH-1140
Public bug reported:
Trying to add a google account that redirects to another site for sign
in results in a window with the following error:
{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)
** Affects: gnome-online-accounts (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1884126
Title:
Trying to add google account fails with AUTH-1140
Status in gnome-online-accounts package in Ubuntu:
New
Bug description:
Trying to add a google account that redirects to another site for sign
in results in a window with the following error:
{"status":"failed", "cause":[{"code":"AUTH-1140", "message": "There is
an invalid header value that can't be parsed."}]}
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Thu Jun 18 11:41:17 2020
InstallationDate: Installed on 2019-08-17 (306 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to focal on 2020-03-06 (104 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1884126/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Interesting that I didn't see this in eoan, but did once upgrading to focal. appears the "Highlight current line" option default changed to true maybe? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1867819 Title: Dark theme current line highlight hard to read Status in gedit package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1867819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell 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] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Fix Committed Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1848086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844575 Title: Pixelated fonts sometimes Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1845031 Title: gnome not remembering numlock state in eoan Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844575 Title: Pixelated fonts sometimes Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844575 Title: Pixelated fonts sometimes Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844575/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [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 Desktop Packages, 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) Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Committed Status in gnome-shell source package in Eoan: Fix Released Bug description: [ Impact ] From time to time, my chrome icon disappears in gnome shell 3.32, leaving only the "open window indicator" below it. It's the first of my icons, and this is running a vanilla gnome session. [ QA ] No further verification as this is a fix coming with a GNOME micro release update that is covered by this exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME --- ProblemType: BugDistroRelease: 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: Tue Apr 2 17:44:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-03-14 (383 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2018-11-20 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 th
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 Desktop Packages, 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" Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/e622155ae760525198ab9d778ae25686a5e55978 Had this happen a few times now, where closing the main evolution window (last visible window on desktop) results in a gnome-shell crash (see bug 1821262) ProblemType: Crash 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 22 18:49:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-09-26 (177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to disco on 2019-03-11 (11 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1822394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820355 Title: Firefox icon is blank in the launcher Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: laptop keyboard & touchpad not working at gdm screen after boot Status in gdm3 package in Ubuntu: New Bug description: 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:
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1821262 Title: gnome-shell crashes when closing evolution Status in gnome-shell package in Ubuntu: Incomplete Bug description: 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
[Desktop-packages] [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
[Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab
Sounds good, thanks! for anyone looking for this functionality, it is now natively supported without chrome css hacks if toolkit.tabbox.switchByScrolling is set to true. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820413 Title: Firefox 66 can't open new tab Status in firefox package in Ubuntu: Invalid Bug description: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab
ah, after a little more digging, it seems that following these instructions: https://forum.manjaro.org/t/howto-enable-tab-switching-in- firefox-using-mouse-wheel/39954 for mouse wheel based tab switching is the cause of the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820413 Title: Firefox 66 can't open new tab Status in firefox package in Ubuntu: Incomplete Bug description: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab
yup, have done so, but obviously not ideal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820413 Title: Firefox 66 can't open new tab Status in firefox package in Ubuntu: Incomplete Bug description: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1820413] Re: Firefox 66 can't open new tab
there is no + button in the tab bar (actually the tab bar doesn't even show the current tab). Ctrl + T does nothing, control + click on link does nothing. opening eg, preferences from the hamburger menu (which usually tries to open in a new tab) does nothing. safe mode does work, but disabling/removing all extensions does not. fresh profile works, and installing all the same extensions to the fresh profile still works. On Mon, Mar 18, 2019 at 7:35 AM Olivier Tilloy wrote: > Does this happen if you start firefox with the -safe-mode argument? > > firefox -safe-mode > > How do you try to open a new tab (+ button in the tabs bar, Ctrl+T > keyboard shortcut)? How does it fail? > > ** Changed in: firefox (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1820413 > > Title: > Firefox 66 can't open new tab > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820413 Title: Firefox 66 can't open new tab Status in firefox package in Ubuntu: Incomplete Bug description: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820413] [NEW] Firefox 66 can't open new tab
Public bug reported: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1820413 Title: Firefox 66 can't open new tab Status in firefox package in Ubuntu: New Bug description: With the disco upgrade to firefox 66, I can't open new tabs, and the browser doesn't cleanly exit on closing windows. Disabling all extensions does not fix, downgrading to firefox 65 does. Safe mode also appears to fix, but weird that disabling extensions doesn't? ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2363 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: GNOME Date: Sat Mar 16 10:09:11 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-26 (171 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 172.20.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.20.0.0/20 dev wlp2s0 proto kernel scope link src 172.20.1.179 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/adobe-flashplugin/libflashplayer.so (adobe-flashplugin) PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js prefs.js Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RelatedPackageVersions: adobe-flashplugin 1:20190312.1-0ubuntu1 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-03-11 (4 days ago) dmi.bios.date: 10/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0N338G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/10/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0N338G:rvrA00:cvnDellInc.:ct10:cvr:
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1820355 Title: Firefox icon missing Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-shell package in Ubuntu: Confirmed Status in iio-sensor-proxy package in Ubuntu: Confirmed Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1797178
Title:
gnome-shell activities / application icon touches not fully
registering
Status in gnome-shell package in Ubuntu:
New
Bug description:
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)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797174 Title: gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797178 Title: gnome-shell activities / application icon touches not fully registering Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1797174 Title: gnome-shell unrotates immediately after rotating Status in gnome-shell package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1797174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795991 Title: Difficulty setting up multimonitor with fractional scaling Status in mutter package in Ubuntu: New Bug description: 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 SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-09-28 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [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 Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795991 Title: Difficulty setting up multimonitor with fractional scaling Status in mutter package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757321] [NEW] Can't mount encrypted USB drive after upgrade to bionic
Public bug reported: after upgrading to bionic, attempts to mount an encrypted USB drive fail with the error "function bd_crypto_luks_open_blob called but not implemented" Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting appears to have fixed it, but should that be necessary? or at least better documented? (https://www.distrowatch.com/weekly.php?issue=20171113 is the only reference I could find on the error) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules Date: Tue Mar 20 20:28:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (942 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1757321 Title: Can't mount encrypted USB drive after upgrade to bionic Status in udisks2 package in Ubuntu: New Bug description: after upgrading to bionic, attempts to mount an encrypted USB drive fail with the error "function bd_crypto_luks_open_blob called but not implemented" Installing libblockdev-crypto2 and libblockdev-crypto-dev and rebooting appears to have fixed it, but should that be necessary? or at least better documented? (https://www.distrowatch.com/weekly.php?issue=20171113 is the only reference I could find on the error) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME CustomUdevRuleFiles: 90-xhc_sleep.rules 70-snap.core.rules Date: Tue Mar 20 20:28:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-08-21 (942 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: Upgraded to bionic on 2018-03-20 (0 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1757321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1721833 Title: Can't type numbers in the evolution search box Status in evolution package in Ubuntu: Confirmed Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1721833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8 --- 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: Crash
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1721833 Title: Can't type numbers in the evolution search box Status in evolution package in Ubuntu: New Bug description: 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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1721833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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() Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8 --- 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.
[Desktop-packages] [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 Desktop Packages, 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() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23d376488259ea5f9fa6fb9843956cb6464f56e8 --- 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
[Desktop-packages] [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:
[Desktop-packages] [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 Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: Confirmed Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: Confirmed Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1709064 Title: evince doesn't start in artful beta Status in evince package in Ubuntu: Confirmed Bug description: Can't open a pdf with evince as nothing happens after clicking twice on the file. Starting from terminal the following error is occurs: ''' (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper (evince:10291): Gdk-WARNING **: Failed to load cursor theme Paper ** Gdk:ERROR:/build/gtk+3.0-f0nGiQ/gtk+3.0-3.22.17/./gdk/wayland/gdkdisplay-wayland.c:1039:_gdk_wayland_display_get_scaled_cursor_theme: assertion failed: (display_wayland->cursor_theme_name) Aborted (core dumped) ''' carlo@thinkpad:~$ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 carlo@thinkpad:~$ apt-cache policy evince evince: Installed: 3.24.1-0ubuntu1 Candidate: 3.24.1-0ubuntu1 Version table: *** 3.24.1-0ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.24.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 7 13:24:59 2017 InstallationDate: Installed on 2017-08-06 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1709064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629620] Re: DNS resolver stops accepting queries
this seems to be less of a problem after switching /etc/resolv.conf to point to the systemd-resolved managed file instead of the resolvconf managed file. not sure exactly which package should be changed to have this work automatically? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: New Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1629620] [NEW] DNS resolver stops accepting queries
Public bug reported: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address:127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 63f0b05b-f699-4a68-81ce-f62d2c1a247d /org/freedesktop/NetworkManager/ActiveConnection/0 wlp3s0 wifi connected /org/freedesktop/NetworkManager/Devices/4 HOME-1622-5 6df3f2f0-fb86-43b5-802a-d59bc5734be3 /org/freedesktop/NetworkManager/ActiveConnection/2 24:DA:9B:B9:09:0E btdisconnected /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1629620 Title: DNS resolver stops accepting queries Status in network-manager package in Ubuntu: New Bug description: After a while / after resume from suspend, the system becomes unable to respond to DNS queries, with the following output for example: $ nslookup google.com 127.0.1.1 Server: 127.0.1.1 Address: 127.0.1.1#53 ** server can't find google.com: REFUSED This is on an up to date yakkety install. Changing resolv.conf to use 8.8.8.8, or restarting network-manager appears to fix this, at least until it recurs again. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Oct 1 21:28:51 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-08-21 (407 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.5 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to yakkety on 2016-09-29 (2 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID
[Desktop-packages] [Bug 1575896] Re: Scrollbar thumb not drawn in firefox 46 (gtk3?)
Simlarly, checkboxes and radio buttons are pretty much invisible until
activated, should that be a separate bug or handled in this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1575896
Title:
Scrollbar thumb not drawn in firefox 46 (gtk3?)
Status in firefox package in Ubuntu:
Confirmed
Bug description:
As of today's firefox 46 release, the scrollbar thumb is not being
drawn, just see a thin grey bar on the right side of the window.
Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 2545 F pulseaudio
/dev/snd/controlC1: jbarnett 2545 F pulseaudio
/dev/snd/controlC3: jbarnett 2545 F pulseaudio
/dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-08-21 (250 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 172.16.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.16.1.0/24 dev wlp3s0 proto kernel scope link src 172.16.1.43 metric
600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
[Profile]/extensions/cookie...@jayapal.com/defaults/preferences/cookiemgr.js
[Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
[Profile]/extensions/{ea4637dc-e014-4c17-9c2c-879322d23268}/defaults/preferences/defaults.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
browser-plugin-freshplayer-nacl0.3.4-3
browser-plugin-freshplayer-pepperflash 0.3.4-3
adobe-flashplugin 1:20160407.1-0ubuntu1
gnome-shell3.20.1-0ubuntu1~xenial3
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-02-16 (71 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575896] Re: Scrollbar thumb not drawn in firefox 46 (gtk3?)
actually, installing the gnome theme at least makes the scrollbar
appear, even if it looks kinda ugly. see attached screenshot
** Attachment added: "Screenshot from 2016-05-04 16-11-21.png"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575896/+attachment/4656014/+files/Screenshot%20from%202016-05-04%2016-11-21.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1575896
Title:
Scrollbar thumb not drawn in firefox 46 (gtk3?)
Status in firefox package in Ubuntu:
Confirmed
Bug description:
As of today's firefox 46 release, the scrollbar thumb is not being
drawn, just see a thin grey bar on the right side of the window.
Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 2545 F pulseaudio
/dev/snd/controlC1: jbarnett 2545 F pulseaudio
/dev/snd/controlC3: jbarnett 2545 F pulseaudio
/dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-08-21 (250 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 172.16.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.16.1.0/24 dev wlp3s0 proto kernel scope link src 172.16.1.43 metric
600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
[Profile]/extensions/cookie...@jayapal.com/defaults/preferences/cookiemgr.js
[Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
[Profile]/extensions/{ea4637dc-e014-4c17-9c2c-879322d23268}/defaults/preferences/defaults.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
browser-plugin-freshplayer-nacl0.3.4-3
browser-plugin-freshplayer-pepperflash 0.3.4-3
adobe-flashplugin 1:20160407.1-0ubuntu1
gnome-shell3.20.1-0ubuntu1~xenial3
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-02-16 (71 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575896] Re: Scrollbar thumb not drawn in firefox 46 (gtk3?)
actually, installing the gnome theme at least makes the scrollbar
appear, even if it looks kinda ugly. see attached screenshot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1575896
Title:
Scrollbar thumb not drawn in firefox 46 (gtk3?)
Status in firefox package in Ubuntu:
Confirmed
Bug description:
As of today's firefox 46 release, the scrollbar thumb is not being
drawn, just see a thin grey bar on the right side of the window.
Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 2545 F pulseaudio
/dev/snd/controlC1: jbarnett 2545 F pulseaudio
/dev/snd/controlC3: jbarnett 2545 F pulseaudio
/dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-08-21 (250 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 172.16.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.16.1.0/24 dev wlp3s0 proto kernel scope link src 172.16.1.43 metric
600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
[Profile]/extensions/cookie...@jayapal.com/defaults/preferences/cookiemgr.js
[Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
[Profile]/extensions/{ea4637dc-e014-4c17-9c2c-879322d23268}/defaults/preferences/defaults.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
browser-plugin-freshplayer-nacl0.3.4-3
browser-plugin-freshplayer-pepperflash 0.3.4-3
adobe-flashplugin 1:20160407.1-0ubuntu1
gnome-shell3.20.1-0ubuntu1~xenial3
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-02-16 (71 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575896] Re: Scrollbar thumb not drawn in firefox 46 (gtk3?)
according to the add-ons panel, I only have installed the 'Default'
theme
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1575896
Title:
Scrollbar thumb not drawn in firefox 46 (gtk3?)
Status in firefox package in Ubuntu:
Confirmed
Bug description:
As of today's firefox 46 release, the scrollbar thumb is not being
drawn, just see a thin grey bar on the right side of the window.
Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 2545 F pulseaudio
/dev/snd/controlC1: jbarnett 2545 F pulseaudio
/dev/snd/controlC3: jbarnett 2545 F pulseaudio
/dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-08-21 (250 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 172.16.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.16.1.0/24 dev wlp3s0 proto kernel scope link src 172.16.1.43 metric
600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
[Profile]/extensions/cookie...@jayapal.com/defaults/preferences/cookiemgr.js
[Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
[Profile]/extensions/{ea4637dc-e014-4c17-9c2c-879322d23268}/defaults/preferences/defaults.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
browser-plugin-freshplayer-nacl0.3.4-3
browser-plugin-freshplayer-pepperflash 0.3.4-3
adobe-flashplugin 1:20160407.1-0ubuntu1
gnome-shell3.20.1-0ubuntu1~xenial3
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-02-16 (71 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1575896] [NEW] Scrollbar thumb not drawn in firefox 46 (gtk3?)
Public bug reported:
As of today's firefox 46 release, the scrollbar thumb is not being
drawn, just see a thin grey bar on the right side of the window.
Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jbarnett 2545 F pulseaudio
/dev/snd/controlC1: jbarnett 2545 F pulseaudio
/dev/snd/controlC3: jbarnett 2545 F pulseaudio
/dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini
or extensions.sqlite)
InstallationDate: Installed on 2015-08-21 (250 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819)
IpRoute:
default via 172.16.1.1 dev wlp3s0 proto static metric 600
169.254.0.0/16 dev docker0 scope link metric 1000 linkdown
172.16.1.0/24 dev wlp3s0 proto kernel scope link src 172.16.1.43 metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
[Profile]/extensions/cookie...@jayapal.com/defaults/preferences/cookiemgr.js
[Profile]/extensions/keefox@chris.tomlinson/defaults/preferences/prefs.js
[Profile]/extensions/{ea4637dc-e014-4c17-9c2c-879322d23268}/defaults/preferences/defaults.js
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=46.0/20160425114621 (In use)
RelatedPackageVersions:
google-talkplugin 5.41.0.0-1
browser-plugin-freshplayer-nacl0.3.4-3
browser-plugin-freshplayer-pepperflash 0.3.4-3
adobe-flashplugin 1:20160407.1-0ubuntu1
gnome-shell3.20.1-0ubuntu1~xenial3
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to xenial on 2016-02-16 (71 days ago)
dmi.bios.date: 06/05/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP114.88Z.0172.B04.1506051511
dmi.board.name: Mac-06F11FD93F0323C5
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,4
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-06F11FD93F0323C5
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5:
dmi.product.name: MacBookPro11,4
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug gnome3-ppa third-party-packages xenial
** Attachment added: "Screenshot from 2016-04-27 12-48-04.png"
https://bugs.launchpad.net/bugs/1575896/+attachment/4649456/+files/Screenshot%20from%202016-04-27%2012-48-04.png
** Description changed:
As of today's firefox 46 release, the scrollbar thumb is not being
- drawn. Probably related to switchover to gtk3. Gtk theme is the
- ubuntu-gnome default of Adwaita.
+ drawn, just see a thin grey bar on the right side of the window.
+ Probably related to switchover to gtk3. Gtk theme is the ubuntu-gnome
+ default of Adwaita.
See screenshot attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firefox 46.0+build5-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: jbarnett 2545 F pulseaudio
- /dev/snd/controlC1: jbarnett 2545 F pulseaudio
- /dev/snd/controlC3: jbarnett 2545 F pulseaudio
- /dev/snd/controlC2: jbarnett 2545 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jbarnett 2545 F pulseaudio
+ /dev/snd/controlC1: jbarnett 2545 F pulseaudio
+ /dev/snd/controlC3: jbarnett 2545 F pulseaudio
+ /dev/snd/controlC2: jbarnett 2545 F pulseaudio
BuildID: 20160425114621
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Apr 27 12:47:31 2016
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
- # interfaces(5) file used by ifup(8) and
[Desktop-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
1.18.2 from the x-staging ppa works, thanks Timo! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Committed Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1555434] Re: Black screen/system lockup on 4.4.0-11
I've just downgrade xserver back to 2:1.17.3-2ubuntu4 (and the input/video drivers to compatible previous versions) and no longer see this bug on kernel 4.4.0-13-generic ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1555434 Title: Black screen/system lockup on 4.4.0-11 Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: https://lists.ubuntu.com/archives/ubuntu-devel- discuss/2016-March/016281.html references xenial freezing when plugging in a 2nd monitor on a 2015 macbook pro. I'm seeing similar freezes when _unplugging_ the 2nd monitor -- the screen turns black and everything is unresponsive. Not sure that it happens every time, but have noticed it multiple times today (first time booting with 4.4.0-11), and have not seen it before today (yesterday was booting 4.4.0-10 and the freeze did not occur). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-11-generic 4.4.0-11.26 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jbarnett 2270 F pulseaudio /dev/snd/controlC1: jbarnett 2270 F pulseaudio CurrentDesktop: GNOME Date: Wed Mar 9 20:31:07 2016 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=dd225ec0-47f4-49d8-a51c-a2547f8eb945 InstallationDate: Installed on 2015-08-21 (201 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-11-generic N/A linux-backports-modules-4.4.0-11-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-02-16 (22 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() Status in evolution package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1493989] [NEW] After display goes to sleep, sometimes external monitor is black
Public bug reported: In a gnome session, my screen locks & turns off after a certain amount of inactivity (but the system is not in suspend). When I wake the display back up by moving mouse / hitting a key, it seems like my external monitor is redetected -- both internal & external screen blink black as if I had just plugged in my external monitor, and then _sometimes_ the external monitor stays black (but thinks it is receiving input). Other times it's fine, but when the issue happens, the displays control panel still thinks the external screen is connected, just nothing is visible. Unplugging & replugging the screen fixes the issue, and it happens maybe 1/2 the time the display locks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Sep 9 13:05:10 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.2, 4.2.0-7-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:0147] InstallationDate: Installed on 2015-08-21 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150819) MachineType: Apple Inc. MacBookPro11,4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-7-generic.efi.signed root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP114.88Z.0172.B04.1506051511 dmi.board.name: Mac-06F11FD93F0323C5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,4 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-06F11FD93F0323C5 dmi.modalias: dmi:bvnAppleInc.:bvrMBP114.88Z.0172.B04.1506051511:bd06/05/2015:svnAppleInc.:pnMacBookPro11,4:pvr1.0:rvnAppleInc.:rnMac-06F11FD93F0323C5:rvrMacBookPro11,4:cvnAppleInc.:ct9:cvrMac-06F11FD93F0323C5: dmi.product.name: MacBookPro11,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.6.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.6.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Wed Sep 9 11:12:13 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 41006 vendor APP xserver.version: 2:1.17.2-1ubuntu6 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1493989 Title: After display goes to sleep, sometimes external monitor is black Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: In a gnome session, my screen locks & turns off after a certain amount of inactivity (but the system is not in suspend). When I wake the display back up by moving mouse / hitting a key, it seems like my external monitor is redetected -- both internal & external screen blink black as if I had just plugged in my external monitor, and then _sometimes_ the external monitor stays black (but thinks it is receiving input). Other times it's fine, but when the issue happens, the displays control panel still thinks the external screen is connected, just nothing is visible. Unplugging & replugging the screen fixes the issue, and it happens maybe 1/2 the time the display locks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() Status in evolution package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() Status in evolution package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1492318 Title: evolution crashed with signal 5 in g_object_new_valist() Status in evolution package in Ubuntu: New Bug description: 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1492318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1321903] Re: location box dropdown displays on wrong monitor
this seems to be related to me customizing layout.css.devPixelsPerPx as
per upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=1068390
** Bug watch added: Mozilla Bugzilla #1068390
https://bugzilla.mozilla.org/show_bug.cgi?id=1068390
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1068390
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1321903
Title:
location box dropdown displays on wrong monitor
Status in Mozilla Firefox:
Unknown
Status in firefox package in Ubuntu:
New
Bug description:
if I have a firefox window toward the left side of my right monitor,
when I type something in the location box, the dropdown shortcuts
appear on the rightmost edge of the left monitor. If i move the
firefox window further toward the middle/right side of the right
screen, it appears below the location box as it should. The boundary
appears to be around 1450 pixels from the left hand side of the right
screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 30.0+build1-0ubuntu0.14.04.3
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia wl
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: jbarnett 2982 F pulseaudio
/dev/snd/controlC0: jbarnett 2982 F pulseaudio
/dev/snd/controlC1: jbarnett 2982 F pulseaudio
BuildID: 20140428193813
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 21 12:35:18 2014
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2014-02-24 (86 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140218)
IpRoute:
default via 10.9.0.1 dev wlan0 proto static
10.9.0.0/23 dev wlan0 proto kernel scope link src 10.9.0.55 metric 9
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1321903/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1321903] Re: location box dropdown displays on wrong monitor
this also affects hover text, right click context menu, allow/block
plugins popups, etc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1321903
Title:
location box dropdown displays on wrong monitor
Status in firefox package in Ubuntu:
New
Bug description:
if I have a firefox window toward the left side of my right monitor,
when I type something in the location box, the dropdown shortcuts
appear on the rightmost edge of the left monitor. If i move the
firefox window further toward the middle/right side of the right
screen, it appears below the location box as it should. The boundary
appears to be around 1450 pixels from the left hand side of the right
screen.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 30.0+build1-0ubuntu0.14.04.3
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
NonfreeKernelModules: nvidia wl
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: jbarnett 2982 F pulseaudio
/dev/snd/controlC0: jbarnett 2982 F pulseaudio
/dev/snd/controlC1: jbarnett 2982 F pulseaudio
BuildID: 20140428193813
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed May 21 12:35:18 2014
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2014-02-24 (86 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140218)
IpRoute:
default via 10.9.0.1 dev wlan0 proto static
10.9.0.0/23 dev wlan0 proto kernel scope link src 10.9.0.55 metric 9
Locales: extensions.sqlite corrupt or missing
PrefSources:
prefs.js
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/ubu...@ubuntu.com/defaults/preferences/001ubuntu-gnome-mods.js
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=29.0/20140428193813 (In use)
RunningIncompatibleAddons: False
SourcePackage: firefox
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1321903/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [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 Desktop Packages, 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 Status in gnome-control-center package in Ubuntu: New Bug description: This morning, the following packages upgraded. Since doing so (and restarting, but not sure how related that is), keyboard input in gnome applications periodically freezes, while I can still input to xterms, use the mouse to switch focus, etc The typed keys eventualy show up in the applications they're typed into, but the specific application being typed into completely freezes Upgrade: libgnome-desktop-3-dev:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) gir1.2-clutter-1.0:amd64 (1.22.2-1~vivid0, 1.22.4-1~vivid1) libclutter-gtk-1.0-0:amd64 (1.6.0-1, 1.6.2-1~vivid1) gnome-shell:amd64 (3.16.2-0ubuntu1~vivid1, 3.16.3-1ubuntu1~vivid1) libwmf0.2-7:amd64 (0.2.8.4-10.3ubuntu1, 0.2.8.4-10.3ubuntu1.15.04.1) adobe-flashplugin:amd64 (20150623.1-0vivid1, 20150708.1-0vivid1) gir1.2-gnomedesktop-3.0:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) firefox-locale-en:amd64 (38.0+build3-0ubuntu0.15.04.1, 39.0+build5-0ubuntu0.15.04.1) gir1.2-gtkclutter-1.0:amd64 (1.6.0-1, 1.6.2-1~vivid1) adwaita-icon-theme-full:amd64 (3.16.0-0ubuntu1~vivid2, 3.16.2.1-2ubuntu1~vivid1) firefox:amd64 (38.0+build3-0ubuntu0.15.04.1, 39.0+build5-0ubuntu0.15.04.1) libgnome-desktop-3-10:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) libwmf0.2-7-gtk:amd64 (0.2.8.4-10.3ubuntu1, 0.2.8.4-10.3ubuntu1.15.04.1) gnome-control-center-shared-data:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) gnome-shell-common:amd64 (3.16.2-0ubuntu1~vivid1, 3.16.3-1ubuntu1~vivid1) gnome-control-center:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) libgnome-control-center1:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) libclutter-1.0-0:amd64 (1.22.2-1~vivid0, 1.22.4-1~vivid1) gir1.2-mutter-3.0:amd64 (3.16.2-0ubuntu1~vivid2, 3.16.3-1ubuntu1~vivid1) adwaita-icon-theme:amd64 (3.16.0-0ubuntu1~vivid2, 3.16.2.1-2ubuntu1~vivid1) gnome-desktop3-data:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) mutter:amd64 (3.16.2-0ubuntu1~vivid2, 3.16.3-1ubuntu1~vivid1) mutter-common:amd64 (3.16.2-0ubuntu1~vivid2, 3.16.3-1ubuntu1~vivid1) adobe-flash-properties-gtk:amd64 (20150623.1-0vivid1, 20150708.1-0vivid1) libclutter-1.0-dbg:amd64 (1.22.2-1~vivid0, 1.22.4-1~vivid1) libclutter-1.0-common:amd64 (1.22.2-1~vivid0, 1.22.4-1~vivid1) libmutter0f:amd64 (3.16.2-0ubuntu1~vivid2, 3.16.3-1ubuntu1~vivid1) gnome-control-center-data:amd64 (3.16.1-0ubuntu1~vivid1, 3.16.2-2ubuntu1~vivid1) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-shell 3.16.3-1ubuntu1~vivid1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jul 9 10:22:26 2015 DisplayManager: gdm InstallationDate: Installed on 2014-02-24 (500 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to vivid on 2015-02-04 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1473154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
