[Desktop-packages] [Bug 1947920] Re: tracker-miner-f 100% CPU and slows system down
Thank you for your bug report, could you perhaps report it directly upstream on https://gitlab.gnome.org/GNOME/tracker/issues ? ** Changed in: tracker (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: New Bug description: tracker-miner-f has been using 100% CPU and my system making it almost unresponsive. This happens around once a month or so when I boot up. It sometimes lasts for a number of days (or a number of resets) until the system becomes responsive again. The command "tracker status" always shows the same thing: "Estimated less than one second left" although it appears that everything is already indexed because the file and folder counts do not increase. Even so tracker-miner-f is still showing 100% CPU inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101154 files, 16046 folders Remaining space on database partition: 160.5 GB (64.11%) Data is still being indexed: Estimated less than one second left inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101155 files, 16045 folders Remaining space on database partition: 161.1 GB (64.31%) Data is still being indexed: Estimated 01h 19m 03s left ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker 2.3.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:25:58 2021 InstallationDate: Installed on 2021-06-28 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) UPDATE I have now reset the tracker and it seems to be going through and indexing everything again. tracker reset --hard Now tracker-miner-f has re-indexed everything and tracker-extract and tracker-store are running. UPDATE 2 The tracker reset completed indexing everything and the went into idle state. However when rebooting, tracker-miner-f went to 100% CPU once again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1871644]
Emilio, you're absolutely right :) There's original Bug 1408360 for it. For custom themes we need to apply alpha component only and keep original color from theme (i.e. paint over alpha from theme). Emilio, how is the best way how to do it? We can introduce a new appearance (-moz-window-titlebar-alpha for instance) which contains only alpha component from titlebar and paint it over theme color or use existing one (-moz-window-titlebar) but I'm not very experienced in js/css styling so I'll appreciate any help here. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246287 Bug 1509931 - Add support for chrome-only environment variables. r=stransky This bit is taken straight from D73454 (I reviewed it but I guess another pair of eyes is ok, it's really straight-forward). Co-authored-by: Nicklas Boman -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246289 Bug 1509931 - Use titlebar radius on Linux and make titlebar set-up work for lightweight themes. r=stransky!,dao! Depends on D128680 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
*** Bug 1706752 has been marked as a duplicate of this bug. *** -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246290 Bug 1509931 - Remove -moz-gtk-csd-transparent-background. r=stransky We always use alpha visual for WebRender, and appearance: none is unnecessary (root element has no intrinsic appearance). Depends on D128681 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Ah, I think I know why that might be... -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Pushed by ealva...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/81ca2d28c253 Simplify titlebar buttons CSS. r=desktop-theme-reviewers,dao -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246291 Bug 1509931 - Simplify titlebar buttons CSS. r=stransky There's no need to use the media query to set the default styles of the buttons, we only need to hide them if appropriate. Depends on D128682 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Martin Stránský [:stransky] (ni? me) from comment #11) > Emilio, how is the best way how to do it? We can introduce a new appearance > (-moz-window-titlebar-alpha for instance) which contains only alpha component > from titlebar and paint it over theme color or use existing one > (-moz-window-titlebar) but I'm not very experienced in js/css styling so I'll > appreciate any help here. I don't think that's super-great, I think I have an idea which should be relatively simple, stealing. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #17) > Created attachment 9246290 > Bug 1509931 - Remove -moz-gtk-csd-transparent-background. r=stransky > > > We always use alpha visual for WebRender KDE with disabled compositor, i3, etc. use alpha visual, but it's not transparent. Could -moz-gtk-csd-transparent-background be defined with gdk_screen_is_composited() and be used to forbid outer border-radius + outer shadow of main menu/addon/etc. widgets to remove any Xshape usage (bug 1730991 comment 6)? According to the Chromium bugtracker, Xshape also causes performance problems (bug 1730991 comment 7). -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246288 Bug 1509931 - Expose titlebar radius as a chrome-only CSS environment variable. r=stransky Mostly plumbing. Depends on D128679 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Created attachment 9246314 Bug 1509931 - Use a more precise toolbar radius. r=stransky This seemed possible/maybe worth doing, but let me know if you'd rather keep the 10 hard-coded. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #20) Non-composited X11 (the legacy variant of X11: i3, KDE with manually disabled compositor, etc.) does not support transparency. Everything that would usually be transparent/alpha is just black/opaque. Menus and window corners had [shadows on black background](https://bug1479135.bmoattachments.org/attachment.cgi?id=8995686) (=fat black borders). The autoscroll icon was a [black square with a white circle](https://bug1649246.bmoattachments.org/attachment.cgi?id=9160184) in it. [XShapeCombineMask](https://searchfox.org/mozilla- central/search?q=XShapeCombineMask&path=) is implemented for software rendering only. Firefox creates a stencil (like a cookie cutter) of where transparency needs to get cut off. X11 then applies this stencil on every frame. The outer shadow of a rounded main menu, addon widget or [window titlebar](https://searchfox.org/mozilla- central/rev/37373cdeed20695af1ff1fd090f0736d9bf15e65/widget/gtk/nsWindow.cpp#6729,6793) has transparency, so it gets cut off by X11, leaving a rounded widget without shadow. XShapeCombineMask is not implemented for hardware rendering. That's why SW WR is enforced for menus, addons and autoscroll icon on non-composited X11 to make use of XShapeCombineMask while the main window is still using OpenGL. XShapeCombineMask * caused problems on [Mutter](https://searchfox.org/mozilla-central/rev/37373cdeed20695af1ff1fd090f0736d9bf15e65/widget/gtk/nsWindow.cpp#9084) back then * crashes the GPU process on Nvidia: bug 1730991 * causes performance problems according to the Chromium bugtracker: bug 1733094 comment 18,https://bugs.chromium.org/p/chromium/issues/detail?id=1198080 Could XShapeCombineMask be removed and instead menus and the autoscroll icon loose their border-radius (become rectangular) and loose their shadow (to avoid black background) if gdk_screen_is_composited() is false? IIUC, that would reduce code complexity, improve stability and performance. A rectangular autoscroll icon on non-composited X11 would be noticeable. But users choose non-composited X11 to get more performance than with composited X11. Considering this as well, it doesn't make sense to use XShapeCombineMask which contradicts their intent and causes above problems. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Darkspirit from comment #19) > KDE with disabled compositor, i3, etc. use alpha visual, but it's not > transparent. WDYM, just that the background wouldn't be transparent? > Could -moz-gtk-csd-transparent-background be defined with > gdk_screen_is_composited() > and be used to forbid outer border-radius + outer shadow of main > menu/addon/etc. widgets > to remove any Xshape usage (bug 1730991 comment 6)? > According to the Chromium bugtracker, Xshape also causes performance problems > (bug 1730991 comment 7). I'm not sure about this (not familiar with XShape at all). This patch stack makes Wayland look great, but on X11/XWayland I still see the compositor shadow drawn around the crisp corner when using a lightweight theme... Do you know whether that's avoidable Martin? -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
I fixed the wayland overdraw and the X11 artifacts, so I think this is ready to go. I've tested this stack on KWin and GNOME, both X11 and Wayland. Will test i3 and such asap. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Pushed by emi...@crisal.io: https://hg.mozilla.org/integration/autoland/rev/2be88317a6c0 Fix rebase mistake. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
https://hg.mozilla.org/mozilla-central/rev/c9399923df7b https://hg.mozilla.org/mozilla-central/rev/bcdfe3daf980 https://hg.mozilla.org/mozilla-central/rev/2be88317a6c0 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #43) > Yeah, so `nsWindow::GetTitlebarRadius` can be called off the main thread > which seems unfortunate. We can fix this easily by moving the titlebar radius > to a member or such. I can fix that as a part of Bug 1736518. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Emilio, I tested the patches and it looks great! -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Yeah, so `nsWindow::GetTitlebarRadius` can be called off the main thread which seems unfortunate. We can fix this easily by moving the titlebar radius to a member or such. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
We have a technical debt here as we don't use titlebar rendering in testsuite - I'll look at it. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Oh, great, let me know if I can help. Probably a static atomic integer in nsLookAndFeelGtk is slightly easier to invalidate in practice. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Emilio, when running testsuite with the patch (locally) I'm getting this crash: 2:05.41 GECKO(53217) Assertion failure: sInServoTraversal || NS_IsMainThread(), at /home/komat/src/objdir-opt/dist/include/mozilla/ServoUtils.h:33 2:05.41 GECKO(53217) #01: mozilla::ServoStyleSet::IsInServoTraversal() [/home/komat/src/objdir-opt/dist/include/mozilla/ServoStyleSet.h:103] 2:05.41 GECKO(53217) #02: mozilla::Preferences::InitStaticMembers() [/home/komat/src/modules/libpref/Preferences.cpp:3464] 2:05.41 GECKO(53217) #03: nsresult mozilla::Internals::GetPrefValue(char const*, int*&, mozilla::PrefValueKind) [/home/komat/src/modules/libpref/Preferences.cpp:4439] 2:05.41 GECKO(53217) #04: mozilla::Preferences::GetInt(char const*, int*, mozilla::PrefValueKind) [/home/komat/src/modules/libpref/Preferences.cpp:0] 2:05.41 GECKO(53217) #05: nsXPLookAndFeel::GetFloatValue(mozilla::LookAndFeel::FloatID, float&) [/home/komat/src/widget/nsXPLookAndFeel.cpp:894] 2:05.41 GECKO(53217) #06: nsWindow::GetTitlebarRadius() [/home/komat/src/widget/gtk/nsWindow.cpp:6111] 2:05.41 GECKO(53217) #07: nsWindow::GetTitlebarRect() [/home/komat/src/widget/gtk/nsWindow.cpp:6438] 2:05.41 GECKO(53217) #08: mozilla::widget::GtkCompositorWidget::GetTransparentRegion() [/home/komat/src/widget/gtk/GtkCompositorWidget.cpp:0] 2:05.41 GECKO(53217) #09: mozilla::wr::RenderCompositorSWGL::AllocateMappedBuffer(mozilla::wr::Box2D const*, unsigned long) [/home/komat/src/gfx/webrender_bindings/RenderCompositorSWGL.cpp:149] 2:05.41 GECKO(53217) #10: mozilla::wr::RenderCompositorSWGL::StartCompositing(mozilla::wr::ColorF, mozilla::wr::Box2D const*, unsigned long, mozilla::wr::Box2D const*, unsigned long) [/home/komat/src/gfx/webrender_bindings/RenderCompositorSWGL.cpp:185] 2:05.41 GECKO(53217) #11: ::start_compositing [gfx/wr/webrender/src/compositor/sw_compositor.rs:1400] 2:05.41 GECKO(53217) #12: webrender::renderer::Renderer::draw_frame [gfx/wr/webrender/src/renderer/mod.rs:4582] 2:05.41 GECKO(53217) #13: webrender::renderer::Renderer::render_impl [gfx/wr/webrender/src/renderer/mod.rs:2009] 2:05.41 GECKO(53217) #14: webrender::renderer::Renderer::render [gfx/wr/webrender/src/renderer/mod.rs:0] 2:05.41 GECKO(53217) #15: wr_renderer_render [gfx/webrender_bindings/src/bindings.rs:623] 2:05.41 GECKO(53217) #16: mozilla::wr::RendererOGL::UpdateAndRender(mozilla::Maybe > const&, mozilla::Maybe const&, mozilla::Maybe > const&, bool*, mozilla::wr::RendererStats*) [/home/komat/src/gfx/webrender_bindings/RendererOGL.cpp:186] 2:05.42 GECKO(53217) #17: mozilla::wr::RenderThread::UpdateAndRender(mozilla::wr::WrWindowId, mozilla::layers::BaseTransactionId const&, mozilla::TimeStamp const&, bool, mozilla::Maybe > const&, mozilla::Maybe const&, mozilla::Maybe > const&, bool*) [/home/komat/src/gfx/webrender_bindings/RenderThread.cpp:0] 2:05.42 GECKO(53217) [Parent 53217: Main Thread]: D/Widget GetScreenBounds [7fba6021a000] 95,55 -> 1280 x 1012, unscaled 95,55 -> 1280 x 1012 2:05.42 GECKO(53217) #18: mozilla::wr::RenderThread::HandleFrameOneDoc(mozilla::wr::WrWindowId, bool) [/home/komat/src/gfx/webrender_bindings/RenderThread.cpp:355] 2:05.42 GECKO(53217) [Parent 53217: Main Thread]: D/Widget Events sent from focus in event [7fba6021a000] 2:05.42 GECKO(53217) #19: mozilla::detail::RunnableMethodImpl::Run() [/home/komat/src/objdir-opt/dist/include/nsThreadUtils.h:1203] Any idea what can be wrong? -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackag
[Desktop-packages] [Bug 1871644]
May nsWindow::GetTitlebarRadius() be called from render thread? (this is sw-wr). -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Pushed by ealva...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c9399923df7b Remove -moz-gtk-csd-transparent-background. r=stransky,desktop-theme-reviewers,dao https://hg.mozilla.org/integration/autoland/rev/bcdfe3daf980 Use a more precise toolbar radius. r=stransky -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #26) > If we do want to do the cleanup described above, we might need a new media > query which determines this (but it should definitely not have `csd` in the > name, since it is not about csd at all). So I'd rather clean up the existing > one since it's confusing at best. > And in all cases this patch stack doesn't regress behavior (and improves it in the obvious cases). So I'd say comment 25 should be a separate bug? Yes. I only remembered that a query like `-moz-gtk-csd-transparent- background` might be useful to allow Xshape removal (if it is desired). -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Pushed by ealva...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/257c4f510cfd Add support for chrome-only environment variables. r=stransky https://hg.mozilla.org/integration/autoland/rev/a1e159fd2136 Expose titlebar radius as a chrome-only CSS environment variable. r=stransky -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
Okay, fair enough. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F
** 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/1947746 Title: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F Status in firefox package in Ubuntu: New Bug description: Trezor U2F security key doesn't work with firefox snap after updating to Ubuntu 21.10, but works with apt debian firefox package. Steps to reproduce: 1) Insert Trezor U2F security key in USB port. 2) Launch `run snap firefox` (it is the default on Ubuntu 21.10) 3) Test https://demo.yubico.com/webauthn-technical/registration It works well on Ubuntu 21.04 and on traditional apt debian installation. $ snap list firefox Name Version Rev Tracking Publisher Notes firefox 93.0-1 631 latest/stable mozilla✓ - $ snap connections firefox Interface PlugSlot Notes audio-playbackfirefox:audio-playback :audio-playback - audio-record firefox:audio-record:audio-record - avahi-observe firefox:avahi-observe :avahi-observe - browser-support firefox:browser-sandbox :browser-support - camerafirefox:camera :camera - content[gnome-3-38-2004] firefox:gnome-3-38-2004 gnome-3-38-2004:gnome-3-38-2004 - content[gtk-3-themes] firefox:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] firefox:icon-themes gtk-common-themes:icon-themes- content[sound-themes] firefox:sound-themes gtk-common-themes:sound-themes - cups-control firefox:cups-control:cups-control - dbus - firefox:dbus-daemon - desktop firefox:desktop :desktop - desktop-legacyfirefox:desktop-legacy :desktop-legacy - gsettings firefox:gsettings :gsettings - hardware-observe firefox:hardware-observe:hardware-observe - home firefox:home:home - joystick firefox:joystick- - mpris - firefox:mpris - network firefox:network :network - network-observe firefox:network-observe - - openglfirefox:opengl :opengl - personal-filesfirefox:dot-mozilla-firefox :personal-files - removable-media firefox:removable-media :removable-media - screen-inhibit-controlfirefox:screen-inhibit-control :screen-inhibit-control - system-files firefox:etc-firefox-policies:system-files - system-packages-doc firefox:system-packages-doc :system-packages-doc - u2f-devices firefox:u2f-devices :u2f-devices - unity7firefox:unity7 :unity7 - upower-observefirefox:upower-observe :upower-observe - wayland firefox:wayland :wayland - x11 firefox:x11 :x11 - $ cat /etc/os-release PRETTY_NAME="Ubuntu 21.10" NAME="Ubuntu" VERSION_ID="21.10" VERSION="21.10 (Impish Indri)" VERSION_CODENAME=impish ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=impish $ echo $XDG_SESSION_TYPE wayland $ uname -r 5.13.0-19-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/+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 1947971] [NEW] Zsys fails in update-grub after disk is restored with Acronis True Image
Public bug reported: For years, I have been backing up my Ubuntu OS using Acronis True Image under Windows 10, and restoring it as needed. This has worked well. Recently, I started experimenting with Ubuntu 20.04 and zfs on root. I did a full reinstall of Ubuntu on my SSD for this. I naturally backed it up with Acronis under Windows. At some point, I decided to restore that backup using Acronis. At that point, zsys started reporting problems when creating snapshots during operations such as "apt install" and "apt remove". A simpler test case is to create a manual snapshot : root@server10g:/home/madbrain/Desktop# zsysctl save test-snapshot -s ZSys is adding automatic system snapshot to GRUB menu ERROR "update-grub" returned an error: exit status 2 root@server10g:/home/madbrain/Desktop# Is there a workaround for this problem ? I realize that this is not a common situation, and I should be backing up and restoring zfs snapshots rather than using Acronis, but Acronis has the advantage of having a GUI, and zsys is still experimental. So, I would expect a True Image restore of Ubuntu to still work. Unfortunately, that's not the case. My guess is that there was some sort of partition identifier that was changed during the backup/restore process in Acronis, but I'm not sure what. ** Affects: zsys (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1947971 Title: Zsys fails in update-grub after disk is restored with Acronis True Image Status in zsys package in Ubuntu: New Bug description: For years, I have been backing up my Ubuntu OS using Acronis True Image under Windows 10, and restoring it as needed. This has worked well. Recently, I started experimenting with Ubuntu 20.04 and zfs on root. I did a full reinstall of Ubuntu on my SSD for this. I naturally backed it up with Acronis under Windows. At some point, I decided to restore that backup using Acronis. At that point, zsys started reporting problems when creating snapshots during operations such as "apt install" and "apt remove". A simpler test case is to create a manual snapshot : root@server10g:/home/madbrain/Desktop# zsysctl save test-snapshot -s ZSys is adding automatic system snapshot to GRUB menu ERROR "update-grub" returned an error: exit status 2 root@server10g:/home/madbrain/Desktop# Is there a workaround for this problem ? I realize that this is not a common situation, and I should be backing up and restoring zfs snapshots rather than using Acronis, but Acronis has the advantage of having a GUI, and zsys is still experimental. So, I would expect a True Image restore of Ubuntu to still work. Unfortunately, that's not the case. My guess is that there was some sort of partition identifier that was changed during the backup/restore process in Acronis, but I'm not sure what. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1947971/+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 1871644]
Created attachment 9246335 titlebar CSS rounded borders properties -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
https://hg.mozilla.org/mozilla-central/rev/257c4f510cfd https://hg.mozilla.org/mozilla-central/rev/a1e159fd2136 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
So, querying the individual border-radius properties doesn't work. I get: > (firefox:17330): Gtk-WARNING **: 00:39:54.651: Style property "border- top-left-radius" is not gettable And same for the other corners of course. However, my patch works, because of [this code](https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-20/gtk/gtkcssshorthandpropertyimpl.c#L961-977). Basically, querying `border-radius` on gtk3 returns the `border-top- left-radius`, which happens to work for us, yay :) So given there's no way to access the other border corners, and that this works for our purposes, I think we should probably just roll with it, thoughts? -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1936826]
*** Bug 2016259 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1936826]
*** Bug 2015852 has been marked as a duplicate of this bug. ***
--
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/1936826
Title:
gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
[st-focus-manager.c:199]
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell package in Fedora:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/a7fed12980ff951be9a10c4f2e04d99a23b010ae
---
Testing daily Ubuntu Impish ISO 2021-07-19
Test machine : Dell [Latitude] 7280 (i5-7300U,
Received the error message - Ubuntu has experienced an internal error
...do you want to send ...etc, etc.
This bug occurred when I was scrolling up and down on the "Settings"
app and selected "Appearance".
ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: gnome-shell 40.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 19 12:15:54 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'40.2'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'is')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-07-19 (0 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210719)
ProcCmdline: /usr/bin/gnome-shell
RelatedPackageVersions: mutter-common 40.2.1-1ubuntu1
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
st_focus_manager_remove_group () from /usr/lib/gnome-shell/libst-1.0.so
g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_focus_manager_remove_group()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1936826/+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 1871644]
Well, perhaps, but that seems tangential to this bug, isn't it? We don't use XShapeCombineMask for the titlebar and this patch stack doesn't start doing that. If we do want to do the cleanup described above, we might need a new media query which determines this (but it should definitely not have `csd` in the name, since it is not about csd at all). So I'd rather clean up the existing one since it's confusing at best. Anyways, things I've tested: * KWin (Wayland/X11/XWayland) * GNOME (Wayland/X11/XWayland) with a variety of GTK themes * i3 * bspwm And in all cases this patch stack doesn't regress behavior (and improves it in the obvious cases). So I'd say comment 25 should be a separate bug? If someone has an exotic setup and wants to give this a try before it lands, or wants to provide feedback, builds should be here eventually: https://treeherder.mozilla.org/jobs?repo=try&revision=327533608921f19068d1b8898b094fb3b3cdfc9d -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
https://hg.mozilla.org/mozilla-central/rev/81ca2d28c253 -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
(In reply to Emilio Cobos Álvarez (:emilio) from comment #30) > So given there's no way to access the other border corners, and that this > works for our purposes, I think we should probably just roll with it, > thoughts? I'd agree - should work well for almost everyone. One question I had to think of is if we want to use rounded corners at the bottom at some point - more and more GTK4 apps do that, e.g. nautilus/files. But we can also leave that for the future. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1871644]
btw. It would be great to get border-radius from menu elements (Adwaita uses it) and use it in gecko too, for context menus for instance. But that may be a different bug. -- 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/1871644 Title: Top corners of Firefox windows have weird black protrusions from the rounded edges Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Image to illustrate the problem is attached. All firefox windows on Wayland (EDIT: and X11) have a weird black protrusion from the top- left and top-right corners where yaru has curved the window corners, but something from Firefox appears to not be being clipped by the theme. I need to double check whether this appears on X11, but for now consider it Wayland only until I report back, although oSoMoN has checked their system and they don't see the behaviour (on X11). EDIT: I have now checked X11 on my system and I see the same behaviour as described above, so this is affecting BOTH Wayland AND X11 for me. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 BuildID: 20200403170909 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 14:48:56 2020 InstallationDate: Installed on 2020-03-03 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1871644/+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 1946098] Re: Update to 91.2.0 in impish
** Changed in: thunderbird (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1946098 Title: Update to 91.2.0 in impish Status in thunderbird package in Ubuntu: New Bug description: impish currently has thunderbird 1:91.1.2+build1-0ubuntu1, which at the time of filing this bug is the latest stable release (so all is good). There is a new release candidate, 91.2.0+build1 (https://ftp.mozilla.org/pub/thunderbird/candidates/91.2.0-candidates/build1/) which, if everything goes fine, will become a release before impish is released. I intend to upload that RC to impish-proposed, so I'm filing this bug for the release team to decide whether it's worth accepting in the release, or leaving it out as a 0-day SRU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1946098/+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 1947970] [NEW] Xorg freeze
You have been subscribed to a public bug: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1947970 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1922884] Re: transmission-gtk segfault (core dumped)
could you get a backtrace as described on https://wiki.ubuntu.com/DebuggingProgramCrash ? ** Changed in: transmission (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1922884 Title: transmission-gtk segfault (core dumped) Status in transmission package in Ubuntu: Incomplete Bug description: Unable to launch transmission-gtk application, segfault. Ubuntu 21.04 up-to-date. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: transmission-gtk 3.00-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 7 09:47:02 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to hirsute on 2020-06-09 (301 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1922884/+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 1947970] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947970 Title: [radeon] Graphics freeze Status in Ubuntu: Invalid Bug description: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947970/+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 1947970] Re: Xorg freeze
> so I am planning to go back to the original Ubuntu drivers Please do that and then open a new bug. We can't support all the custom graphics packages you have installed from PPAs. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid ** Tags added: radeon ** Summary changed: - Xorg freeze + [radeon] Graphics freeze -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1947970 Title: [radeon] Graphics freeze Status in Ubuntu: Invalid Bug description: I know I am using non-standard drivers right now, but that was only after I first experienced the problem. I also already replaced the video card TURKS->JUNIPER, but the problem is the same. Later mesa drivers seem to make the problem worse, so I am planning to go back to the original Ubuntu drivers. They too had the problem and made me try other drivers. The problem seems to occur after 'some other error, like network errors', so suspect to me is PCI bus stuff. More logs and info available. I also reported the problem to the mesa team, but thought Ubuntu might want to help, as I guess Caonical wants to offer a stable Linux. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-89.100-generic 5.4.143 Uname: Linux 5.4.0-89-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: LXQt Date: Thu Oct 21 15:32:19 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-88-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-89-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:68bf] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Juniper PRO [Radeon HD 6750] [1002:] InstallationDate: Installed on 2020-11-05 (349 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: MSI MS-7817 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-89-generic root=UUID=223bdcf0-4c35-4422-bf23-522ebd0ff1ff ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 03/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.9:bd03/30/2015:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1~kisak~f version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.4~kisak1~f version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1947970/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
FYI this problem also exists under Manjaro + Gnome 40.4.0 + Wayland Thunderbird version 91.2.0 gnome-shell-extension-dash-to-dock 70-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1018204] Re:
** Changed in: libxml2 (Fedora) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1018204 Title: http://googlechromereleases.blogspot.com/2012/06/stable-channel- update_26.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1018204/+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 1947516] Re: Invisible mouse cursor in games (TF2, CS:GO, LoL, HL2) Wayland Ubuntu 21.10
Also happens with Crusader Kings 2. Using AMD Caicos. -- 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/1947516 Title: Invisible mouse cursor in games (TF2, CS:GO, LoL, HL2) Wayland Ubuntu 21.10 Status in xwayland package in Ubuntu: Confirmed Bug description: I upgraded my system (21.04) to the lastest release which is Ubuntu 21.10 "Impish inri" and while everything went smooth as butter, when i tried to play games like League of Legends under Wine with Lutris and native Linux games such as TF2, CS:GO, Half-Life 2, Left 4 dead, Game Dev Tycoon, etc. The mouse cursor in games was invisible, it was there because i could still click options, new game, etc. General specs: Computer Model: Hewlett-Packard HP Pavilion 14 Notebook PC RAM: 8GB (6.7GB available) Processor: AMD® A8-6410 apu with amd radeon r5 graphics × 4 Graphics: AMD® Kabini (I'm using AMDGPU) HDD: 500.1 GB OS: Ubuntu 21.10 OS Type: 64 bits Gnome Version: 40.4.0 Window system: Wayland (Currently im using Xorg thus it says X11) I installed the OS from scratch and the issue still persist, however like before doing it it's only present when using Wayland because on X11 i can see the cursor to navigate menus as one would do usually. If you need any additional info just let me know and thanks for reading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1947516/+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 1917037] Re: Frozen screen (NVidia GM107 card with large 3840 × 2160 screen)
Unfortunately, I still experience freezes after the GM107GL graphics card exchange - perhaps less often but it's hard to tell. The only positive outcome is the now silent operation of the workstation. I'll keep looking into the hardware side, but I'm back to square one, it could be a software bug too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1917037 Title: Frozen screen (NVidia GM107 card with large 3840 × 2160 screen) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Just after the screen freezes, I am sometimes able to log in with SSH and the log file typically reads: Feb 26 11:18:15 is233895 kernel: [15385.625416] nouveau :01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Feb 26 11:18:15 is233895 kernel: [15385.625436] nouveau :01:00.0: fifo: runlist 0: scheduled for recovery Feb 26 11:18:15 is233895 kernel: [15385.625453] nouveau :01:00.0: fifo: channel 6: killed Feb 26 11:18:15 is233895 kernel: [15385.625462] nouveau :01:00.0: fifo: engine 5: scheduled for recovery Feb 26 11:18:15 is233895 kernel: [15385.625467] nouveau :01:00.0: fifo: engine 0: scheduled for recovery Feb 26 11:18:15 is233895 kernel: [15385.626095] nouveau :01:00.0: Xorg[2366]: channel 6 killed! However, the machine eventually locks up and I cannot log in with SSH any more. Then I need to power down the computer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 26 11:45:55 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K1200] [10de:13bc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K1200] [10de:1140] InstallationDate: Installed on 2020-04-09 (322 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Precision Tower 3620 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.16.2 dmi.board.name: 0MWYPT dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.16.2:bd08/13/2020:svnDellInc.:pnPrecisionTower3620:pvr:rvnDellInc.:rn0MWYPT:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: Precision dmi.product.name: Precision Tower 3620 dmi.product.sku: 06B7 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1917037/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
** Description changed: [Impact] - * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: + * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. + Reverting the problematic commit will fix the usecase reported in this + bug (and all applications where copying from Nautilus and pasting the + data into a text-based input makes sense), but will break copying + to/from Desktop Icons extension. + + I recommend reporting the Desktop Icons extension issue (present already + in every later Ubuntu release) in a separate bug and track the fix + there. + [Test Plan] - 1. Open nautilus. - 2. Right-click on any file or directory and select 'Copy' from the context menu. - 3. Open gnome-terminal and right-click paste the contents of the clipboard. + 1. Open nautilus. + 2. Right-click on any file or directory and select 'Copy' from the context menu. + 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] - * There are some workarounds listed in the upstream bug so fixing the - root cause may break environments with those workarounds in place. + * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. + * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). + + [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 + [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] - + Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: New Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Hi, I am on 21.10 with intel driver and latest displaylink from their website. Everything used to work decently until a couple of day ago when I started seeing the external monitor very slow. I was on 21.04 and after an update it has started being slow. 1. It is slower when more things change on the screen, only the mouse works slow a full screen rendering is unusably slow. 2. on the login screen the screen works very well, as I was used to. 3. Audio work fine, rendering is very slow About my pc 1. Linux vin 5.13.0-20-generic #20-Ubuntu SMP Fri Oct 15 14:21:35 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 2. Driver from display link displaylink-driver-5.4.1-55.174 3. Tried X11 and Wayland from GDM with Gnome I tried to troubleshoot as described here https://wiki.archlinux.org/title/DisplayLink and setting LIBGL_DRI3_DISABLE=true as said here but it does not change Any hint is appreciated! Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1948002] [NEW] software-properties-gtk crashes
Public bug reported: When I try to run "Software and updates" from launcher, nothing happens, try to do so in terminal, there is a report: @ubuntux:~$ software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.175:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.175 was not provided by any .service files Ubuntu 20.04.3 LTS ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1948002 Title: software-properties-gtk crashes Status in software-properties package in Ubuntu: New Bug description: When I try to run "Software and updates" from launcher, nothing happens, try to do so in terminal, there is a report: @ubuntux:~$ software-properties-gtk ERROR:dbus.proxies:Introspect error on :1.175:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 211, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__ return self._connection.call_blocking(self._named_service, File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in call_blocking reply_message = self.send_message_with_reply_and_block( dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.175 was not provided by any .service files Ubuntu 20.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1948002/+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 1906120] Re: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal
I think this issue https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/486 might provide a fix. See also https://bugzilla.redhat.com/show_bug.cgi?id=1829178 where they mention the fix has been backported to 1.22.12. Any chance the Focal package could be upgraded to include that patch level? FWIW we've had the same issue as described on several machines (same network) when upgrading to Focal; installing the Groovy NM package (1.26.2) rebuilt from source for Focal seems to have fixed it. ** Bug watch added: Red Hat Bugzilla #1829178 https://bugzilla.redhat.com/show_bug.cgi?id=1829178 -- 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/1906120 Title: NetworkManager: error -111 disaptching events on DHCPv4 lease renewal Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04.1 running on armv7 (IFC6410) Occasional network interruption with the following message in journal: Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.3983] device[dabf59d236aff82b] (enp1s0): activation-stage: complete activate_stage5_ip_config_result_6,v6 (id 51751) Nov 28 12:03:16 drako NetworkManager[4094]: [1606582996.4026] device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, new-config=0x803e6140) Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8611] dhcp4 (enp1s0): error -111 dispatching events Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8614] dhcp4 (enp1s0): state changed extended -> fail Nov 28 12:03:18 drako NetworkManager[4094]: [1606582998.8622] device (enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds Nov 28 12:04:49 drako NetworkManager[4094]: [1606583089.4023] device (enp1s0): DHCPv4: grace period expired the ipv4 connection is then cut (the interface looses ipc4 address and the ipv4 routes are purged) until NetworkManager is restarted. The networkmanager-dispatcher.service doesn't indicate any error: Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher Service. Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new request (2 scripts) Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: CONNECTION_ID=Wired Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DEVICE_IP_IFACE=enp1s0 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ADDRESSES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP4_NUM_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: IP6_NUM_ROUTES=3 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_DHCP_LEASE_TIME=28800 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_EXPIRY=1606590245 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_HOST_NAME=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_INTERFACE_MTU=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_DOMAIN=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NIS_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_NTP_SERVERS=1 Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1 Nov 28
[Desktop-packages] [Bug 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff” is attached for hirsute(21.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5534867/+files/modemmanager_1-1.16.6-2~21.04.1-hirsute.debdiff ** Patch removed: "modemmanager_1-1.16.6-3-hirsute.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5530707/+files/modemmanager_1-1.16.6-3~hirsute.debdiff ** Patch removed: "modemmanager_1-1.16.6-3-focal.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5530706/+files/modemmanager_1-1.16.6-3-focal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
The .debdiff file “modemmanager_1-1.16.6-2~20.04.1-focal.debdiff” is attached for focal(20.04). The pre-built package : https://launchpad.net/~jerry-lee- tpe/+archive/ubuntu/packages/+packages ** Patch added: "modemmanager_1-1.16.6-2~20.04.1-focal.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1946096/+attachment/5534868/+files/modemmanager_1-1.16.6-2~20.04.1-focal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I confirm that problem persists with "current" ubuntu versions: Ubuntu 21.10 (Impish) - Wayland Gnome-shell 40.5-1ubutnu2 Ubuntu Dock (gnome-shell-extension) 70-ubuntu3 libwayland 1.19.0-2build1 xwayland 2:21.1.2-0ubuntu1 Linux 5.13.0-21 Thunderbird 1:91.2.0+build1-0ubuntu0.21.10.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Unknown Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
** Description changed: [Impact] + + The modem certification requires that different modem firmware is used for different network carrier. + This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other mo
[Desktop-packages] [Bug 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
Thanks Robie. I'll add more details to the description. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: New Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1948005] [NEW] Dell 6000 freeze and restart since october 19.
You have been subscribed to a public bug: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu -- Dell 6000 freeze and restart since october 19. https://bugs.launchpad.net/bugs/1948005 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1948008] [NEW] Copying and pasting to/from Nautilus does not work
Public bug reported: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome-shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Medium Status: New ** Affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Medium Status: New ** Affects: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Medium Status: New ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in gnome-shell-extension-desktop-icons source package in Hirsute: New Status in gnome-shell-extension-desktop-icons source package in Impish: New Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186
[Desktop-packages] [Bug 1948005] Re: Dell 6000 freeze and restart since october 19.
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948005 Title: Dell 6000 freeze and restart since october 19. Status in xorg package in Ubuntu: New Bug description: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1948005/+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 1946096] Re: Support manual firmware upgrading for Foxconn and Quectel modems.
Sponsored both the focal and hirsute versions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Support manual firmware upgrading for Foxconn and Quectel modems. Status in OEM Priority Project: In Progress Status in modemmanager package in Ubuntu: Fix Committed Bug description: [Impact] The modem certification requires that different modem firmware is used for different network carrier. This needs the firmware upgrading capability during the modem certification process. The modem manufacture vendors (Foxconn and Quectel) provided utilities to do modem's firmware upgrading manually.(LP#1943774, LP#1943780) These utilities are verified to be working when the recent versions(> v 1.18.2) of ModemManager are used with. To support manual firmware upgrading on the current Focal release which is using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2. The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 The firmware upgrading was verified using the patched ModemManager v 1.16.6 with the following 2 modems: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading utilities can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
I have reported another bug addressing the desktop-icons extension aspect of this issue: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/+bug/1948008 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: New Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1948010] [NEW] photo comment changed in "binary comment"
Public bug reported: I add a comment in several photo (F3 key) (image 1) and this comment is changed in the following string : binary comment (image 2) ! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: shotwell 0.30.11-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 14:06:06 2021 InstallationDate: Installed on 2020-04-10 (558 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: shotwell UpgradeStatus: Upgraded to impish on 2021-10-16 (5 days ago) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Attachment added: "Comment I write" https://bugs.launchpad.net/bugs/1948010/+attachment/5534891/+files/Capture%201.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1948010 Title: photo comment changed in "binary comment" Status in shotwell package in Ubuntu: New Bug description: I add a comment in several photo (F3 key) (image 1) and this comment is changed in the following string : binary comment (image 2) ! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: shotwell 0.30.11-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 14:06:06 2021 InstallationDate: Installed on 2020-04-10 (558 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: shotwell UpgradeStatus: Upgraded to impish on 2021-10-16 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1948010/+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 1945969] Re: Update Vala to 0.52.6 in Impish
** Changed in: libunity (Ubuntu Impish) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1945969 Title: Update Vala to 0.52.6 in Impish Status in libunity package in Ubuntu: Fix Released Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: Won't Fix Status in vala source package in Impish: Fix Released Bug description: The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+subscriptions -- Mailing list: https://launchpad.net/~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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
Running GNOME Control Center as root (not a good idea, I know), clearly gets the ModemManager connection to work. ** Attachment added: "GNOME Control Center (root)" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534919/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-24.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1946481] Re: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied"
** Attachment added: "Running as normal user" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+attachment/5534920/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202021-10-21%2015-19-34.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946481 Title: GNOME Control Center cannot connect to ModemManager with "org.freedesktop.DBus.Error.AccessDenied" Status in modemmanager package in Ubuntu: New Bug description: Upgraded my laptop (ThinkPad P14s Gen2) from 21.04 to 21.10, trying to get access to Modem Manager fails with: > error: couldn't create manager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied This was working on 21.04. STR: - Open Settings, go to "Network" OR - mmcli -m 0 Running mmcli as root workaround the problem, but I'm not able to use network applet to connect my modem. > $ id uid=1000(alex) gid=1000(alex) groupes=1000(alex),4(adm),6(disk),20(dialout),24(cdrom),27(sudo),30(dip),44(video),46(plugdev),107(lpadmin),124(sambashare),137(libvirtd),155(docker) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1946481/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
I don't think applying the change to hirsute would actually be useful given that we won't be respinning ISOs for hirsute and users would need to update the ubuntu-drivers-common package from the Live system to get the fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
** Tags removed: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1948048] [NEW] Unable to exit fullscreen
Public bug reported: Ubuntu 16.04 Intel i3 processor 64-bit Issue: After the rythmbox is set to fullscreen, I am unable to turn it back to normal window using any method possible. Also it prevents me to activate other programs or access the icons on the taskbar so that I can close it. After half an hour of trials I was somehow able to close the app by ending the process on the system monitor. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1948048 Title: Unable to exit fullscreen Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 16.04 Intel i3 processor 64-bit Issue: After the rythmbox is set to fullscreen, I am unable to turn it back to normal window using any method possible. Also it prevents me to activate other programs or access the icons on the taskbar so that I can close it. After half an hour of trials I was somehow able to close the app by ending the process on the system monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1948048/+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 1948046] [NEW] Flameshot won't paste on Chrome with Ozone enabled
You have been subscribed to a public bug: This is a unique problem to Ubuntu 21.04 and later and all derivatives (pop, mint etc). Since Chrome stable 91, when Ozone was enabled by default, unless Ozone is disabled in Chrome, flameshot (any version) cannot paste on sites such as github, gitlab or kami. The workaround has been so far to disable Ozone in Chrome flags, but since Chrome 95, Ozone cannot be disabled, which means that flameshot no longer works with Chrome and those (and potentially more) sites. Everything works fine in Fedora 33/34/35 and Manjaro 20+. Thank you. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Flameshot won't paste on Chrome with Ozone enabled https://bugs.launchpad.net/bugs/1948046 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- 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 1948046] Re: Flameshot won't paste on Chrome with Ozone enabled
** Package changed: ubuntu => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1948046 Title: Flameshot won't paste on Chrome with Ozone enabled Status in chromium-browser package in Ubuntu: New Bug description: This is a unique problem to Ubuntu 21.04 and later and all derivatives (pop, mint etc). Since Chrome stable 91, when Ozone was enabled by default, unless Ozone is disabled in Chrome, flameshot (any version) cannot paste on sites such as github, gitlab or kami. The workaround has been so far to disable Ozone in Chrome flags, but since Chrome 95, Ozone cannot be disabled, which means that flameshot no longer works with Chrome and those (and potentially more) sites. Everything works fine in Fedora 33/34/35 and Manjaro 20+. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1948046/+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 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
still experiencing this issue with plasma 5.23.1 and kernel 5.14.0 on amd 2500U cpu. switching "EnablePageFlip" on/off doesn't help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21 10:57:26 pc kernel: [ 9475.309388] do_syscall_64+0x57/0x190 Oct 21 10:57:26 pc kernel: [ 9475.309392] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Oct 21 10:57:26 pc kernel: [ 9475.309394] RIP: 0033:0x7f2a1bd0c67b Oct 21 10:57:26 pc kernel: [ 9475.309397] Code: 0f 1e fa 48 8b 05 15 28 0d
[Desktop-packages] [Bug 1888240] Re: Ubuntu Dock shows empty space for apps lacking a .desktop file
Replicated in our systems as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1888240 Title: Ubuntu Dock shows empty space for apps lacking a .desktop file Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Problem: On Ubuntu Desktop 20.04, everything latest, I have run into the inconvenience that when I'm running a GUI program without a freedesktop .desktop launcher, the Ubuntu Dock shows it as an empty space (since it has no icon of its own). Expected behavior: I would expect a generic placeholder / fallback icon to be shown for such applications, as an empty space at the bottom of the Dock is hard to find, and makes navigating applications frustrating. (In older versions of Ubuntu, a generic application icon was shown in such cases.) Steps to reproduce: 1. Open terminal 2. Run "xclock" from the terminal 3. Observe the blank space on Ubuntu Dock Some relevant package versions: gnome-shell: 3.36.3-1ubuntu1~20.04.2 gnome-shell-extension-ubuntu-dock: 68ubuntu1~20.04.1 yaru-theme-icon: 20.04.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1888240/+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 1948052] [NEW] some chromium browser pulldown menus corrupted in 21.10
You have been subscribed to a public bug: Several (but not all) of my Chromium Web Browser pulldown bookmarks menus are highly corrupted with flashing colors since using 21.10 Your first line refuses to accept Chromium, saying that it does not exist in Ubuntu. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- some chromium browser pulldown menus corrupted in 21.10 https://bugs.launchpad.net/bugs/1948052 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- 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 1948052] Re: some chromium browser pulldown menus corrupted in 21.10
** Package changed: ubuntu => chromium-browser (Ubuntu) ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1948052 Title: some chromium browser pulldown menus corrupted in 21.10 Status in chromium-browser package in Ubuntu: New Bug description: Several (but not all) of my Chromium Web Browser pulldown bookmarks menus are highly corrupted with flashing colors since using 21.10 Your first line refuses to accept Chromium, saying that it does not exist in Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1948052/+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 1946599]
*** Bug 1732582 has been marked as a duplicate of this bug. *** -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1946599]
(In reply to Darkspirit from comment #1) > $ sudo snap remove firefox; sudo snap install firefox --channel=latest/beta; > snap run firefox https://webglsamples.org/aquarium/aquarium.html > > firefox (beta) 93.0b9-1 from Mozilla✓ installed > > broken Debian Testing, Gnome Wayland, Intel sudo snap remove firefox; sudo snap install firefox --channel=latest/beta EGL/Wayland works: snap run firefox https://webglsamples.org/aquarium/aquarium.html EGL/Xwayland works: DISABLE_WAYLAND=1 snap run firefox https://webglsamples.org/aquarium/aquarium.html -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1947920] Re: tracker-miner-f 100% CPU and slows system down
No problems all done: https://gitlab.gnome.org/GNOME/tracker/-/issues/334 ** Bug watch added: gitlab.gnome.org/GNOME/tracker/-/issues #334 https://gitlab.gnome.org/GNOME/tracker/-/issues/334 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1947920 Title: tracker-miner-f 100% CPU and slows system down Status in tracker package in Ubuntu: New Bug description: tracker-miner-f has been using 100% CPU and my system making it almost unresponsive. This happens around once a month or so when I boot up. It sometimes lasts for a number of days (or a number of resets) until the system becomes responsive again. The command "tracker status" always shows the same thing: "Estimated less than one second left" although it appears that everything is already indexed because the file and folder counts do not increase. Even so tracker-miner-f is still showing 100% CPU inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101154 files, 16046 folders Remaining space on database partition: 160.5 GB (64.11%) Data is still being indexed: Estimated less than one second left inspiron@Inspiron-7348:~$ tracker status Currently indexed: 101155 files, 16045 folders Remaining space on database partition: 161.1 GB (64.31%) Data is still being indexed: Estimated 01h 19m 03s left ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tracker 2.3.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:25:58 2021 InstallationDate: Installed on 2021-06-28 (114 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) UPDATE I have now reset the tracker and it seems to be going through and indexing everything again. tracker reset --hard Now tracker-miner-f has re-indexed everything and tracker-extract and tracker-store are running. UPDATE 2 The tracker reset completed indexing everything and the went into idle state. However when rebooting, tracker-miner-f went to 100% CPU once again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1947920/+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 1948339] Re: Logon screen can be bypassed using various shortcuts
Your daughter does good work :) Thanks ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1948339 Title: Logon screen can be bypassed using various shortcuts Status in Ubuntu MATE: New Status in arctica-greeter package in Ubuntu: New Status in lightdm package in Ubuntu: New Status in mate-settings-daemon package in Ubuntu: New Bug description: Hi, my little daughter discovered a logon screen bypass in Ubuntu Mate 21.10 after hitting the keyboard for a while. It turns out that several keyboard shortcuts are allowed while Ubuntu Mate is locked (arctica-greeter): - Mod4 + S (mate-search-tool) - Mod4 + E (Open Caja / File Explorer) - CTRL + Shift + Esc (mate-system-monitor) - PRNT (Screenshot) All of the mentioned shortcuts could be used to spawn a file explorer (Caja) or various other binaries as user "lightdm", who owns the logon screen. Although an interactive terminal like mate-terminal, xterm, lxterm etc. could not be opened directly, there are various options to run commands as the lightdm user, for example by creating a shell script using "caja", and execute it directly using the GUI. I've attached Proof-of-Concept GIFs for all shortcuts mentioned above. There might be additional shortcuts that could be used to achieve the same, however I'm not aware about every shortcut that is configured, but I suppose that the root cause is located somewhere in arctica- greeter, rather than within every single binary launched by shortcuts. The bug was reproduced on a fresh installation of Ubuntu Mate 21.10. I haven't tested other versions of Ubuntu Mate yet. Please find additional version details below: $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu4 Candidate: 1.30.0-0ubuntu4 Version table: *** 1.30.0-0ubuntu4 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy arctica-greeter arctica-greeter: Installed: 0.99.1.5-2nmu1 Candidate: 0.99.1.5-2nmu1 Version table: *** 0.99.1.5-2nmu1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status Thanks, Basti To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1948339/+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 1948355] [NEW] Firefox settings font size dropdown flashes, hard to select
Public bug reported: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. ** Affects: firefox (Ubuntu) Importance: Undecided Status: 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/1948355 Title: Firefox settings font size dropdown flashes, hard to select Status in firefox package in Ubuntu: New Bug description: Go to settings, then font, and try to change the font size. The dropdown flashes and disappears, and is very difficult to select. Happens both on the main screen and the "advanced.." screen for all size selectors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948355/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
** Tags removed: disco ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: New Status in gnome-shell-extension-desktop-icons source package in Focal: New Status in nautilus source package in Focal: New Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1948356] [NEW] Firefox 93.0 tabs are not remembered across sessions
Public bug reported: If I close Firefox with a bunch of tabs, then open again, the tabs are gone. I get a list of empty tabs without any actual link to them. Only the last visited site is actually filled with the URL. Up until now Firefox always remembers and restores the list of tabs. I am using Tree Style Tab, but I believe it uses the regular tab list for itself. Ubuntu 21.10 firefox 93.0-1 ** Affects: firefox (Ubuntu) Importance: Undecided Status: 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/1948356 Title: Firefox 93.0 tabs are not remembered across sessions Status in firefox package in Ubuntu: New Bug description: If I close Firefox with a bunch of tabs, then open again, the tabs are gone. I get a list of empty tabs without any actual link to them. Only the last visited site is actually filled with the URL. Up until now Firefox always remembers and restores the list of tabs. I am using Tree Style Tab, but I believe it uses the regular tab list for itself. Ubuntu 21.10 firefox 93.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1948356/+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 1948008] Re: Copying and pasting to/from Nautilus does not work
Bug 1843588 already has a task for gnome-shell-extension-desktop-icons so can you clarify why this bug is required? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons source package in Hirsute: Won't Fix Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1948008/+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 1948008] Re: Copying and pasting to/from Nautilus does not work
Also gnome-shell-extension-desktop-icons is not used in hirsute and impish. They use gnome-shell-extension-desktop-icons-ng instead. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: New => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Status: New => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons source package in Hirsute: Won't Fix Status in gnome-shell-extension-desktop-icons source package in Impish: Invalid Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1948008/+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 1948005] Re: Dell 6000 dock freeze and restart since october 19.
** Summary changed: - Dell 6000 freeze and restart since october 19. + Dell 6000 dock freeze and restart since october 19. ** Package changed: xorg (Ubuntu) => linux-oem-5.10 (Ubuntu) ** Tags added: regression-update ** Tags added: displaylink evdi ** Summary changed: - Dell 6000 dock freeze and restart since october 19. + Dell 6000 dock freeze and restart since October 19. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1948005 Title: Dell 6000 dock freeze and restart since October 19. Status in linux-oem-5.10 package in Ubuntu: New Bug description: Ramdomly my external display (conected via HDMI over a dell 6000 displaylink port) stop working, gone black, and then restart. Buy I notice that all devices conected to dell 6000 stop working. It happens since october 19 ubuntu auto update. I need this continue working as it was before that update. Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1050.52-oem 5.10.68 Uname: Linux 5.10.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 21 08:16:15 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: evdi, 1.9.1, 5.10.0-1049-oem, x86_64: installed evdi, 1.9.1, 5.10.0-1050-oem, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0a29] InstallationDate: Installed on 2021-08-18 (63 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. Vostro 3401 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1050-oem root=UUID=d63f71be-78d3-412a-95ce-c1fd7fc0b432 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2021 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0790WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd05/31/2021:br1.6:svnDellInc.:pnVostro3401:pvr:sku0A29:rvnDellInc.:rn0790WT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3401 dmi.product.sku: 0A29 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1948005/+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 1948362] [NEW] UnboundLocalError: local variable 't' referenced before assignment
Public bug reported:
```
Traceback (most recent call last):
File "/usr/bin/prime-select", line 458, in
switcher.enable_profile(arg)
File "/usr/bin/prime-select", line 223, in enable_profile
if not self._has_integrated_gpu():
File "/usr/bin/prime-select", line 198, in _has_integrated_gpu
if t.find('8086') != -1 or t.lower().find('1002') != -1:
UnboundLocalError: local variable 't' referenced before assignment
```
at file `prime-select`, line 198
https://git.launchpad.net/ubuntu/+source/nvidia-prime/tree/prime-
select#n198
that `t` should be `vendor` I think. :)
** Affects: nvidia-prime (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1948362
Title:
UnboundLocalError: local variable 't' referenced before assignment
Status in nvidia-prime package in Ubuntu:
New
Bug description:
```
Traceback (most recent call last):
File "/usr/bin/prime-select", line 458, in
switcher.enable_profile(arg)
File "/usr/bin/prime-select", line 223, in enable_profile
if not self._has_integrated_gpu():
File "/usr/bin/prime-select", line 198, in _has_integrated_gpu
if t.find('8086') != -1 or t.lower().find('1002') != -1:
UnboundLocalError: local variable 't' referenced before assignment
```
at file `prime-select`, line 198
https://git.launchpad.net/ubuntu/+source/nvidia-prime/tree/prime-
select#n198
that `t` should be `vendor` I think. :)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1948362/+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 1948364] [NEW] Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot
Public bug reported: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl log about static IP" https://bugs.launchpad.net/bugs/1948364/+attachment/5534988/+files/Static_IP_loss_2021-10-22_10-27-30.log -- 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/1948364 Title: Static IP set in /etc/network/interfaces sometimes doesn't set properly after reboot Status in network-manager package in Ubuntu: New Bug description: I use ubuntu20.04 and set static IP 192.168.11.22 in /etc/network/interfaces. Most time it could work but sometimes the IP changed to 192.168.11.105, which same to be a DHCP IP. I checked the syslog and journalctl, find that eth0 same to disconnect and be re- configured by dhcilent.: Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0490] device (eth0): link disconnected (calling deferred action) Oct 22 10:10:03 sv-host NetworkManager[502]: [1634868603.0498] device (eth0): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40] But I don't know which lead eth0 disconnect. Why eth0 doesn't get static IP but DHCP IP when it reconnected? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948364/+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 1947257] Re: Partial profile loss on upgrade from 21.04 to 21.10
I upgraded from 21.04 to 21.10. Other (non-sudo) users of the computer reported that their Firefox profiles were lost. I uninstalled the snap firefox, and installed deb firefox via apt. Their profiles "came back". I guess the snap firefox looks for profiles in a different location, and the profiles aren't transferred from the old deb-firefox location to the snap-firefox-expected location. It looks as though this transition to snap firefox has been done badly. -- 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/1947257 Title: Partial profile loss on upgrade from 21.04 to 21.10 Status in firefox package in Ubuntu: Incomplete Bug description: In the upgrade from 21.04 to 21.10 I noticed it had updated firefox. When restarting some of my profile was kept (themes, addons, etc) but I've noticed my primary window of 50+ tabs was lost. It opened 3 other windows correctly. I tried to find it via "recently closed tabs/windows" but it's not showing up. I have also confirmed there are no duplicate profiles. Silly me assumed it was done correctly and when the upgrade process offered to remove old packages I did so I can't seem to retrieve the old profile. Additional information: lsb_release -rd: Description: Ubuntu 21.10 Release: 21.10 snap package information: snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-21.10 refresh-date: today at 09:00 AEST channels: latest/stable:93.0-1 2021-10-08 (631) 157MB - latest/candidate: 93.0-1 2021-09-28 (631) 157MB - latest/beta: 94.0b5-1 2021-10-13 (650) 157MB - latest/edge: ↑ esr/stable: 78.15.0esr-1 2021-10-04 (637) 148MB - esr/candidate:91.2.0esr-1 2021-09-29 (634) 160MB - esr/beta: ↑ esr/edge: ↑ installed: 93.0-1 (631) 157MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947257/+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 1905054] Re: Firefox 83 Breaks WebGL
I upgraded my PC from 21.04 to 21.10. I found that WebGL doesn't work in the snap firefox that 21.10 installed. I uninstalled the snap firefox and installed the deb firefox via apt. That fixed the WebGL issue. -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+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
