[Desktop-packages] [Bug 2003410] Re: freeze after lead is closest, have black screen without any message, just after hard reset it work
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/2003410 Title: freeze after lead is closest, have black screen without any message, just after hard reset it work Status in gnome-shell package in Ubuntu: Expired Bug description: freeze after lead is closest, have black screen without any message, just after hard reset it work ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 20 10:29:14 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-19 (1157 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-11 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2003410/+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 1318669] Re: On move use same heuristics as Windows Explorer if NTFS inherit option is set
This applies to all versions up to 22.10. ** Changed in: nemo (Ubuntu) Status: Invalid => New ** Changed in: glib2.0 (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1318669 Title: On move use same heuristics as Windows Explorer if NTFS inherit option is set Status in glib2.0 package in Ubuntu: New Status in nemo package in Ubuntu: New Bug description: When moving a file or folder, which inherits its permissions from its parent folder, with original Windows Explorer within same NTFS file system, after the move the object always inherits its permissions from its destination parent folder in contrast to command line move, which never changes owner and permissions. IMO, Nautilus and also Nemo should behave same, if ntfs-3g "inherit" mount option is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1318669/+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 2007743] Re: intramfs Failed: ZSTD-compressed data
now added to this bug: @Andy Whitcroft (~apw) @Andy Whitcroft (~apw2) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Triaged Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2007743] Re: intramfs Failed: ZSTD-compressed data
@Julian Andres Klode (~juliank) what is the current status of progress here? Does anyone working on this? Or should I wait for 23.04.X LTS release and cross my fingers? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2007743 Title: intramfs Failed: ZSTD-compressed data Status in grub2-unsigned package in Ubuntu: Triaged Bug description: The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts! Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package # lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 # dpkg -l | grep init ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64Standalone shell setup for initramfs ii gnome-initial-setup42.0.1-1ubuntu2.3 amd64Initial GNOME system setup helper ii init 1.62 amd64metapackage ensuring an init system is installed ii init-system-helpers1.62 all helper tools for all init systems ii initramfs-tools0.140ubuntu13.1 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu13.1 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.6.1-1ubuntu1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.10-4 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality ii ncurses-base 6.3-2 all basic terminal type definitions ii sysvinit-utils 3.01-1ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu4 amd64X server initialisation tool # dpkg -l | grep zfs -> brings no information here # zfs list -> zfs is not installed here if you need more system-infos to solve this Bug, please let me know! The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up. Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2007743/+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 2012430] Re: attribute breaks dashes
This issue has been a pain in the you know what, for quite some time now. I was not sure if it is MediaWiki or Firefox. Since I only use Ubuntu on all my clients, they were consistently broken. Over the years I have gotten used to working with invisible dashes. It will be really cool to get a fix for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2012430 Title: attribute breaks dashes Status in firefox package in Ubuntu: Confirmed Bug description: The attached HTML file should be rendered as two lines of text, one with dashes between the words and one with spaces. However, Firefox renders the file with no dashes whatsoever. Instead of dashes, it shows double-width spaces. The HTML renders correctly if lang="de-x-formal" attribute is changed to lang="de". Please note that de-x-formal is a valid language code, as verified with http://schneegans.de/lv/ and it is found in the HTML generated by MediaWiki when the language is set to de-formal. I also noticed that the extra wide spaces Firefox incorrectly shows instead of dashes are in the ori1Uni font while the regular letters are in DejaVu Serif. With lang="de", everything is in DejaVu Serif, including dashes which render correctly. This problem does not occur with Chromium on Ubuntu, nor with Firefox on Debian, nor Firefox on Windows. Ubuntu version: Ubuntu 22.04.2 LTS Firefox version: firefox 111.0-2 from snap Thank you very much for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2012430/+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 2012430] Re: attribute breaks dashes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/2012430 Title: attribute breaks dashes Status in firefox package in Ubuntu: Confirmed Bug description: The attached HTML file should be rendered as two lines of text, one with dashes between the words and one with spaces. However, Firefox renders the file with no dashes whatsoever. Instead of dashes, it shows double-width spaces. The HTML renders correctly if lang="de-x-formal" attribute is changed to lang="de". Please note that de-x-formal is a valid language code, as verified with http://schneegans.de/lv/ and it is found in the HTML generated by MediaWiki when the language is set to de-formal. I also noticed that the extra wide spaces Firefox incorrectly shows instead of dashes are in the ori1Uni font while the regular letters are in DejaVu Serif. With lang="de", everything is in DejaVu Serif, including dashes which render correctly. This problem does not occur with Chromium on Ubuntu, nor with Firefox on Debian, nor Firefox on Windows. Ubuntu version: Ubuntu 22.04.2 LTS Firefox version: firefox 111.0-2 from snap Thank you very much for looking into this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2012430/+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 2007760] Re: gjs-console crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1986455 *** https://bugs.launchpad.net/bugs/1986455 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2007760 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() Status in gjs package in Ubuntu: Confirmed Bug description: I just using the system normally ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gjs 1.74.1-1 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 18 14:01:07 2023 ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2023-02-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters --gapplication-service Signal: 6 SourcePackage: gjs StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0 Title: gjs-console crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to lunar on 2023-02-18 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2007760/+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 321932] Re: Ghostscript does not render when ttf-mscorefonts-installer is installed
For anyone looking for a solution to the problem. I've fixed it by creating the following file: /etc/ghostscript/cidfmap.d/20msfonts.conf /Arial-BoldItalicMT << /FileType /TrueType /Path (/usr/share/fonts/truetype/msttcorefonts/arialbi.ttf) /SubfontID 0 /CSI [(Identity) 0] >> ; /Arial-BoldMT << /FileType /TrueType /Path (/usr/share/fonts/truetype/msttcorefonts/arialbd.ttf) /SubfontID 0 /CSI [(Identity) 0] >> ; /Arial-ItalicMT << /FileType /TrueType /Path (/usr/share/fonts/truetype/msttcorefonts/ariali.ttf) /SubfontID 0 /CSI [(Identity) 0] >> ; /ArialMT << /FileType /TrueType /Path (/usr/share/fonts/truetype/msttcorefonts/Arial.ttf) /SubfontID 0 /CSI [(Identity) 0] >> ; /Arial-Black << /FileType /TrueType /Path (/usr/share/fonts/truetype/msttcorefonts/ariblk.ttf) /SubfontID 0 /CSI [(Identity) 0] >> ; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/321932 Title: Ghostscript does not render when ttf-mscorefonts-installer is installed Status in defoma package in Ubuntu: Invalid Status in ghostscript package in Ubuntu: Fix Released Status in msttcorefonts package in Ubuntu: Triaged Status in defoma source package in Lucid: Invalid Status in ghostscript source package in Lucid: Won't Fix Status in msttcorefonts source package in Lucid: Invalid Status in Baltix: New Bug description: Binary package hint: ghostscript GPL Ghostscript SVN PRE-RELEASE 8.64 on ubuntu jaunty does'nt load anymore ps files. ghostscript: Installed: 8.64.dfsg.1~svn9377-0ubuntu1 Candidate: 8.64.dfsg.1~svn9377-0ubuntu1 Version table: *** 8.64.dfsg.1~svn9377-0ubuntu1 0 500 http://it.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status ubuntu jaunty x86_64 Description: Ubuntu jaunty (development branch) Release: 9.04 evince and any other frontend that rely on gs for postscript rendering do not work anymore. No printing is possible on non postscript printers. launching the interpreter from terminal (for instance using the ps2pdf program) gives this stack: Error: /invalidfont in /findfont Operand stack: iso1dict fCourier --nostringval-- Courier Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1862 1 3 %oparray_pop 1861 1 3 %oparray_pop 1845 1 3 %oparray_pop 1739 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- 1820 4 5 %oparray_pop Dictionary stack: --dict:1151/1684(ro)(G)-- --dict:0/20(G)-- --dict:70/200(L)-- --dict:59/200(L)-- --dict:0/8(L)-- Current allocation mode is local Last OS error: 2 Current file position is 16162 GPL Ghostscript SVN PRE-RELEASE 8.64: Unrecoverable error, exit code 1 Input is simple ascii fortran source code transformed to ps using a2ps -o file.ps file.F gs 8.63 worked ok, 8.64 gives error and is unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/defoma/+bug/321932/+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 1973175] Re: Window dimensions are changed and appears behind the dock
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1973175 Title: Window dimensions are changed and appears behind the dock Status in gnome-shell package in Ubuntu: Confirmed Bug description: After using the session for a while with a normal workflow like switching opened windows etc. Some app windows's dimensions are changed automatically from the left side and appears behind the dock as shown in the screenshot. To correct it, the window must be resized and then maximized to return back to normal dimension for the current screen. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu May 12 14:20:21 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (97 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973175/+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 1971196] Re: Applications automatically expand and go under the dock
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1971196 Title: Applications automatically expand and go under the dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 Screen resolution -> 1366*768 (16:9) Refresh Rate -> 60.11 Hz I have the following settings for my dock: Auto hide -> Off Panel Mode -> Off Icon Size -> 32 Show on -> Built in display Position on screen -> right Now, sometimes some applications, which are not active/current windows, expand and go under the dock. If I detach them from the top and reattach them, then again they stick to the dock's border, but may again go under it sometime later. This behaviour is quite unpredictable, and I don't know how someone would reproduce it. Please see the attached image for further clarification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1971196/+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 1962638] Re: Ubuntu dock overlaps programs after resume from screen blank
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1962638 Title: Ubuntu dock overlaps programs after resume from screen blank Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu-desktop: Installed: 1.472 Candidate: 1.472 Version table: *** 1.472 500 500 http://au.archive.ubuntu.com/ubuntu impish/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen - The Ubuntu dock should be displayed next to a program after resume from screen blank. 4) What happened instead - The Ubuntu dock overlaps the program when resuming from screen blank. I have to click "Restore Down" and then "Maximize" so that the dock is displayed next to the program, rather than over the top of it. It doesn't happen on every resume from screen blank, it happens randomly and it happens on different programs. I have "Auto-hide the Dock" disabled. Please see screenshot for an example. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1962638/+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 1985968] Re: Maximized windows often end up behind the dock on session unlock
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1985968 Title: Maximized windows often end up behind the dock on session unlock Status in gnome-shell package in Ubuntu: Confirmed Bug description: Using the default Ubuntu 22.04 desktop on Wayland, with little tweaks. I have a bunch of maximized windows, two screens extended horizontally. Often when I unlock the session, one of the maximized windows will be maximized behind the dock. I have to un- and maximize them again to bring them back. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 12 12:51:09 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-29 (104 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1985968/+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 1970245] Re: Windows not respecting dock boundary
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1970245 Title: Windows not respecting dock boundary Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Context: Fresh installation of 22.04 amd64 on Dell XPS13, running on Intel, Wayland session. Behavior observed: Application windows often stop respecting the boundary of the dock and suddenly invade its space (since the dock is slightly transparent I can see which application it is that is doing so, but haven't seen a pattern yet). The scenario is that application windows are maximized, thus the dock should be the boundary on one of the four sides of an opened application depending on where the dock is placed. Alternatives tried: Moved dock from left to bottom, no change. Why is this a problem: Applications in a maximized state should not be partially hidden by a system UI element until explicitly configured as such (e.g. with a UI config option that the dock is "in the front" and apps in the back). Sorry for the non technical description, I hope it helps to narrow it down. It is one of the hand full of annoying little things noticed upon launch day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1970245/+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 1988576] Re: Maximized window goes behind the launcher
*** This bug is a duplicate of bug 1961508 *** https://bugs.launchpad.net/bugs/1961508 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1988576 Title: Maximized window goes behind the launcher Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: Launch Libreoffice Writer Maximize Libreoffice Writer's window Launch Files Maximize Files's window => Your screen is currently like Capture 1 Lock the screen (like shown in Capture 2) Unlock the screen by typing the user's password => In the following, do no release key unless you are told to. Press Alt (without releasing) One second later, press Tab and release Tab One second later, release Alt => Your screen is currently like Capture 3 What I expected to happen: I expected to see LibreOffice Writer's window maximized but not behind the launcher. What happened instead LibreOffice Writer's window is maximized and is behind the launcher. nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1988576/+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 2012788] Re: Entering Unicode characters with code points broken
Happens in both x11 and wayland sessions. -- 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/2012788 Title: Entering Unicode characters with code points broken Status in gnome-shell package in Ubuntu: New Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012788/+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 2012788] [NEW] Entering Unicode characters with code points broken
Public bug reported: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. ** Affects: gnome-shell (Ubuntu) Importance: High Status: New ** Tags: lunar regression-release rls-ll-incoming -- 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/2012788 Title: Entering Unicode characters with code points broken Status in gnome-shell package in Ubuntu: New Bug description: On an updated lunar, following this instruction: https://help.ubuntu.com/stable/ubuntu-help/tips- specialchars.html#ctrlshiftu no longer works. If I press for instance Ctrl+Shift+U followed by 2014 I see u2014 (underlined) on the screen. But it's not replaced with the expected character (in this case an Em Dash) when I confirm with Space or Enter — it just disappears. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2012788/+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 2011806] Re: [lunar] Snaps don't launch due to cgroup issue
Same issue here, I have never seen any snaps opening from the dash (both Firefox and Brave) and they both put out a cgroup error in the syslog. Starting from terminal works and without the cgroup error in the log. Maybe also noticable, I see snap core20 and core22 both installed and cannot remove core20 because it is being used by firefox (but not brave which also does not start). The list of snaps installed: Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base brave 1.49.128 218latest/stable brave - core2020230308 1852 latest/stable canonical✓ base core2220230316 583latest/stable canonical✓ base firefox 111.0-2 2453 latest/stable/… mozilla✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - kde-frameworks-5-96-qt-5-15-5-core20 5.96.07 latest/stable kde✓- keepassxc 2.7.4 1645 latest/stable keepassxreboot - libreoffice 7.5.1.2 270latest/stable canonical✓ - snap-store41.3-76-g2e8f3b0 935latest/stable/… canonical✓ - snapd 2.58.318596 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 71 latest/stable/… canonical✓ - -- 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/2011806 Title: [lunar] Snaps don't launch due to cgroup issue Status in gnome-shell package in Ubuntu: In Progress Bug description: Hi, Lunar up to date, Intel+Nvidia GPUs, Ubuntu Wayland or X11 session, hybrid or discrete graphics. If I click on a snap dash icon, nothing happens. Tested with Thunderbird, Firefox, Shortwave... (VS Code seems ok, maybe due to classic confinment?) I can launch without issue Chrome (deb), Synaptic, GNOME apps, etc. Recent updates included gnome-shell and libadwaita. --- I get this type of log for all problematic snaps: /user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome- shortwave_shortwave-11885.scope is not a snap cgroup --- Context: $ snap --version snap2.58.3+23.04ubuntu1 snapd 2.58.3+23.04ubuntu1 series 16 ubuntu 23.04 kernel 6.1.0-16-generic $ snap list Nom Version Révision Suivi Éditeur Notes bare 1.0 5 latest/stable canonical✓base code ee2b180d122 latest/stable vscode✓ classic core 16-2.58.2 14784 latest/stable canonical✓core core18202303082714 latest/stable canonical✓base core20202302071828 latest/stable canonical✓base core2220230210522 latest/stable canonical✓base firefox 111.0-2 2432 latest/candidate mozilla✓ - gimp 2.10.30 393 latest/stable snapcrafters - gnome-3-28-1804 3.28.0-19-g98f9e67.98f9e67 161 latest/stable canonical✓- gnome-3-38-2004 0+git.6f39565 119 latest/stable canonical✓- gnome-42-2204 0+git.09673a5 65 latest/stable canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- gtk-theme-pocillo 0.14.4.15 latest/stable ubuntubudgie - gtk-theme-qogirbudgie 22.04.1 8 latest/stable ubuntubudgie - gtk2-common-themes0.1 13 latest/stable canonical✓- hunspell-dictionaries-1-7-20041.7-20.04+pkg-6fd6 2 latest/stable brlin - kde-frameworks-5-91-qt-5-15-3-core20 5.91.0 1 latest/stable kde✓ - kde-frameworks-5-99-qt-5-15-7-core20 5.99.0 15
[Desktop-packages] [Bug 2003259] Re: [MIR] libcupsfilters libppd cups-browsed
Thanks Mark, promoting libppd now! $ ./change-override -c main -t libppd Override component to main libppd 2:2.0~b4-0ubuntu3 in lunar: universe/libs -> main Override [y|N]? y 1 publication overridden. $ ./change-override -c main libppd-dev libppd2 libppd2-common Override component to main libppd-dev 2:2.0~b4-0ubuntu3 in lunar amd64: universe/libdevel/optional/100% -> main libppd-dev 2:2.0~b4-0ubuntu3 in lunar arm64: universe/libdevel/optional/100% -> main libppd-dev 2:2.0~b4-0ubuntu3 in lunar armhf: universe/libdevel/optional/100% -> main libppd-dev 2:2.0~b4-0ubuntu3 in lunar ppc64el: universe/libdevel/optional/100% -> main libppd-dev 2:2.0~b4-0ubuntu3 in lunar riscv64: universe/libdevel/optional/100% -> main libppd-dev 2:2.0~b4-0ubuntu3 in lunar s390x: universe/libdevel/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar amd64: universe/libs/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar arm64: universe/libs/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar armhf: universe/libs/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar ppc64el: universe/libs/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar riscv64: universe/libs/optional/100% -> main libppd2 2:2.0~b4-0ubuntu3 in lunar s390x: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar amd64: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar arm64: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar armhf: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar i386: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar ppc64el: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar riscv64: universe/libs/optional/100% -> main libppd2-common 2:2.0~b4-0ubuntu3 in lunar s390x: universe/libs/optional/100% -> main Override [y|N]? y 19 publications overridden. ** Changed in: libppd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2003259 Title: [MIR] libcupsfilters libppd cups-browsed Status in cups-browsed package in Ubuntu: Fix Released Status in libcupsfilters package in Ubuntu: Fix Released Status in libppd package in Ubuntu: Fix Released Bug description: == Summary = Source packages to be promoted to Main: - libcupsfilters - libppd - cups-browsed Binary packages to be promoted to Main: - libcupsfilters2 - libcupsfilters2-common - libppd-dev - libppd2 - libppd2-common - ppdc No source packages and no binary packages which are in Main should get demoted to Universe. == Overview Due to a major change in the printing architecture [1] the cups-filters upstream project at OpenPrinting got split into 5 components [2]: - libcupsfilters - libppd - cups-filters - braille-printer-app - cups-browsed [1] https://openprinting.github.io/current/#the-new-architecture-for-printing-and-scanning [2] https://openprinting.github.io/cups-filters-Second-Generation-First-Beta-Release/ To reflect this in the Debian/Ubuntu packaging also the cups-filters source package there is getting split, rendering 3 new source packages (+) and therefore we need this MIR: Binaries: Source BEFORE (1.x) Source AFTER (2.x) - cups-browsed cups-filters cups-browsed + cups-filters cups-filters cups-filters cups-filters-core-drivers cups-filters cups-filters libcupsfilters-dev cups-filters libcupsfilters + libcupsfilters1 X cups-filters Replaced by libcupsfilters2 * libcupsfilters2 + libcupsfilters + (NEW) libcupsfilters2-common +libcupsfilters + (NEW) libfontembed-dev X cups-filters REMOVED ** libfontembed X cups-filters REMOVED ** libppd-dev +libppd + (NEW) *** libppd2 + libppd + (NEW) *** libppd2-common +libppd + (NEW) *** ppdc + libppd + (NEW) *** * : libcupsfilters has new API generation/SONAME 1 -> 2 ** : libfontembed code folded into libcupsfilters, API removed, no other package is using it. ***: libppd contains all PPD-supporting code of CUPS, as in CUPS 3.x this code will get removed. libppd is for legacy-retro-fitting of classic CUPS drivers with PPD files. Code comes from CUPS source: cups/ppd*.[ch], scheduler/cups-driverd.cxx, ppdc/* X: Binary package getting REMOVE
[Desktop-packages] [Bug 2011770] Re: [gsd-rfkill] WwanEnabled never get synced
** Changed in: oem-priority Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2011770 Title: [gsd-rfkill] WwanEnabled never get synced Status in OEM Priority Project: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Jammy: Fix Committed Status in gnome-settings-daemon source package in Kinetic: Fix Committed Bug description: [ Impact ] * Sometimes on devices with WWAN card, whenever user presses the wireless function key (Fn+F8) or turn on the airplane mode radio button in Settings, the airplane mode will not be enabled, and the airplane mode icon is not shown in the status bar. * There is a unmerged upstream merge request that delivers the fix: https://gitlab.gnome.org/GNOME/gnome-settings- daemon/-/merge_requests/310 It works perfectly well on several Lenovo laptops with WWAN cards. The root causes is that the value of "WwanEnabled" under "org.freedesktop.NetworkManager" is not synced correctly, gsd-rfkill should listen to "g-properties-changed" instead of "g-signal" now. [ Test Plan ] 1. Find a machine which has WWAN card. 2. Boot the machine, and run rfkill list to see if WWAN is unblocked. if not use rfkill to unblock the WWAN, and reboot. 3. Press the wireless media key (Fn+F8) or turn on the airplane mode radio button in Settings. 4. The airplane mode should be enabled, but actually not. [ Where problems could occur ] * When user is using a very low version network-manager (< 1.20) that still broadcasting DBUS "PropertiesChanged" events on "g-signal" instead of the concurrent "g-properties-changed", the airplane mode will sometimes not be able to enable. [1]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/853 [2]: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6fb917178aa19c61e909957f5146aa4565e0cb2f [ Other Info ] 1. About Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Kernel: 6.1.0-1007-oem 2. The version of packages: gnome-settings-daemon: Installed: 42.1-1ubuntu2.1 network-manager: Installed: 1.36.6-0ubuntu2 3. Expect: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is called, and manager->wwan_enabled is set to the correct value. 4. Actual: The function nm_signal(plugins/rfkill/gsd-rfkill-manager.c) is never called, so manager->wwan_enabled is not synced, If machine has WWAN device(s), and the initial value of manager->wwan_enabled is true, it will never be able to switch to airplane mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2011770/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
I have this issue on Xubuntu 22.04.2 LTS, amdgpu and X11.
--
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/2004532
Title:
Hardware acceleration broken for amdgpu/mesa in snap
Status in chromium-browser package in Ubuntu:
Triaged
Status in firefox package in Ubuntu:
Confirmed
Status in snapd package in Ubuntu:
Confirmed
Bug description:
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
Two snap packages which are now unusable are Mozilla Firefox and
Chromium browsers. Both display animated speckled color garbage inside
their windows, overlayed with the correct image. Disabling hardware
acceleration in the settings for the snap version of Firefox fixed it.
Also, Firefox version installed from the original Mozilla tarball into
/opt/ works just fine with the acceleration enabled on the same
system, as well as glmark2 benchmark. Looks like the issue is only
affecting snap packages.
$ snap list firefox chromium
Name Version Rev Tracking Publisher Notes
chromium 109.0.5414.119 2295 latest/stable canonical✓ -
firefox 109.0.1-1 2311 latest/stable mozilla✓-
$ dpkg -l snapd|grep ^ii
ii snapd 2.58+22.10 amd64Daemon and tooling that enable
snap packages
$ dpkg -l mesa\* | grep ^ii
ii mesa-utils8.5.0-1 amd64Miscellaneous
Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous
Mesa utilities -- native applications
ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API
video acceleration drivers
ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video
acceleration drivers
ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan
graphics drivers
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename: kinetic
$ uname -a
Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Feb 1 22:55:48 2023
InstallationDate: Installed on 2020-08-02 (913 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snap
UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480
640x480 640x480 640x480
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2020-08-02 (914 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS System Product Name
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
(772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458})
Snap.ChromiumVersion:
up
