[Desktop-packages] [Bug 2085089] Re: Account server settings: XML Parsing Error: undefined entity
It's fixed with Thunderbird 128.4.0esr (the last version) installed using snap. -- 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/2085089 Title: Account server settings: XML Parsing Error: undefined entity Status in thunderbird package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 24.04 from 23.10 I can't access my email server settings in thunderbird on any of my email mailbox with following error: error:XML Parsing Error: undefined entity Location: chrome://messenger/content/am-server.xhtml Line Number 171, Column 21: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2085089/+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 2085089] Re: Account server settings: XML Parsing Error: undefined entity
Same error. Thunderbird 128.3.1esr (64-bit), on Ubuntu newly upgraded to 24.04. -- 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/2085089 Title: Account server settings: XML Parsing Error: undefined entity Status in thunderbird package in Ubuntu: Confirmed Bug description: After upgrade to Ubuntu 24.04 from 23.10 I can't access my email server settings in thunderbird on any of my email mailbox with following error: error:XML Parsing Error: undefined entity Location: chrome://messenger/content/am-server.xhtml Line Number 171, Column 21: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2085089/+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 2083875] [NEW] cannot add nautilus to seahorse; can't get 'encrypt' option on right click on a file
Public bug reported: I am on ubuntu 24.04, trying to install encryption capability. I could not get Veracrypt to work, and am now trying to use seahorse. I have installed seahorse. Per instructions on 'make use of' i then try to install nautilus, and get: thomas@thomas-ThinkCentre-M75e:~$ sudo apt install seahorse-nautilus Reading package lists... Done Building dependency tree... Done Reading state information... Done Package seahorse-nautilus is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'seahorse-nautilus' has no installation candidate (I tried caja instrad - no joy) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/2083875 Title: cannot add nautilus to seahorse; can't get 'encrypt' option on right click on a file Status in nautilus package in Ubuntu: New Bug description: I am on ubuntu 24.04, trying to install encryption capability. I could not get Veracrypt to work, and am now trying to use seahorse. I have installed seahorse. Per instructions on 'make use of' i then try to install nautilus, and get: thomas@thomas-ThinkCentre-M75e:~$ sudo apt install seahorse-nautilus Reading package lists... Done Building dependency tree... Done Reading state information... Done Package seahorse-nautilus is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'seahorse-nautilus' has no installation candidate (I tried caja instrad - no joy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2083875/+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 2083310] [NEW] GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in custom.conf
Public bug reported: GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in /etc/gdm3/custom.conf Nine years ago with xorg-server 1.17 ago the `-nolisten tcp` option was reversed as a `-listen tcp`. Before, the behavior was to always enable tcp unless `-nolisten tcp` was set, now the behavior is to always disable tcp unless `-listen tcp` is set. To reverse the behaviour, GDM should be built with `HAVE_XSERVER_WITH_LISTEN` being defined, typically by passing `-DHAVE_XSERVER_WITH_LISTEN=1` to the compiler, as seen in the source: https://gitlab.gnome.org/GNOME/gdm/-/blob/08aea8002a2725f07a0889f52584d284648b2e82/daemon/gdm- server.c#L329 GDM modified its behaviour 8 years ago: https://gitlab.gnome.org/GNOME/gdm/-/commit/3f59fa0da5168451898db63e51e312ce894af0c1 and two years ago it was modified again: https://gitlab.gnome.org/GNOME/gdm/-/commit/bc16c9898012e463bc6b79c3faa8f81ed54527f7 Maybe this define was never added to the GDM build script? The web is full of forum threads of people trying to make GDM works with TCP listening, fail to get it working, and give up and use lightdm instead, this is probably because GDM was built without the expected define. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Oct 1 10:43:26 2024 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 mtime.conffile..etc.gdm3.custom.conf: 2024-10-01T10:43:20.322306 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages ** Description changed: GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in /etc/gdm3/custom.conf Nine years ago with xorg-server 1.17 ago the `-nolisten tcp` option was reversed as a `-listen tcp`. Before, the behavior was to always enable tcp unless `-nolisten tcp` was set, now the behavior is to always disable tcp unless `-listen tcp` is set. To reverse the behaviour, GDM should be built with `HAVE_XSERVER_WITH_LISTEN` being defined, typically by passing `-DHAVE_XSERVER_WITH_LISTEN=1` to the compiler, as seen in the source: https://gitlab.gnome.org/GNOME/gdm/-/blob/08aea8002a2725f07a0889f52584d284648b2e82/daemon/gdm- server.c#L329 - GDM modified its default behaviour 8 years ago: + GDM modified its behaviour 8 years ago: https://gitlab.gnome.org/GNOME/gdm/-/commit/3f59fa0da5168451898db63e51e312ce894af0c1 and two years ago it was modified again: https://gitlab.gnome.org/GNOME/gdm/-/commit/bc16c9898012e463bc6b79c3faa8f81ed54527f7 - Maybe this define was never added to GDM the build script? + Maybe this define was never added to the GDM build script? The web is full of forum threads of people trying to make GDM works with TCP listening, fail to get it working, and give up and use lightdm instead, this is probably because GDM was built without the expected define. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gdm3 46.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-44.44-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Oct 1 10:43:26 2024 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 mtime.conffile..etc.gdm3.custom.conf: 2024-10-01T10:43:20.322306 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2083310 Title: GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in custom.conf Status in gdm3 package in Ubuntu: New Bug description: GDM doesn't start Xorg with `-listen tcp` when DisallowTCP=false is set in /etc/gdm3/custom.conf Nine years ago with xorg-server 1.17 ago the `-nolisten tcp` option was reversed as a `-listen tcp`. Before, the behavior was to always enable tcp unless `-nolisten tcp` was set, now the behavior is to always disable tcp unless `-listen tcp` is set. To reverse the behaviour, GDM should be built with `HAVE_XSERVER_WITH_LISTEN` being defined, typically by passing `-DHAVE_XSERVER_WITH_LISTEN=1` to the compiler, as seen in the source: https://gitlab.gnome.org/GNOME/gdm/-/blob/08aea8002a2725f07a0889f52584d284648b2e82/daemon/gdm- server.c#L329 GDM modified its behaviour
[Desktop-packages] [Bug 2080768] [NEW] apparmor profile: allow gio-launch-desktop
Public bug reported:
I use the mozilla-team-ppa for Firefox and was not able to open
downloaded files directly from Firefox itself. It only gave me a file
picker to open file-links.
After open Firefox from the shell I saw this message:
** (firefox:1628082): WARNING **: 14:27:58.603: Cannot launch default
application: Kindprozess
»/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop« konnte nicht ausgeführt
werden (Keine Berechtigung)
[Parent 1628082, Main Thread] WARNING: Cannot launch application: Kindprozess
»/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop« konnte nicht ausgeführt
werden (Keine Berechtigung): 'glib warning', file
/build/firefox-J0YjYH/firefox-130.0+build2/toolkit/xre/nsSigHandlers.cpp:187
Which I fixed after adding to following content to the
/etc/apparmor.d/usr.bin.firefox
# Allow opening links
/usr/lib/@{multiarch}/glib-[0-9]*/gio-launch-desktop ix,
and forced a reload with
sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox
Please include this to the Firefox packages.
Many thanks,
Thomas Creutz
** 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/2080768
Title:
apparmor profile: allow gio-launch-desktop
Status in firefox package in Ubuntu:
New
Bug description:
I use the mozilla-team-ppa for Firefox and was not able to open
downloaded files directly from Firefox itself. It only gave me a file
picker to open file-links.
After open Firefox from the shell I saw this message:
** (firefox:1628082): WARNING **: 14:27:58.603: Cannot launch default
application: Kindprozess
»/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop« konnte nicht ausgeführt
werden (Keine Berechtigung)
[Parent 1628082, Main Thread] WARNING: Cannot launch application: Kindprozess
»/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop« konnte nicht ausgeführt
werden (Keine Berechtigung): 'glib warning', file
/build/firefox-J0YjYH/firefox-130.0+build2/toolkit/xre/nsSigHandlers.cpp:187
Which I fixed after adding to following content to the
/etc/apparmor.d/usr.bin.firefox
# Allow opening links
/usr/lib/@{multiarch}/glib-[0-9]*/gio-launch-desktop ix,
and forced a reload with
sudo apparmor_parser -r /etc/apparmor.d/usr.bin.firefox
Please include this to the Firefox packages.
Many thanks,
Thomas Creutz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2080768/+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 2063005] Re: Some shell elements don't respond to touchscreen in Xorg sessions
Is there a known workaround for this bug? I've found that holding an additional finger on the screen before pressing an element will sometimes work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2063005 Title: Some shell elements don't respond to touchscreen in Xorg sessions Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Starting in GNOME 46 touchscreen input on the X11 session has become unusable the touchscreen is responsive on the desktop itself (moving the cursor) but does not interact with most things on GNOME 46 on the current version of Ubuntu Noble, touch input does NOT work with: - On screen keyboard (touch is registered but no keystrokes get input) - clicking options in gnome appindicators (indicators can be opened but clicking any option does nothing) - interacting with application overview (cannot press left and right buttons or search bar) - selecting textboxs - any of the touch gestures (eg: swipe up from bottom to bringup keyboard) All of the above worked just fine on GNOME 45 on Ubuntu Mantic (and Ubuntu Noble from March and earlier before it was "upgraded" to GNOME 46). Tested on a fresh image as well as an old image from February running GNOME 45 upgraded to the latest packages with GNOME 46 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu DisplayManager: sddm DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2021-06-21 (1035 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Package: xorg-server PackageArchitecture: amd64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 46.0-1ubuntu7 Tags: noble Uname: Linux 6.8.0-28-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-04-21 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev render sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu2 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 24.04 Package: xorg-server PackageArchitecture: arm64 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu7 Tags: noble third-party-packages Uname: Linux 4.9.140-l4t aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip gdm lpadmin plugdev sambashare sudo users video weston-launch _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063005/+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 819835] Re: PANIC: unprotected error in call to Lua API
Adding to this since I'm seeing the exact same issue: fmtutil [INFO]: log file copied to: /var/lib/texmf/web2c/pdftex/pdfetex.log fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/pdfetex.fmt installed. fmtutil [ERROR]: running `luatex -ini -jobname=luatex -progname=luatex luatex.ini https://bugs.launchpad.net/bugs/819835 Title: PANIC: unprotected error in call to Lua API Status in texlive-base package in Ubuntu: New Bug description: I am trying to install live tex, but I will get errors everywhere i try to install and uninstall the software. This is a copy of the fmtutil file which has been generated. fmtutil: running `pdftex -ini -jobname=etex -progname=etex -translate-file=cp227.tcx *etex.ini' ... This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (INITEX) (/usr/share/texmf-texlive/web2c/cp227.tcx) entering extended mode (/usr/share/texmf-texlive/tex/plain/config/etex.ini (/usr/share/texmf-texlive/tex/plain/etex/etex.src (/usr/share/texmf-texlive/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, macros, math definitions, output routines, hyphenation (/usr/share/texmf-texlive/tex/generic/hyphen/hyphen.tex [skipping from \patterns to end-of-file...])) (/usr/share/texmf-texlive/tex/plain/etex/etexdefs.lib Skipping module "grouptypes"; Loading module "interactionmodes"; Skipping module "nodetypes"; Skipping module "iftypes";) (/var/lib/texmf/tex/generic/config/language.def (/usr/share/texmf-texlive/tex/generic/hyphen/hyphen.tex)) Augmenting the Plain TeX definitions: \tracingall; Adding new e-TeX definitions: \eTeX, \loggingall, \tracingnone, register allocation; extended register allocation; Recycling: \addlanguage, \@nswer (not defined), \@sk, \b@dresponsetrue, \b@dresponsefalse, \ch@ckforyn, \mayber@cycle, \et@xabort, \et@xbuf, \et@xfmtsrc, \et@xfilehdr, \et@xinf, \et@xpatterns, \l@ngdefnfile, \n@xt, \p@rse (not defined), \pr@mpt (not defined), \pr@mptloop (not defined), \forcer@cycle, \usef@llback, \usef@llbacktrue, \usef@llbackfalse, Retaining: \et@xerr, \et@xinput, \et@xlibhdr, \et@xmsg, \et@xtoks, \et@xwarn, \et@xl@@d, \et@xl@ad, \et@xload, \et@xlang, \et@xhash, \eTeX, \etexhdrchk, \etexstatus, \module, \uselanguage, \r@tain, \r@cycle,) ) Beginning to dump on file etex.fmt (format=etex 2011.8.2) 2861 strings of total length 42087 7960 memory locations dumped; current usage is 203&7290 1251 multiletter control sequences \font\nullfont=nullfont \font\tenrm=cmr10 \font\preloaded=cmr9 \font\preloaded=cmr8 \font\sevenrm=cmr7 \font\preloaded=cmr6 \font\fiverm=cmr5 \font\teni=cmmi10 \font\preloaded=cmmi9 \font\preloaded=cmmi8 \font\seveni=cmmi7 \font\preloaded=cmmi6 \font\fivei=cmmi5 \font\tensy=cmsy10 \font\preloaded=cmsy9 \font\preloaded=cmsy8 \font\sevensy=cmsy7 \font\preloaded=cmsy6 \font\fivesy=cmsy5 \font\tenex=cmex10 \font\preloaded=cmss10 \font\preloaded=cmssq8 \font\preloaded=cmssi10 \font\preloaded=cmssqi8 \font\tenbf=cmbx10 \font\preloaded=cmbx9 \font\preloaded=cmbx8 \font\sevenbf=cmbx7 \font\preloaded=cmbx6 \font\fivebf=cmbx5 \font\tentt=cmtt10 \font\preloaded=cmtt9 \font\preloaded=cmtt8 \font\preloaded=cmsltt10 \font\tensl=cmsl10 \font\preloaded=cmsl9 \font\preloaded=cmsl8 \font\tenit=cmti10 \font\preloaded=cmti9 \font\preloaded=cmti8 \font\preloaded=cmti7 \font\preloaded=cmu10 \font\preloaded=cmmib10 \font\preloaded=cmbsy10 \font\preloaded=cmcsc10 \font\preloaded=cmssbx10 \font\preloaded=cmdunh10 \font\preloaded=cmr7 at 14.51799pt \font\preloaded=cmtt10 at 14.4pt \font\preloaded=cmssbx10 at 14.4pt \font\preloaded=manfnt 14787 words of font info for 50 preloaded fonts 14 hyphenation exceptions Hyphenation trie of length 6075 has 181 ops out of 35111 181 for language 0 0 words of pdfTeX memory 0 indirect objects No pages of output. Transcript written on etex.log. fmtutil: /var/lib/texmf/web2c/pdftex/etex.fmt installed. fmtutil: running `pdftex -ini -jobname=pdfetex -progname=pdfetex -translate-file=cp227.tcx *pdfetex.ini' ... This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009/Debian) (INITEX) (/usr/share/texmf-texlive/web2c/cp227.tcx) entering extended mode (/usr/share/texmf-texlive/tex/plain/config/pdfetex.ini (/etc/texmf/tex/generic/config/pdftexconfig.tex) (/usr/share/texmf-texlive/tex/plain/etex/etex.src (/usr/share/texmf-texlive/tex/plain/base/plain.tex Preloading the plain format: codes, registers, parameters, fonts, more fonts, macros, math definitions, output routines, hyphenation (/usr/share/texmf-texlive/tex/generic/hyphen/hyphen.tex [skipping from \patterns to end-of-file...])) (/usr/share/texmf-texlive/tex/plain/etex/etexdefs.lib Skipping module "grouptypes"; Loading module "interactionmodes"; Skipping module "nodetypes"; Skipping module "iftypes";) (/var/lib/texmf/tex/gener
[Desktop-packages] [Bug 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 Is there any estimate when this is being solved? This is really annoying. We upgraded the family to 22.04 LTS (using Firefox) and are now affected by this. Everything is updated to the most current level. Thank you. -- 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/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade 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/1968887/+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 2056590] [NEW] No physical sound through speakers, settings show sound.
Public bug reported: Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS. Bluetooth headset does not give problems. Microphone works, but bad quality. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 18:11:08 2024 InstallationDate: Installed on 2024-02-28 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3504DA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3504DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook 15 UM3504DA_UM3504DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2056590 Title: No physical sound through speakers, settings show sound. Status in alsa-driver package in Ubuntu: New Bug description: Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS. Bluetooth headset does not give problems. Microphone works, but bad quality. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 18:11:08 2024 InstallationDate: Installed on 2024-02-28 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/02/2023 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UM3504DA.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UM3504DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook 15 UM3504DA_UM3504DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2056590/+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 2049353] [NEW] wayland XWarpPointer backwards compability
Public bug reported: I'm not sure how to report this really as it's not a bug but still quite severe. Bear with me as I'm a Unity dev mainly. Unity uses function calls to X11 for setting mouse cursor positions. Many games use this to lock the cursor to a certain position. With no backwards compatibility to XWarpPointer these games will be broken in Wayland. As there's little chance these games will be updated, the only possibility here is that Wayland supports this in some way. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/2049353 Title: wayland XWarpPointer backwards compability Status in wayland package in Ubuntu: New Bug description: I'm not sure how to report this really as it's not a bug but still quite severe. Bear with me as I'm a Unity dev mainly. Unity uses function calls to X11 for setting mouse cursor positions. Many games use this to lock the cursor to a certain position. With no backwards compatibility to XWarpPointer these games will be broken in Wayland. As there's little chance these games will be updated, the only possibility here is that Wayland supports this in some way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/2049353/+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 2025526] Re: Printer is not available in chromium snap
Hello all, I have been having the same problem (CUPS printer not showing/being available on Chromium), and seem to have fixed it as follows:- Open CUPS administration page (localhost:631/admin) under Server settings, enable 'Allow printing from the Internet' (I also have 'Allow remote administration' enabled, but I don't think this matters) Click 'Change Settings' The printer now appears in the Print dialog, under 'More...' options, and can be selected (and, more importantly, will print!) -- 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/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2046650] Re: pcscd starts, then from applications all readers connected wont work
# pcscd --foreground --info --color debuglog.c:386:DebugLogSetLevel() debug level=info 0040 pcscdaemon.c:356:main() Force colored logs 0381 pcscdaemon.c:666:main() pcsc-lite 1.9.9 daemon ready. 00013684 hotplug_libudev.c:421:HPAddDevice() Adding USB device: REINER SCT cyberJack wave 0068 readerfactory.c:1093:RFInitializeReader() Attempting startup of REINER SCT cyberJack wave (3428049512) 00 00 using /usr/lib/pcsc/drivers/libifd-cyberjack.bundle/Contents/Linux/libifd-cyberjack.so CYBERJACK: Started 1582 readerfactory.c:968:RFBindFunctions() Loading IFD Handler 3.0 Same for some other readers. While pcscd ist starting they are reported, but starting pcsc_scan just prints $ pcsc_scan PC/SC device scanner V 1.6.2 (c) 2001-2022, Ludovic Rousseau then doing nothing more. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2046650 Title: pcscd starts, then from applications all readers connected wont work Status in pcsc-lite package in Ubuntu: New Bug description: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2046650/+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 2046650] [NEW] pcscd starts, then from applications all readers connected wont work
Public bug reported: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2046650 Title: pcscd starts, then from applications all readers connected wont work Status in pcsc-lite package in Ubuntu: New Bug description: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2046650/+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 2041491] Re: Provide an option to avoid the yaml NM backend
I also would like to opt-out to the Netplan Backend in NM, without recomplie the whole stuff. As already written on that page*, I dont like to be forced to that backend. It could be such a easy job, if the original keyfile plugin would not be patched that way it got - and if it could be compiled with a extra name like keyfile-netplan or something. So there could also be two plugin distibution packages, we can select to install. * https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml- settings/32420/21 -- 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/2041491 Title: Provide an option to avoid the yaml NM backend Status in netplan.io package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Hi, recently netplan added support for a yaml NM backend: https://discourse.ubuntu.com/t/call-for-testing-networkmanager-yaml- settings/32420 The rationale is that "the descriptive YAML layer is especially useful in cloud environments": https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/556 It's great that you care about that user group! Please also care for the rest of us that do not use cloud environments! For example, I routinely review, clone, backup or even directly edit the /etc/NetworkManager/system-connections files in my desktops and servers, in all distributions. Having an Ubuntu-specific way to do things will make things harder for me. I will have to learn a new Ubuntu-specific syntax, develop scripts and methods to convert my connections between distributions, I will need to discover and report bugs in the netplan <=> nm mapping etc... I.e. Ubuntu is great for the cloud, and it's awesome that you want to provide a unified yaml-based experience for cloud-init etc. But Ubuntu is also great outside the cloud; please allow us to continue having a unified experience between distributions (i.e. directly using nm or systemd-networkd) without enforcing an Ubuntu-specific way of doing things (netplan) to us. For Ubuntu 24.04+, please provide an option to avoid the yaml NM backend, thank you very much! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2041491/+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 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!
@oibaf thanks, I reported it:
- https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
(nice issue number by the way ☺️)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #1
https://gitlab.freedesktop.org/mesa/mesa/-/issues/1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039352
Title:
OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
with: *ERROR* Not enough memory for command submission!
Status in mesa package in Ubuntu:
New
Bug description:
I first thought the Radeon PRO W7600 was affected, in fact the
affected GPU is the AMD FirePro S7150.
See comment 3 and below:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
__
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
[Desktop-packages] [Bug 2039352] Re: OpenGL applications don't run on AMD FirePro S7150 and fill dmesg with: *ERROR* Not enough memory for command submission!
I reproduce the bug with current Mesa
(d97427f41c1603db2f657b5d9c3f91a97f74b1c0) and LLVM 16.0.6. I don't know
if the bug is on drm side or on Mesa side.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039352
Title:
OpenGL applications don't run on AMD FirePro S7150 and fill dmesg
with: *ERROR* Not enough memory for command submission!
Status in mesa package in Ubuntu:
New
Bug description:
I first thought the Radeon PRO W7600 was affected, in fact the
affected GPU is the AMD FirePro S7150.
See comment 3 and below:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
__
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default
[Desktop-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!
I reproduce the same issue if I just do:
```
DRI_PRIME=1 glxinfo -B
name of display: :1
```
Which means the fault happens when using the AMD FirePro S7150, NOT the
AMD Radeon PRO W7600.
Maybe for some reasons Unigine Superposition tries to use all GPUs
available?
So, the bug is now easier to reproduce, it is affecting the AMD FirePro
S7150, and a glxinfo is enough.
** Summary changed:
- Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not
enough memory for command submission!
+ OpenGL applications don't run on AMD FirePro S7150 and fills dmesg with:
*ERROR* Not enough memory for command submission!
** Description changed:
+ I first thought the Radeon PRO W7600 was affected, in fact the affected
+ GPU is the AMD FirePro S7150.
+
+ See comment 3 and below:
+ https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2039352/comments/3
+
+ __
+
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvr
[Desktop-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not enough memory for command submission!
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
- There are more then one GPU in that system but the one used for
+ There are more than one GPU in that system but the one used for
rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xse
[Desktop-packages] [Bug 2039352] Re: Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!
In the log file you may see notice of some amdgpu-pro OpenCL components
like ROCm ROCr OpenCL or Legacy Orca OpenCL, there is no amdgpu-pro
OpenGL or dkms module installed though. Removing entirely the amdgpu-pro
OpenCL packages produce the same bug anyway. The contrary would have
been surprising since I assume Superposition to be an OpenGL benchmark
and to not make use of OpenCL, but to be 100% sure I removed all those
amdgpu-pro packages and I get the same bug with stock Ubuntu anyway.
** Summary changed:
- Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough
memory for command submission!
+ Unigine Superposition 1.1 doesn't run and fills dmesg with: *ERROR* Not
enough memory for command submission!
** Description changed:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
- There is multiple GPU in that system but the one used for rendering is a
- Radeon PRO W7600:
-
+ There are more then one GPU in that system but the one used for
+ rendering is a Radeon PRO W7600:
```
Slot: 47:00.0
Class:VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice: Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
- Vendor: AMD (0x1002)
- Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
- Version: 23.2.1
- Accelerated: yes
- Video memory: 8192MB
- Unified memory: no
- Preferred profile: core (0x1)
- Max core profile version: 4.6
- Max compat profile version: 4.6
- Max GLES1 profile version: 1.1
- Max GLES[23] profile version: 3.2
+ Vendor: AMD (0x1002)
+ Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
+ Version: 23.2.1
+ Accelerated: yes
+ Video memory: 8192MB
+ Unified memory: no
+ Preferred profile: core (0x1)
+ Max core profile version: 4.6
+ Max compat profile version: 4.6
+ Max GLES1 profile version: 1.1
+ Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
- vhba/20211218, 6.2.0-33-generic, x86_64: installed
- vhba/20211218, 6.5.0-9-generic, x86_64: installed
+ v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff
between built and installed module!)
+ vhba/20211218, 6.2.0-33-generic, x86_64: installed
+ vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.re
[Desktop-packages] [Bug 2039352] [NEW] Unigine Superposition 1.1 doesn't run and fill dmesg with: *ERROR* Not enough memory for command submission!
Public bug reported:
When I run Unigine Superposition 1.1, it doesn't open any window and
dmesg is filled with:
```
[36881.961064] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.962579] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.963946] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.965556] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.967138] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
[36881.968522] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Not enough memory for
command submission!
```
printing new error log lines many time per second.
Killing the Unigine Superposition process stops the log printing.
There is multiple GPU in that system but the one used for rendering is a
Radeon PRO W7600:
```
Slot: 47:00.0
Class: VGA compatible controller [0300]
Vendor: Advanced Micro Devices, Inc. [AMD/ATI] [1002]
Device: Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] [7480]
SVendor:Advanced Micro Devices, Inc. [AMD/ATI] [1002]
SDevice:Device [0e0d]
ProgIf: 00
Driver: amdgpu
Module: amdgpu
IOMMUGroup: 58
```
```
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: AMD (0x1002)
Device: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.54,
6.5.0-9-generic) (0x7480)
Version: 23.2.1
Accelerated: yes
Video memory: 8192MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
```
Other games like Unvanquished or Quake II RTX are working correctly.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: libglapi-mesa 23.2.1-1ubuntu3
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins:
[core,bailer,detection,composite,opengl,imgjpeg,compiztoolbox,copytex,decor,regex,snap,vpswitch,mousepoll,gnomecompat,titleinfo,imgpng,resize,animation,expo,ezoom,grid,place,move,imgsvg,workarounds,wall,session,thumbnail,staticswitcher,fade,scale]
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Oct 14 14:58:23 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback/0.12.7, 6.5.0-9-generic, x86_64: installed (WARNING! Diff between
built and installed module!)
vhba/20211218, 6.2.0-33-generic, x86_64: installed
vhba/20211218, 6.5.0-9-generic, x86_64: installed
ExtraDebuggingInterest: Yes
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.5.0-9-generic
root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@
amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1
radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1
amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/08/2023
dmi.bios.release: 5.23
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: WRX80SU8-F6
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Default string
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80SU8-F6:bd06/08/2023:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: Default string
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Default string
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
htt
[Desktop-packages] [Bug 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists
To be even more precise: you activated a countdown that would automatically close this issue if no answer would be given to the only question that was not answerable because of the very nature of this bug. The Launchpad software is just obeying to human decisions, there. -- 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/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: Expired Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+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 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists
I may update that sentence: > You're just saying no one tried to reproduce the bug, this is different. You're just saying no one tried to reproduce the bug _and it was just decided to let it expire with the distribution version itself_, this is different. Launchpad can't be taken responsible for, it's a machine. -- 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/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: Expired Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+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 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists
There was enough information to be actionable: 1. Get Ubuntu with the version the bug is reported for. 2. Apply the reproduction steps given in the very first message reporting the bug: ``` killall nautilus GTK_THEME= nautilus ``` The bug was said to be a rendering bug, any human with functional eyes following the reproduction steps could see the rendering bug described in the very first message: > Then try to select some icons, selected icons will not be displayed as selected. There was no need for any screenshot: the described bug is that rendering of nautilus would not change between selected and unselected icon. Those words are more meaningful than a screenshot. Screenshot may even add more ambiguities to the description, since the bug is that no change were rendered, nothing happens between before and after the action that should lead to a change being rendered. The bug was that the render did not update when you selected something. There was no way a screenshot could describe the bug as the bug was there was no rendering change. The bug was that something was not rendered. The bug could not be captured by a screenshot. The bug was that the render was not responding to an event. The issue was complete from the start. You're just saying no one tried to reproduce the bug, this is different. Don't let to machines what machines can't do. This issue was written for humans. That's why there was reproduction steps given, and that's why what should be expected and what was given instead was described. -- 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/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: Expired Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+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 2038892] [NEW] How To Contact +1(202-960-2084) McAfee Customer Service Number?
Private bug reported: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. ** Affects: null-and-void Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2038892 Title: How To Contact +1(202-960-2084) McAfee Customer Service Number? Status in NULL Project: Invalid Bug description: o contact McAfee Customer Service Phone Number, you can follow these steps: Visit the McAfee Website: Start by going to the official McAfee website. Navigate to Support: Look for a “Support” or “Contact Us” link on the website. This is typically found at the top or bottom of the homepage. Choose Your Product: Select the McAfee product you need assistance with. They offer various security solutions, so make sure to pick the right one. Access the Help Center: Many common issues can be resolved by searching the McAfee Help Center. Try entering your problem or question in the search bar. Contact Options: If you can’t find a solution in the Help Center, look for contact options. This may include phone numbers, live chat, or email support. Click on the option that suits you best. Provide Information: When contacting McAfee, be prepared to provide information like your product key, account details, and a clear description of your issue. Follow Instructions: Follow the instructions provided by McAfee’s customer support team. They may guide you through troubleshooting steps or offer a solution tailored to your problem. Record Reference Numbers: If you speak to a customer service representative or open a support ticket, make sure to record any reference numbers or case IDs for future reference. Remember that McAfee’s contact options may vary depending on your location and the specific product you’re using. Always verify the contact details on their official website to ensure you’re reaching out to legitimate customer support. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/2038892/+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 2018555] Re: Nautilus rendering is broken if GTK_THEME env variable exists
This looks fixed in Ubuntu 23.04 and this was reported against Ubuntu 22.10. So, now that Ubuntu 22.10 is not supported, this can be considered fixed. That said, I don't understand why this bug was closed because “there has been no activity for 60 days”. The bug was still reproducible on Ubuntu 22.10 and reproduction instructions properly described. Bugs don't disappear by magic because there is no comment to add. I noticed that setting GTK_THEME to empty string (you also have to export the variable) still changes the way nautilus look in Ubuntu 23.04, but the different look doesn't make nautilus unusable (unlike what happened on Ubuntu 22.10). ``` killall nautilus export GTK_THEME= nautilus ``` I'm not sure what happens on Ubuntu 23.04 is a bug, though. -- 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/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: Expired Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+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 2036528] Re: Can't turn on bluetooth
works now. closing. ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2036528 Title: Can't turn on bluetooth Status in gnome-control-center package in Ubuntu: Invalid Bug description: When I try to click (enable) the toggle switch in the bluetooth panel in gnome-control-center, nothing happens. Bluetooth is always disabled. This happens since roughly 2 days on mantic. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:27:46 2023 InstallationDate: Installed on 2023-05-10 (132 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-07-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2036528/+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 2033645] Re: [BPO] libreoffice 7.5.6 for jammy
This has been accepted and is now in the queue pending publication. ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2033645 Title: [BPO] libreoffice 7.5.6 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.5.6 is in its sixth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.6_release * This source packages matches the proposed SRU for lunar handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033643 [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.5.6-0ubuntu0.23.04.1 * Backport target is Jammy/22.04 LTS releases to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1671/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Jammy/22.04 build at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15135069/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20230902_144308_89e10@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20230902_165623_9d364@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20230904_200742_5f3fa@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20230902_160737_b0f46@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20230902_232846_e9b82@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2033645/+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 2035016] Re: one of 3 monitors "frozen" when a window moves there
And it happened again after I unplugged and plugged my usb-c->display port cable . looks like this time there's more useful information in the logs. ** Attachment added: "journal.txt after unplug/plug the display port cable with mutter (45.0-1ubuntu1)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702554/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
with latest mutter+gnome-shell (single GPU), this still happens. log attached. ** Attachment added: "journal.txt from current boot 2 seconds after the problem occured with mutter (45.0-1ubuntu1)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2035016/+attachment/5702553/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in mutter package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overv
[Desktop-packages] [Bug 2036528] [NEW] Can't turn on bluetooth
Public bug reported: When I try to click (enable) the toggle switch in the bluetooth panel in gnome-control-center, nothing happens. Bluetooth is always disabled. This happens since roughly 2 days on mantic. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:27:46 2023 InstallationDate: Installed on 2023-05-10 (132 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-07-19 (61 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2036528 Title: Can't turn on bluetooth Status in gnome-control-center package in Ubuntu: New Bug description: When I try to click (enable) the toggle switch in the bluetooth panel in gnome-control-center, nothing happens. Bluetooth is always disabled. This happens since roughly 2 days on mantic. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-control-center 1:45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 19 10:27:46 2023 InstallationDate: Installed on 2023-05-10 (132 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to mantic on 2023-07-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2036528/+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 2035170] [NEW] Super+Left / Super+Right doesn't work with tiling extension enabled
Public bug reported: I have the tiling extension enabled & the key bindings correctly configured (see screenshot) but pressing Super+Left or Super+Right doesn't do anything. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 41-1+gnome45.2ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 06:56:47 2023 InstallationDate: Installed on 2023-05-10 (125 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-07-19 (54 days ago) ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages wayland-session ** Attachment added: "Tiling extension keybinding settings" https://bugs.launchpad.net/bugs/2035170/+attachment/5700172/+files/Screenshot%20from%202023-09-12%2006-58-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2035170 Title: Super+Left / Super+Right doesn't work with tiling extension enabled Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: I have the tiling extension enabled & the key bindings correctly configured (see screenshot) but pressing Super+Left or Super+Right doesn't do anything. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 41-1+gnome45.2ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 06:56:47 2023 InstallationDate: Installed on 2023-05-10 (125 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-07-19 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2035170/+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 2035114] [NEW] zenity 3.24.1 --question argument does not return a value in ubuntu 22.04
Public bug reported: '--question' attribute in zenity is not returning a value after the user interacts with the message box. It should be returning a 0, 1, or 5 depending on what the user selects. Other forms that zenity produces do return the appropriate values. tom@BossUbuntui9:~$ zenity --version 3.42.1 tom@BossUbuntui9:~$ zenity --calendar 09/12/2024 tom@BossUbuntui9:~$ zenity --question --title="Answer the question." --text="Yes or No?" tom@BossUbuntui9:~$ This is a paste from my terminal. As you can see the --version and --calendar arguments return the appropriate values. When I use the --question argument, it does not matter whether I press yes or no, I get nothing. ** Affects: zenity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/2035114 Title: zenity 3.24.1 --question argument does not return a value in ubuntu 22.04 Status in zenity package in Ubuntu: New Bug description: '--question' attribute in zenity is not returning a value after the user interacts with the message box. It should be returning a 0, 1, or 5 depending on what the user selects. Other forms that zenity produces do return the appropriate values. tom@BossUbuntui9:~$ zenity --version 3.42.1 tom@BossUbuntui9:~$ zenity --calendar 09/12/2024 tom@BossUbuntui9:~$ zenity --question --title="Answer the question." --text="Yes or No?" tom@BossUbuntui9:~$ This is a paste from my terminal. As you can see the --version and --calendar arguments return the appropriate values. When I use the --question argument, it does not matter whether I press yes or no, I get nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/2035114/+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 2035016] Re: one of 3 monitors "frozen" when a window moves there
> Please try adding this to /etc/environment as a workaround: > MUTTER_DEBUG_FORCE_KMS_MODE=simple this seem to help. and it also helps for having the mouse pointer in firefox working again (I filled https://bugzilla.mozilla.org/show_bug.cgi?id=1852519 for that) Does that have any negative impact (on performance)? ** Bug watch added: Mozilla Bugzilla #1852519 https://bugzilla.mozilla.org/show_bug.cgi?id=1852519 -- 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/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
** Attachment added: "journal.txt from current boot 2 seconds after the problem occured" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2035016/+attachment/5699911/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789d9f
[Desktop-packages] [Bug 2035016] Re: one of 3 monitors "frozen" when a window moves there
@Daniel, what exactly do you need from the journal? I don't want to post the full output here. it contains some private user sessions services output which I don't want to share. -- 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/2035016 Title: one of 3 monitors "frozen" when a window moves there Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789d9f0 i resource:///or
[Desktop-packages] [Bug 2035054] [NEW] Reset keyboard shortcuts gets overwritten and modifications show up again
Public bug reported: I did reset all keyboard shortcuts (Settings->Keyboard->View and customize Shortcuts) via the "Reset All ..." button. But now (after a reboot and apt update && apt dist-upgrade) I have some modfications back. Those modifications are: - Windows->Maximize Window - Windows->Restore Window - Windows->View split on left - Windows->View split on right Note that I have disabled all extensions (via the Extensions App and then the top toggle) but the "Ubuntu Tilling Assistant" toggle was still active. Deactivating that one does reset the Shortcuts again (and eg. Super+Left does work again) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-settings-daemon 45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 06:48:03 2023 InstallationDate: Installed on 2023-05-10 (124 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to mantic on 2023-07-19 (53 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/2035054 Title: Reset keyboard shortcuts gets overwritten and modifications show up again Status in gnome-settings-daemon package in Ubuntu: New Bug description: I did reset all keyboard shortcuts (Settings->Keyboard->View and customize Shortcuts) via the "Reset All ..." button. But now (after a reboot and apt update && apt dist-upgrade) I have some modfications back. Those modifications are: - Windows->Maximize Window - Windows->Restore Window - Windows->View split on left - Windows->View split on right Note that I have disabled all extensions (via the Extensions App and then the top toggle) but the "Ubuntu Tilling Assistant" toggle was still active. Deactivating that one does reset the Shortcuts again (and eg. Super+Left does work again) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-settings-daemon 45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 06:48:03 2023 InstallationDate: Installed on 2023-05-10 (124 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to mantic on 2023-07-19 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/2035054/+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 2035016] [NEW] one of 3 monitors "frozen" when a window moves there
Public bug reported: When I move a window to one of my 3 monitors (not the main display), the monitor freezes. That means that moving the mouse there doesn't work and the picture is frozen on that monitor (including the mouse pointer which is visible there). The journal has those logs: Sep 10 07:21:49 clown-t14 gnome-shell[5640]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Sep 10 07:21:49 clown-t14 systemd[5341]: Started vte-spawn-99883356-4f85-429c-a61b-60abac42.scope - VTE child process 15895 launched by kgx process 7379. Sep 10 07:22:00 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:04 clown-t14 gnome-shell[5640]: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThumbnail_ThumbnailsBox (0x55b07b31e510), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d5260 b resource:///org/gnome/shell/ui/workspacesView.js:646 (276d81d44970 @ 33) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:693 (276d81d44a10 @ 472) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #12 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: == Stack trace for context 0x55b0777837f0 == Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #0 7ffe4d1d53b0 b resource:///org/gnome/shell/ui/workspacesView.js:695 (276d81d44a10 @ 489) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #1 55b07789ddb8 i resource:///org/gnome/shell/ui/workspace.js:856 (276d81d040b0 @ 369) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #2 55b07789dd30 i resource:///org/gnome/shell/ui/workspace.js:808 (9aad18f9fb0 @ 17) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #3 55b07789dc98 i resource:///org/gnome/shell/ui/workspacesView.js:1014 (276d81d45420 @ 129) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #4 55b07789dc08 i resource:///org/gnome/shell/ui/overviewControls.js:699 (9aad188a100 @ 50) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #5 55b07789db80 i resource:///org/gnome/shell/ui/layout.js:372 (793307f55b0 @ 22) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #6 55b07789daf0 i resource:///org/gnome/shell/ui/overview.js:652 (9aad1885f10 @ 190) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #7 55b07789da70 i resource:///org/gnome/shell/ui/overview.js:635 (9aad1885ec0 @ 12) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #8 55b07789d9f0 i resource:///org/gnome/shell/ui/overviewControls.js:750 (9aad188a330 @ 55) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #9 7ffe4d1dc560 b resource:///org/gnome/shell/ui/environment.js:84 (7933077d560 @ 39) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #10 55b07789d968 i resource:///org/gnome/shell/ui/environment.js:250 (7933077da60 @ 14) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: #11 55b07789d8d8 i resource:///org/gnome/shell/ui/init.js:21 (7933077d060 @ 48) Sep 10 07:22:05 clown-t14 gnome-shell[5640]: Object .Gjs_ui_workspaceThu
[Desktop-packages] [Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_in
Facing the same issue with one of my client's site. Related to https://capapkcut.com/story-keren-capcut-template/";>Story Keren. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1648534 Title: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_connection_call_sync Status in GNOME Software: New Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Xenial: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1648534/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Is there any progress on this issue? (Progress as in: works for end- users as it did the last 20 years…) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2028758] [NEW] Enhanced Tilling broken when using Super-Left / Super-Right
Public bug reported: When enhanced tilling is activated (see screenshot) and I want to move a window to the left or right (with Super-Left or Super-Right commands), the window moves but also the app switcher is visible (see video). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 11:35:20 2023 InstallationDate: Installed on 2023-05-10 (77 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-07-19 (6 days ago) ** Affects: gnome-shell-extension-tiling-assistant (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic third-party-packages wayland-session ** Attachment added: "screencast showing the bug" https://bugs.launchpad.net/bugs/2028758/+attachment/5688536/+files/Screencast%20from%202023-07-26%2011-34-47.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-tiling-assistant in Ubuntu. https://bugs.launchpad.net/bugs/2028758 Title: Enhanced Tilling broken when using Super-Left / Super-Right Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: When enhanced tilling is activated (see screenshot) and I want to move a window to the left or right (with Super-Left or Super-Right commands), the window moves but also the app switcher is visible (see video). ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-ubuntu-tiling-assistant 39-3ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 26 11:35:20 2023 InstallationDate: Installed on 2023-05-10 (77 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-shell-extension-tiling-assistant UpgradeStatus: Upgraded to mantic on 2023-07-19 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2028758/+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 2023491] [NEW] Deleting files causes folders in the directory to disappear and reappear after a refresh
Public bug reported: I'm experiencing some inconsistencies when using Nautilus and deleting files. I've found a bug report upstream that describes the same behavior: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 Reproduced here for completeness: Steps to reproduce - Open a directory. - Delete some files, either permanently or move to wastebasket. - Refresh the current view. Current behavior - Folders that were not selected to be deleted disappear. Expected behavior - Only the selected files are deleted and removed from the file view. This bug (which affects me on Ubuntu 23.04) has apparently been fixed in upstream Gtk: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873 Please pull the fixes into Ubuntu 23.04. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 19:06:01 2023 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1607, 1234)' InstallationDate: Installed on 2021-11-12 (575 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (60 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus Importance: Unknown Status: Unknown ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #2941 https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 Importance: Unknown Status: Unknown -- 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/2023491 Title: Deleting files causes folders in the directory to disappear and reappear after a refresh Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: I'm experiencing some inconsistencies when using Nautilus and deleting files. I've found a bug report upstream that describes the same behavior: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2941 Reproduced here for completeness: Steps to reproduce - Open a directory. - Delete some files, either permanently or move to wastebasket. - Refresh the current view. Current behavior - Folders that were not selected to be deleted disappear. Expected behavior - Only the selected files are deleted and removed from the file view. This bug (which affects me on Ubuntu 23.04) has apparently been fixed in upstream Gtk: https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/5873 Please pull the fixes into Ubuntu 23.04. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 19:06:01 2023 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'7z'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1607, 1234)' InstallationDate: Installed on 2021-11-12 (575 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: nautilus UpgradeStatus: Upgraded to lunar on 2023-04-12 (60 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/2023491/+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 2023463] [NEW] Cannot remove items from side panel
Public bug reported: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic 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/2023463 Title: Cannot remove items from side panel Status in xorg package in Ubuntu: New Bug description: Only an annoying bug I cannot remove the attached from my menu on the side panel. Other items are removed ok. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-43.44-generic 5.19.17 Uname: Linux 5.19.0-43-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 11 14:22:20 2023 DistUpgraded: 2023-05-30 14:55:36,989 DEBUG /openCache(), new cache size 74014 DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:100c] InstallationDate: Installed on 2023-02-08 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire F5-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic root=UUID=d5663606-7967-4f64-9bf3-a8843f95c2b6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-05-30 (11 days ago) dmi.bios.date: 05/25/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.18 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Zoro_SL dmi.board.vendor: Acer dmi.board.version: V1.18 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.18:bd05/25/2017:br0.0:efr2.70:svnAcer:pnAspireF5-572:pvrV1.18:rvnAcer:rnZoro_SL:rvrV1.18:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireF5-572_100C_1.18: dmi.product.family: SKL dmi.product.name: Aspire F5-572 dmi.product.sku: Aspire F5-572_100C_1.18 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compi
[Desktop-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Is there any progress on this one? It completely disrupts workflows and is the single most annoying bug in the Gnome shell since a few years. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
Why is this bug a duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968887 ? It should definitely be the other way around, since it does not only affect chromium but all programs using the Gnome shell file-save dialog. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: Invalid Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Fix Released Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 2018555] [NEW] Nautilus rendering is broken if GTK_THEME env variable exists
Public bug reported: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages -- 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/2018555 Title: Nautilus rendering is broken if GTK_THEME env variable exists Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 22.10, nautilus rendering is broken as soon as GTK_THEME environment exists, and there are some other components of GNOME that sets it at desktop launch (for example the Desktop may set it as GTK_THEME=Adwaita:dark). I have found no GTK_THEME value to make nautilus render properly, even the empty string breaks nautilus. How to reproduce: ``` killall nautilus GTK_THEME= nautilus ``` Then try to select some icons, selected icons will not be displayed as selected. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri May 5 06:49:41 2023 GsettingsChanges: ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 nautilus-image-converter 0.4.0-2 python3-nautilus 4.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2018555/+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 2018526] [NEW] Mesa Clover built with opaque pointers against LLVM built without opaque pointers
Public bug reported: This can be verified with any OpenCL application that actually tries to compute something (clinfo may not be enough). A very simple application to reproduce the bug is cl-mem: ``` git clone https://github.com/nerdralph/cl-mem.git cd cl-mem make ./cl-mem OpenCL build failed (-11). Build log follows: fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 15.0.7') ``` I may provide help to fix it, without guarantee. The migration of LLVM to opaque pointers was not painless, some versions of Mesa may build and run against some versions of LLVM 15 given that build option or that patch is used, some not. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mesa-opencl-icd 22.2.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu May 4 17:38:07 2023 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches MachineType: Default string Default string ProcEnviron: LANGUAGE=fr_FR:en TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=f35ecf77-511e-4dde-ac11-c1d848e97315 ro rootflags=subvol=@ amdgpu.si_support=1 radeon.si_support=0 amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.exp_hw_support=1 amdgpu.gpu_recovery=1 amdgpu.ppfeaturemask=0x delayacct zswap.enabled=1 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/04/2022 dmi.bios.release: 5.23 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: WRX80PRO-F1 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrWRX80PRO-F1:bd08/04/2022:br5.23:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-06-16T17:39:00.798346 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2018526 Title: Mesa Clover built with opaque pointers against LLVM built without opaque pointers Status in mesa package in Ubuntu: New Bug description: This can be verified with any OpenCL application that actually tries to compute something (clinfo may not be enough). A very simple application to reproduce the bug is cl-mem: ``` git clone https://github.com/nerdralph/cl-mem.git cd cl-mem make ./cl-mem OpenCL build failed (-11). Build log follows: fatal error: cannot open file '/usr/lib/clc/hawaii-amdgcn-mesa-mesa3d.bc': Opaque pointers are only supported in -opaque-pointers mode (Producer: 'LLVM15.0.7' Reader: 'LLVM 15.0.7') ``` I may provide help to fix it, without guarantee. The migration of LLVM to opaque pointers was not painless, some versions of Mesa may build and run against some versions of LLVM 15 given that build option or that patch is used, some not. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: mesa-opencl-icd 22.2.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.3 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDes
[Desktop-packages] [Bug 2017365] [NEW] vanilla-gnome-desktop depends on pulseaudio which results in a conflict
Public bug reported: Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with: The following packages have unmet dependencies: pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. ** Affects: ubuntu-gnome-meta (Ubuntu) Importance: Undecided Status: New ** Package changed: pipewire (Ubuntu) => ubuntu-gnome-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017365 Title: vanilla-gnome-desktop depends on pulseaudio which results in a conflict Status in ubuntu-gnome-meta package in Ubuntu: New Bug description: Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with: The following packages have unmet dependencies: pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/2017365/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio
I realize that the conflict is probably intended and my issue is that vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate bug, sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire- alsa conflicts with pulseaudio] Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2017196] Re: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire-alsa conflicts with pulseaudio
I seem to hit the same dep issues on a freshly installed 23.04 system when trying to install vanilla-gnome-desktop. The following packages have unmet dependencies: pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2017196 Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 [pipewire- alsa conflicts with pulseaudio] Status in pipewire package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Upgrading from UBUNTU 22.10 to UBUNTU 23.04 as advised. Required software appeared to have downloaded. Committing Changes operated to about 84% at which point the system crashed. It was necessary to re- initiate the upgrade procedure. This time, the upgrade proceeded to about 95% when an error notification appeared on the screen. Further upgrades were not attempted. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: pipewire-alsa (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Fri Apr 21 04:46:04 2023 ErrorMessage: conflicting packages - not installing pipewire-alsa:amd64 InstallationDate: Installed on 2020-02-04 (1171 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: pipewire Title: package pipewire-alsa (not installed) failed to install/upgrade: conflicting packages - not installing pipewire-alsa:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/2017196/+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 2014198] [NEW] the gnome IPsec/IKEv2 (strongswan) connection editor is missing in 23.04 beta. The menu item is there, but the application is missing.
Public bug reported: WhenI hope the Gnome connection editor, OpenVPN et all load properly when selected. But the IPsec/IKEv2 configurator does not load from the configuration menu. The IPsec/IKEv2 gnome plugin is missing, even though all the others are present. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager-gnome 1.30.0-2ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 16:08:59 2023 InstallationDate: Installed on 2022-05-24 (311 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.2.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.240 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: network-manager-applet UpgradeStatus: Upgraded to lunar on 2023-01-28 (62 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.12 connected started full enabled enabled enabled missing enabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/2014198 Title: the gnome IPsec/IKEv2 (strongswan) connection editor is missing in 23.04 beta. The menu item is there, but the application is missing. Status in network-manager-applet package in Ubuntu: New Bug description: WhenI hope the Gnome connection editor, OpenVPN et all load properly when selected. But the IPsec/IKEv2 configurator does not load from the configuration menu. The IPsec/IKEv2 gnome plugin is missing, even though all the others are present. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: network-manager-gnome 1.30.0-2ubuntu1 Uname: Linux 6.2.8-060208-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 31 16:08:59 2023 InstallationDate: Installed on 2022-05-24 (311 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IpRoute: default via 192.168.2.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.2.0/24 dev wlp2s0 proto kernel scope link src 192.168.2.240 metric 600 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: network-manager-applet UpgradeStatus: Upgraded to lunar on 2023-01-28 (62 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.12 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/2014198/+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 2013135] [NEW] Dissapearing Mouse Cursor
Public bug reported: Touching the touch screen display removes the mouse cursor. It comes back after blindly navigating to the menu bar. This also happends randomly without touching the touchscreen. There doesn't appear to be a trigger for the random disappearances that is user input. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 18:19:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc] InstallationDate: Installed on 2023-02-28 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell Inc. Inspiron 7737 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1322e8b8-bc4a-464a-89b8-6bc305451ff5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0H9X60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.ec.firmware.release: 0.4 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/09/2013:br0.4:efr0.4:svnDellInc.:pnInspiron7737:pvr:rvnDellInc.:rn0H9X60:rvrA00:cvnDellInc.:ct8:cvr0.1:skuInspiron7737: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7737 dmi.product.sku: Inspiron 7737 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2013135 Title: Dissapearing Mouse Cursor Status in xorg package in Ubuntu: New Bug description: Touching the touch screen display removes the mouse cursor. It comes back after blindly navigating to the menu bar. This also happends randomly without touching the touchscreen. There doesn't appear to be a trigger for the random disappearances that is user input. Thanks, ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.157 Wed Oct 12 09:19:07 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 28 18:19:00 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05fc] Subsystem: Dell GK107M [GeForce GT 750M] [1028:05fc] InstallationDate: Installed on 2023-02-28 (28 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: Dell In
[Desktop-packages] [Bug 2011751] Re: openbox crashed with SIGABRT
After discussion with the Security Team, we do not believe this is a Security bug and that there currently is no need to keep it private as there is other public discourse via other related bugs on other trackers and here in Launchpad with other bugs (marked as dupes of this or such). ** Information type changed from Private Security to Public -- 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/2011751 Title: openbox crashed with SIGABRT Status in glib2.0 package in Ubuntu: Confirmed Status in openbox package in Ubuntu: Confirmed Bug description: Lubuntu lunar (primary box) on - dell [optiplex] 7050 (i5-6500, 16gb, intel hd530/i915) I experienced a crash yesterday (openbox) but tend to ignore the first crashes... Whilst using the machine again today a crash occurred. This is my primary box, so my setup is pretty consistent - featherpad (restored session) - hexchat (irc) - qterminal (only single tab today; usually many) - firefox (snap, most sites excluding google related) - chromium (snap, used for anything google related) - telegram (snap) - element I was using chromium full screen (trying to read my gmail inbox) when borders around windows disappeared & I lost the capacity to switch between windows; mouse would move, but keyboard appeared mostly dead (it wasn't, more I think windows weren't responding, inc. clicks with mouse though that's likely inconsistent; I could work out how to describe it yesterday, but todays is almost identical). I switched to text terminal (ctrl+alt+f4) & explored; returned to GUI and used - ctrl+alt+t to open new terminal - openbox & session returned to what I expect... ** expected outcome Openbox doesn't crash ** actual outcome all windows lost borders, and i lost ability to switch between windows I appeared to have minimal control (not true, more a fraction of what I expect) ** How to get crash For me, - I used chromium (browser) - make chromium full screen (ie. F11) - click on something & right-click to open in new window OPENBOX CRASH. ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: openbox 3.6.1-10 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: LXQt Date: Thu Mar 16 09:46:22 2023 ExecutablePath: /usr/bin/openbox ExecutableTimestamp: 1643543619 InstallationDate: Installed on 2023-01-25 (49 days ago) InstallationMedia: Lubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230124) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/openbox ProcCwd: /home/guiverc RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: openbox StacktraceTop: () at /lib/x86_64-linux-gnu/libobt.so.2 () at /lib/x86_64-linux-gnu/libc.so.6 client_calc_layer () () () at /lib/x86_64-linux-gnu/libobt.so.2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+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 1701424] Re: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção.
*** This bug is a duplicate of bug 1706204 *** https://bugs.launchpad.net/bugs/1706204 ** This bug has been marked a duplicate of bug 1706204 package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to blt in Ubuntu. https://bugs.launchpad.net/bugs/1701424 Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. Status in blt package in Ubuntu: New Bug description: I can't install anything on my terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tk8.6-blt2.5 2.5.3+dfsg-3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 29 23:34:39 2017 DpkgTerminalLog: dpkg: erro ao processar o pacote tk8.6-blt2.5 (--remove): O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. ErrorMessage: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. InstallationDate: Installed on 2017-04-13 (77 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: blt Title: package tk8.6-blt2.5 2.5.3+dfsg-3 failed to install/upgrade: O pacote está num estado de inconsistência muito mau; deve reinstalá-lo antes de tentar a remoção. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blt/+bug/1701424/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
Regarding NGINX, PCRE2 support is now available in NGINX nginx 1.21.5+ so there was support as of December 24th 2021 and later. Which means that NGINX 1.22+ supports PCRE2. This could be marked as Triaged *for 23.04 and later* once NGINX is merged in from Debian upstream, if someone can put a few cycles to build/test. Refer to https://trac.nginx.org/nginx/changeset/0b5f12d5c531be630a4aae644686be83cfed3267/nginx and the "fixed" Trac bug https://trac.nginx.org/nginx/ticket/720 -- 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/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in postfix package in Debian: Fix Released Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1968887] Re: Save As Dialog Box does not get focus in Ubuntu 22.04
*** This bug is a duplicate of bug 1949340 *** https://bugs.launchpad.net/bugs/1949340 This annoying bug rears its ugly head since I upgraded my own and my wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop or 20.04 workbox. When using the Save As dialog, focus switches to the filter/search field in the dialog when we start typing a name for the file. The focus change happens after each character, so it's practically unusable. Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap). -- 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/1968887 Title: Save As Dialog Box does not get focus in Ubuntu 22.04 Status in gnome-shell package in Ubuntu: Confirmed Bug description: When using a browser to right click a file and save as, the save as window does not get focus, which means you can't just type the name of the file you want, you have to force focus onto the window to use it by clicking it. This defeats the entire purpose of 2 built in features, 1 being the pre-selected original file name (since you can't rename until you re- aquire focus for that window, thereby undoing the pre-selection programmed in) and 2, the ability to quickly save the file with a keystroke. A side note to this, ubuntu-bug should have an option to report bugs with other WITHOUT having to specify a package. This is a bug in ubuntu-bug. Not a feature. Because we don't always know what package(s) are involved. This needs to be addressed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.8 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 13 07:55:24 2022 InstallationDate: Installed on 2022-03-31 (12 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade 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/1968887/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog
This annoying bug rears its ugly head since I upgraded my own and my wifes computer to Ubuntu 22.04. This does not happen on my 18.04 laptop or 20.04 workbox. When using the Save As dialog, focus switches to the filter/search field in the dialog when we start typing a name for the file. The focus change happens after each character, so it's practically unusable. Confirmed with Firefox (snap), Google Chrome (PPA) and Brave (snap). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog Status in Mozilla Firefox: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome package in Ubuntu: Confirmed Status in xdg-desktop-portal-gtk package in Ubuntu: Confirmed Status in gtk+3.0 source package in Jammy: Confirmed Status in gtk4 source package in Jammy: Triaged Status in gtk+3.0 source package in Kinetic: Confirmed Status in gtk4 source package in Kinetic: Triaged Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1949340/+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 1997691] [NEW] libmysqlcppconn7v5: broken TLS configuration allows insecure connections without any warnings
Public bug reported: I wrote a small test program to test the client connectivity with libmysqlcppconn7v5 (tested on Ubuntu 20.04 LTS) to an up-to MariaDB server (Ubuntu 22.10 LTS). The MariaDB server was explicitly configured to not use TLS. The test client is configured to enforce TLS, i.e.: sql::ConnectOptionsMap connectionProperties; ... connectionProperties["sslVerify"] = true; connectionProperties["sslEnforce"]= true; Without any warning, it succeeds to connect to the insecure MariaDB server, i.e. leaving the connection insecure without any error or warning! Analysing the sources of libmysqlcppconn7v5 (libmysqlcppconn7v5-dev, i.e. mysql-connector-c++-1.1.12), I found a line where the option MYSQL_OPT_SSL_MODE (used by the underlying MySQL library) is explicitly commented out. Changing this seems to fix the issue: diff -r mysql-connector-c++-1.1.12.orig/driver/nativeapi/mysql_native_connection_wrapper.cpp mysql-connector-c++-1.1.12/driver/nativeapi/mysql_native_connection_wrapper.cpp 100c100 < //case sql::mysql::MYSQL_OPT_SSL_MODE: return ::MYSQL_OPT_SSL_MODE; --- > case sql::mysql::MYSQL_OPT_SSL_MODE: return ::MYSQL_OPT_SSL_MODE; That is, the client now, as intended, rejects the insecure connection. This bug is a major security issue, allowing MitM attacks on any client application using libmysqlcppconn7v5. ** Affects: mysql-connector-c++ (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public ** Package changed: firefox (Ubuntu) => mysql-connector-c++ (Ubuntu) ** Information type changed from Public to Public Security ** Attachment removed: "IpAddr.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632588/+files/IpAddr.txt ** Attachment removed: "IpRoute.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632589/+files/IpRoute.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632586/+files/CurrentDmesg.txt ** Attachment removed: "PulseList.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632596/+files/PulseList.txt ** Attachment removed: "Profile0Prefs.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632595/+files/Profile0Prefs.txt ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632585/+files/AlsaInfo.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632594/+files/ProcStatus.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632593/+files/ProcMaps.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632590/+files/Lspci.txt ** Attachment removed: "PciNetwork.txt" https://bugs.launchpad.net/ubuntu/+source/mysql-connector-c++/+bug/1997691/+attachment/5632591/+files/PciNetwork.txt ** Information type changed from Public Security to Public ** Description changed: I wrote a small test program to test the client connectivity with libmysqlcppconn7v5 (tested on Ubuntu 20.04 LTS) to an up-to MariaDB server (Ubuntu 22.10 LTS). The MariaDB server was explicitly configured to not use TLS. The test client is configured to enforce TLS, i.e.: sql::ConnectOptionsMap connectionProperties; ... connectionProperties["sslVerify"] = true; connectionProperties["sslEnforce"]= true; Without any warning, it succeeds to connect to the insecure MariaDB server, i.e. leaving the connection insecure without any error or warning! Analysing the sources of libmysqlcppconn7v5 (libmysqlcppconn7v5-dev, i.e. mysql-connector-c++-1.1.12), I found a line where the option MYSQL_OPT_SSL_MODE (used by the underlying MySQL library) is explicitly commented out. Changing this seems to fix the issue: diff -r mysql-connector-c++-1.1.12.orig/driver/nativeapi/mysql_native_connection_wrapper.cpp mysql-connector-c++-1.1.12/driver/nativeapi/mysql_native_connection_wrapper.cpp 100c100 < //case sql::mysql::MYSQL_OPT_SSL_MODE: return ::MYSQL_OPT_SSL_MODE; --- > case sql::mysql::MYSQL_OPT_SSL_MODE: return ::MYSQL_OPT_SSL_MODE; That is, the client now, as intended, rejects the insecure connection. This bug is a major security issue, allowing MitM attacks on any client application using libmysqlcppconn7v5. - - ProblemType: Bug - DistroRelease: Ubuntu 20.04 - Package: firefox 107.0+build2-0ubuntu0.20.04.1 - ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 - Uname: Linux 5.15.0-53-generic x86_64 - NonfreeKernelModules: nvidia_modeset nvidia - AddonCompatCheckDisabled: False - ApportVersion
[Desktop-packages] [Bug 1993594] Re: Scrolling in a view with many files is broken
Possibly related to https://gitlab.gnome.org/GNOME/gtk/-/issues/2971 -- 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/1993594 Title: Scrolling in a view with many files is broken Status in nautilus package in Ubuntu: New Bug description: Scrolling up and down in a Files window, in a directory with many files, the scrolling is erratic and seems to often jump to the bottom of the view. It happens only when scrolling while hovering the actual files (eg. using the mouse wheel). If hovering the scrollbar instead, there are no problems. The problem is bad enough, it's basically useless to get things done. Problem happens both in List View and Grid View ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 19 21:42:25 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)' InstallationDate: Installed on 2022-05-20 (152 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+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 1993594] Re: Scrolling in a view with many files is broken
** Attachment added: "Video showing problem. Using mouse wheel to ONLY scroll up." https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+attachment/5625351/+files/Screencast%20from%202022-10-19%2021-52-35.webm ** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2971 https://gitlab.gnome.org/GNOME/gtk/-/issues/2971 -- 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/1993594 Title: Scrolling in a view with many files is broken Status in nautilus package in Ubuntu: New Bug description: Scrolling up and down in a Files window, in a directory with many files, the scrolling is erratic and seems to often jump to the bottom of the view. It happens only when scrolling while hovering the actual files (eg. using the mouse wheel). If hovering the scrollbar instead, there are no problems. The problem is bad enough, it's basically useless to get things done. Problem happens both in List View and Grid View ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 19 21:42:25 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)' InstallationDate: Installed on 2022-05-20 (152 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+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 1993594] [NEW] Scrolling in a view with many files is broken
Public bug reported: Scrolling up and down in a Files window, in a directory with many files, the scrolling is erratic and seems to often jump to the bottom of the view. It happens only when scrolling while hovering the actual files (eg. using the mouse wheel). If hovering the scrollbar instead, there are no problems. The problem is bad enough, it's basically useless to get things done. Problem happens both in List View and Grid View ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 19 21:42:25 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)' InstallationDate: Installed on 2022-05-20 (152 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1993594 Title: Scrolling in a view with many files is broken Status in nautilus package in Ubuntu: New Bug description: Scrolling up and down in a Files window, in a directory with many files, the scrolling is erratic and seems to often jump to the bottom of the view. It happens only when scrolling while hovering the actual files (eg. using the mouse wheel). If hovering the scrollbar instead, there are no problems. The problem is bad enough, it's basically useless to get things done. Problem happens both in List View and Grid View ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Oct 19 21:42:25 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'search-filter-time-type' b"'created'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2179, 1167)' InstallationDate: Installed on 2022-05-20 (152 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-10-01 (18 days ago) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+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 1993359] Re: profile snap-update-ns.firefox is denied
Confirmed in QEMU 22.10 from the current ISO image at this time, LVM, no encryption. $ journalctl | grep denied | grep appa | grep fire Oct 18 20:09:51 teward-Standard-PC-Q35-ICH9-2009 audit[1248]: AVC apparmor="DENIED" operation="mkdir" class="file" profile="snap-update-ns.firefox" name="/usr/share/cups/doc-root/" pid=1248 comm="6" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Oct 18 20:09:51 teward-Standard-PC-Q35-ICH9-2009 kernel: audit: type=1400 audit(1666138191.488:56): apparmor="DENIED" operation="mkdir" class="file" profile="snap-update-ns.firefox" name="/usr/share/cups/doc-root/" pid=1248 comm="6" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Oct 18 20:09:51 teward-Standard-PC-Q35-ICH9-2009 audit[1248]: AVC apparmor="DENIED" operation="mkdir" class="file" profile="snap-update-ns.firefox" name="/usr/share/gimp/2.0/" pid=1248 comm="6" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Oct 18 20:09:51 teward-Standard-PC-Q35-ICH9-2009 audit[1248]: AVC apparmor="DENIED" operation="mkdir" class="file" profile="snap-update-ns.firefox" name="/usr/share/libreoffice/help/" pid=1248 comm="6" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 Oct 18 20:09:51 teward-Standard-PC-Q35-ICH9-2009 audit[1248]: AVC apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=1248 comm="6" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 (All firefox related apparmor items are visible at https://pastebin.ubuntu.com/p/jrwcBm62y7/ but I shortened to just the DENIED ones 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/1993359 Title: profile snap-update-ns.firefox is denied Status in firefox package in Ubuntu: Confirmed Bug description: profile snap-update-ns.firefox is denied on fresh kinetic boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1993359/+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 1990521] Re: Open gnome-terminal window not shown in favorite list
This is solved with gnome-shell 43.0-1ubuntu2 from kinetic. Feel free to close the bug. -- 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/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990521/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
This update makes it possible to connect to VPNs where the "cipher" (now
"data-ciphers") option is needed, as long as the connection is manually
modified. This part works great.
The Gnome settings interface however, still looks for the "cipher"
option, so this part does not work. The settings interface cannot see
the specified data-ciphers setting and trying to set it from the
interface, sets the cipher option instead, rendering the connection
unusable.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Fix Released
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1886653] Re: cups-pki-expired
I tried adding the option 'AllowExpiredCerts' and setting it 'true'. It did not change anything for me: The printer state is set to 'Stopped' with status message 'cups-pki-expired' as soon as I send a job. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1886653 Title: cups-pki-expired Status in cups package in Ubuntu: Confirmed Bug description: The printer always goes to stopped state in Ubuntu 20.04. Print properties window has status message saying: "cups-pki-expired". I have HP color laserjet m552, which Ubuntu discovers directly from the local network and configures automatically. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 7 14:40:00 2020 InstallationDate: Installed on 2019-11-03 (247 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for HP_Color_LaserJet_M552_5F80BF_: implicitclass://HP_Color_LaserJet_M552_5F80BF_/ MachineType: LENOVO 81H1 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=7f92666a-65f8-485e-b998-046c2c596aa5 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to focal on 2020-03-28 (100 days ago) dmi.bios.date: 08/17/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8PCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 530S-14ARR dmi.modalias: dmi:bvnLENOVO:bvr8PCN45WW:bd08/17/2018:svnLENOVO:pn81H1:pvrLenovoideapad530S-14ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad530S-14ARR: dmi.product.family: ideapad 530S-14ARR dmi.product.name: 81H1 dmi.product.sku: LENOVO_MT_81H1_BU_idea_FM_ideapad 530S-14ARR dmi.product.version: Lenovo ideapad 530S-14ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1886653/+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 1990521] Re: Open gnome-terminal window not shown in favorite list
Not sure if that is related, but I have a systemd override to make screen sharing working with google meet, google-chrome and a wayland session: $ cat ~/.config/systemd/user/gnome-terminal-server.service.d/override.conf [Service] Environment=GDK_BACKEND=x11 But that was already there before I upgraded to kinetic and it worked before. -- 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/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990521/+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 1990521] [NEW] Open gnome-terminal window not shown in favorite list
Public bug reported: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic third-party-packages wayland-session ** Attachment added: "gnome-terminal open application not showing in pinned icon" https://bugs.launchpad.net/bugs/1990521/+attachment/5618043/+files/gnome-terminal-pin.png -- 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/1990521 Title: Open gnome-terminal window not shown in favorite list Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: I have gnome-terminal pinned as favorite . But when I open a window, gnome-terminal is shown at the bottom instead of adding a red dot to the pinned icon. That only happens with gnome-terminal. Other applications (eg. Thunderbird, hexchat, emacs) do have the dot beside the pinned icon. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell-extension-ubuntu-dock 72ubuntu6 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 22 13:41:38 2022 InstallationDate: Installed on 2022-03-21 (184 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to kinetic on 2022-09-18 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1990521/+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 1990382] Re: [BPO] libreoffice 7.3.6 for bionic
Not all Autopkgtests have run and therefore you cannot claim they are all passing. This is marked Incomplete until you have provided evidence that all the autopkgtests and such clear for all supported architectures. ** Changed in: libreoffice (Ubuntu Bionic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1990382 Title: [BPO] libreoffice 7.3.6 for bionic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Bionic: Incomplete Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the processed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and a test build is currently available at https://launchpad.net/~libreoffice/+archive/ubuntu/experimental/+packages * Similar backport of 7.3.6 for focal handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418 * LibreOffice 6.0.7 (EOL since November 26, 2018) is currently released in bionic. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Bionci/18.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/amd64/libr/libreoffice/20220921_023821_f6636@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/arm64/libr/libreoffice/20220921_015824_12ef6@/log.gz * [armhf] ... * [i386] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/i386/libr/libreoffice/20220921_150152_8877b@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/ppc64el/libr/libreoffice/20220921_140441_6e26b@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-bionic-libreoffice-experimental/bionic/s390x/libr/libreoffice/20220921_134627_506c7@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1990382/+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 1989967] [NEW] Linux 5.15 for Ubuntu 20.04.5 cannot build nvidia-340 and let the default boot option unbootable
Public bug reported: Context: the computer is running nvidia-340 to workaround suspend bug happening when using nouveau. Since more than a year, the system isn't bootable with the default boot option because nvidia-340 can't be built against newer default kernels. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-46-generic Date: Fri Sep 16 15:36:14 2022 InstallationDate: Installed on 2021-07-02 (440 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1989967 Title: Linux 5.15 for Ubuntu 20.04.5 cannot build nvidia-340 and let the default boot option unbootable Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Context: the computer is running nvidia-340 to workaround suspend bug happening when using nouveau. Since more than a year, the system isn't bootable with the default boot option because nvidia-340 can't be built against newer default kernels. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.15.0-46-generic Date: Fri Sep 16 15:36:14 2022 InstallationDate: Installed on 2021-07-02 (440 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1989967/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
OK just doing due diligence. Approved for backports pocket, it'll need to build and publish then should be available afterwards. ** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418/+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 1989418] Re: [BPO] libreoffice 7.3.6 for focal
I'm confused, are you asking for a backport to the backports pocket or an SRU? The bug refers to SRU in multiple places. Backports in the backports pocket are NOT SRUs so its critical to identify which process and goal you have in mind - SRU or backport. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1989418 Title: [BPO] libreoffice 7.3.6 for focal Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Focal: In Progress Bug description: [Impact] * LibreOffice 7.3.6 is in its sixth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.6_release * This source packages matches the proposed SRU for jammy handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1988744 and its backport is currently provided by the LibreOffice Fresh PPA at https://launchpad.net/~libreoffice/+archive/ubuntu/ppa/+packages * Previous backport of 7.3.5 handled at https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1987045 * LibreOffice 6.4.7 (EOL since November 30, 2020) is currently released in focal. * LibreOffice 7.3.5 is currently released in focal-backports. * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Scope] * Backport of https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.6-0ubuntu0.22.04.1 * Backport target is Focal/20.04 LTS only to provide an official build of a more recent upstream version of LibreOffice [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1900/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/amd64/libr/libreoffice/20220904_103401_f46f5@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/arm64/libr/libreoffice/20220904_144020_84b5b@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/armhf/libr/libreoffice/20220904_113245_95845@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/ppc64el/libr/libreoffice/20220904_100953_3af7d@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-focal-libreoffice-libreoffice-prereleases/focal/s390x/libr/libreoffice/20220904_095636_d0c69@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 50 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1989418/+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 1961108] Re: network options greyed out in paprefs
Bug still exists in Kubuntu 22.04.1 and Pulseaudio 15.99
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1961108
Title:
network options greyed out in paprefs
Status in pulseaudio package in Ubuntu:
New
Bug description:
I installed Kubuntu 21.10 which comes with pulseaudio
1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
greyed out. The problem seems to be, that the directory with the
modules is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the
modules in /usr/lib/pulse-15.0
$ strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) =
-1 ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1
ENOENT (No such file or directory)
Creating a symlink /usr/lib/pulse-15.0 solves the problem
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1961108/+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 1987076] Re: Mouse cannot control windows after suspend and display change
lspci -k ** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610691/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987076 Title: Mouse cannot control windows after suspend and display change Status in mutter package in Ubuntu: Incomplete Bug description: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1987076] Re: Mouse cannot control windows after suspend and display change
journalctl -b0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610690/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987076 Title: Mouse cannot control windows after suspend and display change Status in mutter package in Ubuntu: Incomplete Bug description: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1987076] Re: Mouse cannot control windows after suspend and display change
Thanks for the directions... It's not that hard to reproduce here, I just have to move between places (or I could bring my other monitor closer, for more intense troubleshooting if need be). But it just happened... There are no recent crashes and nothing reported by whoopsie. The requested files are attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987076 Title: Mouse cannot control windows after suspend and display change Status in mutter package in Ubuntu: Incomplete Bug description: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1987076] [NEW] Mouse cannot control windows after suspend and display change
Public bug reported: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1987076 Title: Mouse cannot control windows after suspend and display change Status in mutter package in Ubuntu: New Bug description: My setup is this: Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland) Laptop: Lenovo ThinkPad P14s Gen 2a (AMD). Display: Lenovo T34w-20, connected via USB-C The problem started with upgrade to 22.04 I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10. Way I can usually reproduce (always?) 1. Suspend my laptop by yanking out the USB-C cable. 2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times. Note: Resuming on the same physical display does not seem to result in the same problem. After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful). I can navigate the windows and use the applications, using the keyboard. Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken". Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken". Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months). Please let me know what else I can provide you with, in order to get this fixed. :) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Fri Aug 19 10:32:48 2022 InstallationDate: Installed on 2022-05-20 (91 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+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 1979053] Re: UI glitches (coloured squares) in GTK application with AMDGPU
Ok, I created this issue: https://gitlab.freedesktop.org/drm/amd/-/issues/2088 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2088 https://gitlab.freedesktop.org/drm/amd/-/issues/2088 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1979053 Title: UI glitches (coloured squares) in GTK application with AMDGPU Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: stieler1622 F pulseaudio /dev/snd/pcmC3D0p: stieler1622 F...m pulseaudio /dev/snd/controlC2: stieler1622 F pulseaudio /dev/snd/controlC1: stieler1622 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: jammy DistroRelease: Ubuntu 22.04 DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Tul Corporation / PowerColor Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [148c:2402] InstallationDate: Installed on 2022-04-27 (55 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7B98 Package: mesa (not installed) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=2186bb5d-f2f0-4775-97ef-066ee5c2d05d ro quiet splash nosgx vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-39-generic N/A linux-backports-modules-5.15.0-39-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 RfKill: Tags: jammy ubuntu Uname: Linux 5.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.E1 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.E1:bd11/17/2021:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ub
[Desktop-packages] [Bug 1979053] Re: UI glitches in GTK application with AMDGPU
** Description changed: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: - The effect show up there, too. So it's than a problem of my actual + The effect shows up there, too. So it's not a problem of my specific installation. I will upload some Gimp screenshots, so you can see what I mean... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: - The effect shows up there, too. So it's not a problem of my specific + The effect show up there, too. So it's than a problem of my actual installation. I will upload some Gimp screenshots, so you can see what I mean... + + I'm not sure, but I tried to find the library used by all affected + application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe the problem is caused by a weird interaction between the AMDGPU X.Org driver (I use a Radeon RX5600XT) and GTK. But as the KDE desktop itself isn't affected and only GTK application show these glitches, I think it's not a general problem with AMDGPU. I also booted both Kubunutu and Ubuntu live images and installed Gimp: - The effect show up there, too. So it's than a problem of my actual + The effect shows up there, too. So it's not only a problem of my current installation. I will upload some Gimp screenshots, so you can see what I mean... I'm not sure, but I tried to find the library used by all affected application: Maybe it's libcairo2, maybe not... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcairo2 1.16.0-5ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35 Uname: Linux 5.15.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Jun 17 12:36:26 2022 InstallationDate: Installed on 2022-04-27 (50 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: cairo UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1979053 Title: UI glitches in GTK application with AMDGPU Status in cairo package in Ubuntu: New Bug description: After updating to (K)ubuntu 22.04, I see user interface glitches in GTK application. Most obviously affected is Gimp, but Evolution and Eclipse IDE are affected, too. The glitches don't appear on a notebook with Intel graphics, so maybe
[Desktop-packages] [Bug 1978340] [NEW] "flatpak run ..." fails with "bwrap: Can't get type of source /mnt: Permission denied"
Public bug reported: When I try to start a flatpak app, I get: $ flatpak run org.gnome.gitg bwrap: Can't get type of source /mnt: Permission denied error: Failed to sync with dbus proxy $ echo $? 1 I have: $ flatpak list Name Application ID Version BranchInstallation Freedesktop Platform org.freedesktop.Platform 21.08.1421.08 system Mesa org.freedesktop.Platform.GL.default21.3.8 21.08 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system GNOME Application Platform version 41 org.gnome.Platform 41system gitg org.gnome.gitg 41 stablesystem Yaru Gtk Themeorg.gtk.Gtk3theme.Yaru 3.22 system ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 20:08:35 2022 InstallationDate: Installed on 2022-03-21 (80 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-03-21 (80 days ago) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1978340 Title: "flatpak run ..." fails with "bwrap: Can't get type of source /mnt: Permission denied" Status in flatpak package in Ubuntu: New Bug description: When I try to start a flatpak app, I get: $ flatpak run org.gnome.gitg bwrap: Can't get type of source /mnt: Permission denied error: Failed to sync with dbus proxy $ echo $? 1 I have: $ flatpak list Name Application ID Version BranchInstallation Freedesktop Platform org.freedesktop.Platform 21.08.1421.08 system Mesa org.freedesktop.Platform.GL.default21.3.8 21.08 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system GNOME Application Platform version 41 org.gnome.Platform 41system gitg org.gnome.gitg 41 stablesystem Yaru Gtk Themeorg.gtk.Gtk3theme.Yaru 3.22 system ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 20:08:35 2022 InstallationDate: Installed on 2022-03-21 (80 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-03-21 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1978340/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can support Douglas' statement #17. I installed the fuse package on my fresh Ubuntu 22.04 and it caused the ubuntu-desktop and xdg-desktop-portal packages to be removed. After this, I started getting weird behavior when uploading files on Chrome. I submitted a bug report to the fuse package here: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1978310 Reinstalling the ubuntu-desktop-minimal package solved the issues I was having with Chrome. (I am running the minimal version of 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1884299] Re: Chromium snap won't run with nfs home drive
I get the same error "cannot open path of the current working directory: Permission denied" when trying to open a file located on a filesystem which is mounted with sshfs. This is the case for firefox and chromium-browser (both snaps), but not for google-chrome (not snap). This is on 22.04. It used to work fine for firefox in 21.10, when firefox was not a snap. -- 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/1884299 Title: Chromium snap won't run with nfs home drive Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: My physical computer lab uses AutoFS home drives (per https://help.ubuntu.com/community/Autofs#Wildcard_characters). If any user tries to run chromium browser, it fails. I assume it is related to these: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 But that says a fix was released, but seems toi only work for NFS home drives https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873 That ones is reported as a dupe but it's not, AutoFS home drives still don't work. $ chromium -v cannot create user data directory: /home/test.student2/snap/chromium/1193: Stale file handle $ tail -f /var/log/syslog Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 13 Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" $ lsb_release -rd Description: Ubuntu 20.04 LTS $ apt policy chromium-browser chromium-browser: Installed: 81.0.4044.129-0ubuntu0.20.04.1 Candidate: 81.0.4044.129-0ubuntu0.20.04.1 Version table: *** 81.0.4044.129-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 100 /var/lib/dpkg/status 80.0.3987.163-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+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 1973618] Re: can no longer open new windows after some time
I haven't been able to find other actual bugs/issues describing this issue, but there are threads on reddit and such that seem to indicate that this is a wayland/gnome42 issue, and that it affects all distributions. https://www.reddit.com/r/gnome/comments/ugpe12/firefox_on_gnome_42_cant_open_new_windows_after/ https://www.reddit.com/r/archlinux/comments/ugp9af/firefox_on_gnome_42_wayland_cant_create_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/1973618 Title: can no longer open new windows after some time Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: After some time using firefox, I can no longer open a new window. => ps -ef | grep -c firefox 21 => /snap/bin/firefox => ps -ef | grep -c firefox 21 There is no new process created and the window never appears. I can open new tabs, but when I drag the tab to make it a new window, it is never created. The only remedy is to restart firefox. Sometimes I need to SIGTERM all of the zombi processes. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 15 19:45:08 2022 InstallationDate: Installed on 2021-10-12 (215 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-04-22 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1973618/+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 1975421] [NEW] Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag
Public bug reported: running a fresh install of kubuntu 22.04 plymouth version: 0.9.5+git20211018-1ubuntu3 What should happen: Plymouth should totally cover all bootmessages (no bootmessages should be printed to console in the first place) What actually happens: When Plymouth quits the last 2-3 messages are visible on shutdown i get: [OK] Reached target Late Shutdown Services [OK] Finished System Power Off [OK] Reached target System Power off it seems to be absolutely impossible to hide all boot messages i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed) My Kernelparameters: fbcon=nodefer rd.systemd.show_status=false vt.global_cursor_default=0 quiet splash loglevel=3 rd.udev.log_level=3 What part of the system throws these messages ? i thought it is systemd? so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts and i edited the plymouth start and stop scripts and added -no-boot-log but plymouth totally ignores this flag and still logs everything to console and to /var/log/boot.log this defies the whole purpose of plymouth if plymouth itself spams the console with messages and if it's systemd why doesn't it respect the kernel parameters ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/1975421 Title: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag Status in plymouth package in Ubuntu: New Bug description: running a fresh install of kubuntu 22.04 plymouth version: 0.9.5+git20211018-1ubuntu3 What should happen: Plymouth should totally cover all bootmessages (no bootmessages should be printed to console in the first place) What actually happens: When Plymouth quits the last 2-3 messages are visible on shutdown i get: [OK] Reached target Late Shutdown Services [OK] Finished System Power Off [OK] Reached target System Power off it seems to be absolutely impossible to hide all boot messages i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed) My Kernelparameters: fbcon=nodefer rd.systemd.show_status=false vt.global_cursor_default=0 quiet splash loglevel=3 rd.udev.log_level=3 What part of the system throws these messages ? i thought it is systemd? so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts and i edited the plymouth start and stop scripts and added -no-boot- log but plymouth totally ignores this flag and still logs everything to console and to /var/log/boot.log this defies the whole purpose of plymouth if plymouth itself spams the console with messages and if it's systemd why doesn't it respect the kernel parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1975421/+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 604357] Re: Ubuntu's printing queue is not user friendly
With this issue I was facing another one issue like my hp docking system is not working. But after long time I found the best solution from this website: https://internettablettalk.com/fix-hp-docking-station-not-working/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/604357 Title: Ubuntu's printing queue is not user friendly Status in System Config Printer: New Status in system-config-printer package in Ubuntu: Confirmed Bug description: Binary package hint: system-config-printer-gnome The printing queue can make simple user's live quite hard for the following reasons: - It seems you can only delete one job at a time. If for some reason 400 wrong jobs were started, happy clicking. - You cannot delete jobs with the keyboard and need at least two clicks per job, - Command names are somewhat ambiguous. I have "Delete" and "Abort" for each job and they seem to do exactly the same thing. I propose the following solution: - We could make it possible to select multiple jobs so that you can delete them at once. - We could register a handler on the Del key to trigger job deletion. - We could remove one of the ambiguous entries in case they are equivalent. To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/604357/+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 1852474] Re: cups not printing if authentication required by server
Solved upstream with later versions of cups. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: Confirmed Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1852474/+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 1856187] Re: Cups wont print to smb-shared printer requiring user authentication via kerberos
Solved upstream with later versions of cups -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856187/+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 1971534] [NEW] connecting bluetooth devices fails
Public bug reported: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1971534 Title: connecting bluetooth devices fails Status in bluez package in Ubuntu: New Bug description: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1971534/+sub
[Desktop-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Unsure if this helps. I too have this issue with my university's wifi. I was able to work with one of the networking people in the tech center and we found that 22.04 would not even show up as attempting to connect on their end, (and we verified that 21.10 successfully connected as expected. Unsure how much this helps but I thought it would be useful information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Simon, I changed it to DEFAULT@SECLEVEL=0 and ran sudo systemctl restart wpa_supplicant.service, but unfortunately it did not make any difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)
Simon, I tried your suggestion followed by running sudo systemctl restart wpa_supplicant.service and I still am unable to connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network (e.g. eduroam) Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam
I am facing a similar problem after upgrading my Laptop from 21.10 to 22.04. I lost Wifi during the upgrade process, which also meant that refreshing the snap packages failed. But I was unable to connect to my Wifi again, even after reboot. I have a Unifi network set up for WPA enterprise, using a Let's encrypt certificate. It works fine on all my Windows machines and all machines on older Ubuntu. I tried the work-around in comment #22, but sadly it does not work for me. I am seeing an "internal error" in syslog: Apr 23 10:41:31 thomas-laptop wpa_supplicant[3116]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error Apr 23 10:41:31 thomas-laptop wpa_supplicant[3116]: OpenSSL: openssl_handshake - SSL_connect error:0A0C0103:SSL routines::internal error Apr 23 10:41:32 thomas-laptop wpa_supplicant[3116]: wlp0s20f3: CTRL-EVENT-EAP-FAILURE EAP authentication failed Apr 23 10:41:32 thomas-laptop kernel: [ 431.697248] wlp0s20f3: deauthenticated from xx:xx:xx:xx:xx:xx (Reason: 23=IEEE8021X_FAILED) I attached my full /var/log/syslog output. ** Attachment added: "wpa-auth-error.log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+attachment/5582874/+files/wpa-auth-error.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: "Connection failed" for WPA Enterprise network eduroam Status in wpa package in Ubuntu: Confirmed Status in wpa source package in Jammy: Confirmed Bug description: With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1854183] Re: when compiz have enabled gtk-window-decorator libreoffice-calc show transparent window
** Package changed: libreoffice (Unity Linux) => libreoffice (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1854183 Title: when compiz have enabled gtk-window-decorator libreoffice-calc show transparent window Status in Compiz: New Status in libreoffice package in Ubuntu: Unknown Bug description: ubuntu 20.04 Compiz 0.9.14.0 Libreoffice 6.3 from repo LIbreoffice 6.4 from document fundation Description: when compiz have enabled gtk-window-decorator, libreoffice apliction show transparent window To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1854183/+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 1968875] [NEW] Bluetooth devices disconnect, connect, disconnect
Public bug reported: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: New Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1947210] Re: Firefox Snap can't copy&paste or drag&drop in Wayland
Still a problem here. I'm on 22.04 with all updates (including proposed) installed, latest firefox snap (99.0-2, rev 1188). -- 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/1947210 Title: Firefox Snap can't copy&paste or drag&drop in Wayland Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: I just upgraded to 21.10 Impish which supplies Firefox 93.0-1 via snap. I could not copy and paste to and from the browser. I logged out of Wayland and into Xorg and copy & paste works. Already reported at https://bugzilla.mozilla.org/show_bug.cgi?id=1729901 so it's a known issue. I wanted to report it here so it gets into the Impish release notes or wherever along with the workaround. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+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 1968004] Re: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail
recreating the account worked (after the login.ubuntu.com page, I got redirected to the accounts.google.com page to allow thunderbird to access mail & calendar, that was not happening with my existing account after the package update) -- 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/1968004 Title: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail Status in thunderbird package in Ubuntu: New Bug description: Since the latest update: Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1) End-Date: 2022-04-05 06:36:02 Thunderbird opens a new window (title is "Enter credentials for thomas.becht...@canonical.com on imap.gmail.com", url is https://login.ubuntu.com) when I select any new message in thunderbird. Even if I do login, nothing happens and the page reopens when I select another message. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.8.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BuildID: 20220401203107 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:05:04 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-03-21 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.8.0/20220401203107 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to jammy on 2022-03-21 (15 days ago) dmi.bios.date: 12/23/2021 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET68W(1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnLENOVO:bvrR1BET68W(1.37):bd12/23/2021:br1.37:efr1.37:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1968004/+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 1968004] [NEW] Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail
Public bug reported: Since the latest update: Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1) End-Date: 2022-04-05 06:36:02 Thunderbird opens a new window (title is "Enter credentials for thomas.becht...@canonical.com on imap.gmail.com", url is https://login.ubuntu.com) when I select any new message in thunderbird. Even if I do login, nothing happens and the page reopens when I select another message. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.8.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BuildID: 20220401203107 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:05:04 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-03-21 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.8.0/20220401203107 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to jammy on 2022-03-21 (15 days ago) dmi.bios.date: 12/23/2021 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET68W(1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.37 dmi.modalias: dmi:bvnLENOVO:bvrR1BET68W(1.37):bd12/23/2021:br1.37:efr1.37:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1968004 Title: Thunderbird opens new window (login.ubuntu.com for me) when trying to open any mail Status in thunderbird package in Ubuntu: New Bug description: Since the latest update: Upgrade: thunderbird:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1), thunderbird-gnome-support:amd64 (1:91.7.0+build2-0ubuntu1, 1:91.8.0+build2-0ubuntu1) End-Date: 2022-04-05 06:36:02 Thunderbird opens a new window (title is "Enter credentials for thomas.becht...@canonical.com on imap.gmail.com", url is https://login.ubuntu.com) when I select any new message in thunderbird. Even if I do login, nothing happens and the page reopens when I select another message. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.8.0+build2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 BuildID: 20220401203107 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 10:05:04 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Inst
[Desktop-packages] [Bug 1967768] [NEW] can not start libreoffice: execv failed: No such file or directory
Public bug reported: I'm trying to execute libreoffice: tom@melisse:~$ libreoffice.writer execv failed: No such file or directory tom@melisse:~$ snap list|grep libreoffice libreoffice 7.3.2.2 250latest/stable canonical* - tom@melisse:~$ ls /snap/libreoffice/2 247/ 250/ tom@melisse:~$ ls /snap/libreoffice/250/ config/ etc/ gnome-platform/ lib/ meta/usr/ data-dir/filebug.py javasettings.py libreoffice.wrapper snap/var/ tom@melisse:~$ ls /snap/libreoffice/250/ config data-dir etc filebug.py gnome-platform javasettings.py lib libreoffice.wrapper meta snap usr var tom@melisse:~$ ls /snap/libreoffice/250/usr/bin/ tom@melisse:~$ ls /snap/libreoffice/250/usr/sbin/ update-java-alternatives tom@melisse:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 17:11:19 2022 InstallationDate: Installed on 2022-03-21 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap: libreoffice 7.3.2.2 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 61 Done2022-04-04T06:42:42+02:00 2022-04-04T06:43:21+02:00 Auto-refresh snaps "libreoffice", "openstackclients" SnapSource: ubuntu/+source/libreoffice UpgradeStatus: Upgraded to jammy on 2022-03-21 (13 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy snap wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1967768 Title: can not start libreoffice: execv failed: No such file or directory Status in libreoffice package in Ubuntu: New Bug description: I'm trying to execute libreoffice: tom@melisse:~$ libreoffice.writer execv failed: No such file or directory tom@melisse:~$ snap list|grep libreoffice libreoffice 7.3.2.2 250latest/stable canonical* - tom@melisse:~$ ls /snap/libreoffice/2 247/ 250/ tom@melisse:~$ ls /snap/libreoffice/250/ config/ etc/ gnome-platform/ lib/ meta/usr/ data-dir/filebug.py javasettings.py libreoffice.wrapper snap/var/ tom@melisse:~$ ls /snap/libreoffice/250/ config data-dir etc filebug.py gnome-platform javasettings.py lib libreoffice.wrapper meta snap usr var tom@melisse:~$ ls /snap/libreoffice/250/usr/bin/ tom@melisse:~$ ls /snap/libreoffice/250/usr/sbin/ update-java-alternatives tom@melisse:~$ ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 4 17:11:19 2022 InstallationDate: Installed on 2022-03-21 (13 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap: libreoffice 7.3.2.2 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 61 Done2022-04-04T06:42:42+02:00 2022-04-04T06:43:21+02:00 Auto-refresh snaps "libreoffice", "openstackclients" SnapSource: ubuntu/+source/libreoffice UpgradeStatus: Upgraded to jammy on 2022-03-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1967768/+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 1967235] Re: Can not trash files in other partitions
There are rumors that a Trash existent directory like .Trash-th might help in this specific partition/mount but it does not help. -- 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/1967235 Title: Can not trash files in other partitions Status in nautilus package in Ubuntu: New Bug description: I know this is an old one, but this is still present, either it is a regression or not. Files in another partition than home can only be deleted but not moved to Trash, even if the whole partition has writing allowed for the current user. How to reproduce: USER=th mkdir /home/th/shim sudo mkdir /mnt/shim sudo mount -o bind /home/th/shim cd /mnt/shim touch ttt nautilus /mnt/shim Now trashing ttt fails. However trashing when in /home/th/shim it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Mar 31 09:27:36 2022 InstallationDate: Installed on 2019-12-19 (832 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/ubuntu/+source/nautilus/+bug/1967235/+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 1967235] [NEW] Can not trash files in other partitions
Public bug reported: I know this is an old one, but this is still present, either it is a regression or not. Files in another partition than home can only be deleted but not moved to Trash, even if the whole partition has writing allowed for the current user. How to reproduce: USER=th mkdir /home/th/shim sudo mkdir /mnt/shim sudo mount -o bind /home/th/shim cd /mnt/shim touch ttt nautilus /mnt/shim Now trashing ttt fails. However trashing when in /home/th/shim it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Mar 31 09:27:36 2022 InstallationDate: Installed on 2019-12-19 (832 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1967235 Title: Can not trash files in other partitions Status in nautilus package in Ubuntu: New Bug description: I know this is an old one, but this is still present, either it is a regression or not. Files in another partition than home can only be deleted but not moved to Trash, even if the whole partition has writing allowed for the current user. How to reproduce: USER=th mkdir /home/th/shim sudo mkdir /mnt/shim sudo mount -o bind /home/th/shim cd /mnt/shim touch ttt nautilus /mnt/shim Now trashing ttt fails. However trashing when in /home/th/shim it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Mar 31 09:27:36 2022 InstallationDate: Installed on 2019-12-19 (832 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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/ubuntu/+source/nautilus/+bug/1967235/+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 1425000] Re: Cannot set right monitor as primary in dual monitor configuration
I'm on 20.04 and this is still an issue for me. I know this bug is considered invalid and won't be fixed, but is there still hope this can be fixed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1425000 Title: Cannot set right monitor as primary in dual monitor configuration Status in unity-control-center package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Won't Fix Status in xfwm4 package in Ubuntu: Invalid Bug description: Unity always considers the left monitor as the default/primary one when in a dual-monitor configuration. By this I mean that: - Desktop icons appear only on the left monitor - An opened app (eg libreoffice writer) is opened on the left screen, even if I launch it via the launcher on the right monitor The current configuration can be seen at http://i286.photobucket.com/albums/ll86/wild_oscar/Screenshotfrom2015-02-24100853.png The .config/monitors.xml file is shown below. Notice that the HDMI display (green in the photo) is set asyes. Nevertheless, this seems to be ignored - the behaviour is the one mentioned above (desktop icons on the left and writer opening on the left) . no GSM 0x4b7a 0xb13b 1440 900 60 0 0 normal no no no GSM 0x5a26 0x0008976f 1920 1080 60 1440 0 normal no no yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1425000/+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 1961852] [NEW] PRIME profiles is missing in nvidia-settings
Public bug reported: Usually I used the on-demand profile. Somehow this is gone in latest 510 version. I also tried 460 but no success. I only can switch between internal graphics and nvidia. (Power Saving and Performance). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.16~0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 23 00:56:00 2022 Dependencies: InstallationDate: Installed on 2019-12-19 (796 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot_2022-02-23_01-00-47.png" https://bugs.launchpad.net/bugs/1961852/+attachment/5562852/+files/Screenshot_2022-02-23_01-00-47.png -- 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/1961852 Title: PRIME profiles is missing in nvidia-settings Status in nvidia-prime package in Ubuntu: New Bug description: Usually I used the on-demand profile. Somehow this is gone in latest 510 version. I also tried 460 but no success. I only can switch between internal graphics and nvidia. (Power Saving and Performance). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-prime 0.8.16~0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Wed Feb 23 00:56:00 2022 Dependencies: InstallationDate: Installed on 2019-12-19 (796 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1961852/+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
