[Desktop-packages] [Bug 1990024] [NEW] screenshot a window captures also a large border
Public bug reported: Using screenshot to capture a window the screenshot contains also a large border. This not happen selecting an area. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 17 07:30:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Screenshot from 2022-09-17 07-27-05.png" https://bugs.launchpad.net/bugs/1990024/+attachment/5616624/+files/Screenshot%20from%202022-09-17%2007-27-05.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1990024 Title: screenshot a window captures also a large border Status in gnome-shell package in Ubuntu: New Bug description: Using screenshot to capture a window the screenshot contains also a large border. This not happen selecting an area. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 17 07:30:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1990024/+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 1981996] Re: Remmina external tools not working
[Expired for remmina (Ubuntu) because there has been no activity for 60 days.] ** Changed in: remmina (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1981996 Title: Remmina external tools not working Status in remmina package in Ubuntu: Expired Bug description: Remmina external tools is not work well. If i run Remmina on terminal i can see the output in the terminal, but when i run Remmina from the menu it does not open a windows like before. It worked well in Ubuntu 18.04. I have "terminator" installed and configured as "x-terminal-emulator". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: remmina-common 1.4.25+dfsg-1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 18 10:51:24 2022 InstallationDate: Installed on 2022-06-02 (45 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1981996/+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 1990010] Re: VA error: resource allocation failed
I added logging of the unsupported modifier value.
This is the value that it fails on:
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:379: Unsupported
modifier: 0x108
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
New
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1990010/+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 1500307] Re: xubuntu does not disable gtk overlay scrollbars (i.e. use solid scrollbars)
Closing as won't fix. This won't be addressed by Xubuntu. ** Changed in: xubuntu-default-settings (Ubuntu) Status: Opinion => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1500307 Title: xubuntu does not disable gtk overlay scrollbars (i.e. use solid scrollbars) Status in One Hundred Papercuts: Confirmed Status in PolicyKit: Won't Fix Status in policykit-1 package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: Won't Fix Bug description: xubuntu does not disable gtk overlay scrollbars (i.e. use solid scrollbars) On this page http://tracker.xubuntu.org/ in the source code, Sean Davis is assigned to disable gtk3.16 overlay scrollbars in xubuntu- default-settings (i.e. use solid scrollbars) and https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-w-development shows also that the work is done. I am running xubuntu 15.10 beta 2 and this is not the case. Opening up ubuntu-modified programmes shows solid scrollbars (like the non-csd-ized, non-header-bar-ized evince), but synaptic shows overlay scrollbars. I find it very annoying. There is no visual clue of a scrollbar until I move my mouse over the window, and unlike Android or iOS scrollbars, the width changes and the transparency changes depending on how close my mouse is. Very hard to use. Please fix. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xubuntu-default-settings 15.10.3 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.365 CurrentDesktop: XFCE Date: Mon Sep 28 04:43:49 2015 LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xubuntu-default-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1500307/+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 1989821] Re: Firefox hangs, unable to reload tabs for up to 2min after switching to session that was idle for several hours
** Description changed: I am not sure when exactly this started. I feel like it was around FF v99. System is always on. 2 user accounts (mine, wife's). We keep the desktop sessions logged-in, just switch between accounts whenever needed. Firefox stays open since it's heavily used. When an active session is unlocked or switched to after being unused for several hours (not rigorously measured but I'd say more than 6-8 hours), we observe the following behavior in Firefox: - * Gmail tab will show a message at the top of the page along the lines of "encountered a problem, retrying in 3:00" with the timer counting down + * Gmail tab will show a message at the top of the page along the lines of "Not connected, retrying in 3:00" with the timer counting down * For the first 10-20s, clicking on another tab will have no effect - FF doesn't switch to the tab * From 20s to between 1-2 minutes: - Switching tabs will work albeit slowly. - Reloading an existing tab does nothing except cause the side-to-side loading indicator on the tab to cycle - I am able to open a new tab via ctrl-T - I can enter a URL into a new tab, but the site doesn't load. The loading indicator cycles in the tab title. - I cannot open about:performance to troubleshoot After some period of time, as short as 30-40s and as long as 2 minutes, FF becomes usable again. Sites can be loaded/reloaded, etc. What I have tried, but has not resolved the issue: * Restart FF in troubleshooting mode * Upgrade to new releases as they are available in the package manager * Run in non-troubleshooting mode but with all extensions removed * Refresh the browser * Set browser.tabs.unloadOnLowMemory = false * rm -rf ~/.mozilla and start with a fresh profile Workaround: killall -9 firefox, then relaunch firefox Again, this seems to have started suddenly at some point possibly around the v99 timeframe. Prior to that, I did not observe this problem. Hardware, and to the best of my knowledge the usage habits of the 2 users, have not changed in quite some time. I've attached the output of a "vmstat 1" command that I launched when I unlocked a session that was idle for approximately 40h, before interacting with the existing firefox session. The firefox issue manifested for about 1min 20s. Once firefox became usable, I stopped the vmstat command. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-124.140-generic 5.4.195 Uname: Linux 5.4.0-124-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tyr 743015 F pulseaudio /dev/snd/controlC1: tyr 743015 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: XFCE Date: Thu Sep 15 18:38:25 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-01-05 (2444 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.100 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:302 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=104.0/20220818191623 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2021-02-04 (588 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS -- 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/1989821 Title: Firefox hangs, unable to reload tabs for up to 2min
[Desktop-packages] [Bug 1966436] Re: Bluetooth fails to connect "br-connection-profile-unavailable"
Thanks for this - I couldn't pair a simple Bluetooth speaker on 22.04 upgraded from 22.04. I didn't even know that pipewire was a thing nor that it crept in. Now it's working well, hopefully my JACK configuration will continue to work well as well... -- 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/1966436 Title: Bluetooth fails to connect "br-connection-profile-unavailable" Status in bluez package in Ubuntu: Invalid Status in pipewire package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: How to reproduce: > bluetoothctl scan on Discovery started ... > bluetoothctl connect 94:DB:56:8E:0B:96 Attempting to connect to 94:DB:56:8E:0B:96 Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable > systemctl status bluetooth bluetooth.service - Bluetooth service Loaded: loaded ... mars 25 12:39:08 ncelrnd2375 bluetoothd[1282]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for 94:DB:56:8E:0B:96: Protocol not available Notes: kernel-5.15, bluez-5.64 Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth Dell Precision 3560 Unfortunately I did not test before upgrade to 22.04. Tried installing pipewire-pulse, blueman, but this is lower-level. There are reports of similar errors popping up in Arch and Manjaro recently: https://bbs.archlinux.org/viewtopic.php?id=270465 https://forum.manjaro.org/t/bluetooth-ko-with-kernel-5-16/99913 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 25 12:56:34 2022 InstallationDate: Installed on 2022-03-04 (21 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Precision 3560 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic root=/dev/mapper/AmadeUbuntu20-root ro audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to jammy on 2022-03-22 (3 days ago) dmi.bios.date: 09/13/2021 dmi.bios.release: 1.12 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.2 dmi.board.name: 095HH7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.2:bd09/13/2021:br1.12:svnDellInc.:pnPrecision3560:pvr:rvnDellInc.:rn095HH7:rvrA00:cvnDellInc.:ct10:cvr:sku0A22: dmi.product.family: Precision dmi.product.name: Precision 3560 dmi.product.sku: 0A22 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 44:E5:17:BC:00:DD ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:24189 acl:41 sco:0 events:519 errors:0 TX bytes:8252 acl:33 sco:0 commands:239 errors:0 modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1966436/+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 1989217] Re: Please remove mozjs91 from Ubuntu 22.10
Removing packages from kinetic: mozjs91 91.13.0-1 in kinetic libmozjs-91-0 91.13.0-1 in kinetic amd64 libmozjs-91-0 91.13.0-1 in kinetic arm64 libmozjs-91-0 91.13.0-1 in kinetic armhf libmozjs-91-0 91.13.0-1 in kinetic i386 libmozjs-91-0 91.13.0-1 in kinetic ppc64el libmozjs-91-0 91.13.0-1 in kinetic riscv64 libmozjs-91-0 91.13.0-1 in kinetic s390x libmozjs-91-dev 91.13.0-1 in kinetic amd64 libmozjs-91-dev 91.13.0-1 in kinetic arm64 libmozjs-91-dev 91.13.0-1 in kinetic armhf libmozjs-91-dev 91.13.0-1 in kinetic i386 libmozjs-91-dev 91.13.0-1 in kinetic ppc64el libmozjs-91-dev 91.13.0-1 in kinetic riscv64 libmozjs-91-dev 91.13.0-1 in kinetic s390x Comment: No revdeps, obsoleted by mozjs102; LP: #1989217 1 package successfully removed. ** Changed in: mozjs91 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs91 in Ubuntu. https://bugs.launchpad.net/bugs/1989217 Title: Please remove mozjs91 from Ubuntu 22.10 Status in mozjs91 package in Ubuntu: Fix Released Bug description: mozjs is the SpiderMonkey JavaScript engine from Firefox ESR. Firefox ESR 91 has reached End of Life. mozjs91 has no remaining dependencies in Ubuntu 22.10 and is a security sensitive library, so let's remove it from Ubuntu 22.10. The replacement is mozjs102. mozjs91 is temporarily still in Debian because mozjs102 doesn't build on armel. Debian is likely to just drop GNOME Shell and related packages from armel "soon". $ reverse-depends src:mozjs91 No reverse dependencies found $ reverse-depends -b src:mozjs91 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs91/+bug/1989217/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
This bug was fixed in the package mutter - 43~rc-2ubuntu2 --- mutter (43~rc-2ubuntu2) kinetic; urgency=medium * Ignore build test failures on s390x -- Jeremy Bicha Tue, 13 Sep 2022 11:43:54 -0400 ** Changed in: mutter (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 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 and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1988625] Re: Left-over cursor visible on second screen
This bug was fixed in the package mutter - 43~rc-2ubuntu2 --- mutter (43~rc-2ubuntu2) kinetic; urgency=medium * Ignore build test failures on s390x -- Jeremy Bicha Tue, 13 Sep 2022 11:43:54 -0400 ** Changed in: mutter (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- 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/1988625 Title: Left-over cursor visible on second screen Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] When I move my mouse between screens, every once in a while a leftover cursor remains on the screen I just left. Moving to that screen again fixes. [ Test Plan ] 1. Set up a dual-monitor system using open source graphics drivers only. 2. Log into a Wayland session (usually just "Ubuntu"). 3. Wiggle the mouse between the two monitors. Expect: The mouse pointer never gets left behind and frozen on the previous monitor. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] This sounds like (Fix Released) #1724977, but seems to happen on extra screens. It may be related to different scales of my two displays (100% vs. 200%). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~beta-1ubuntu2 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.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 3 11:51:47 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (2 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 43~beta-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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 1975823] Re: pipewire alsa blocks after initial buffer size of data got written
** Changed in: pipewire (Debian) Status: Fix Committed => Fix Released -- 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/1975823 Title: pipewire alsa blocks after initial buffer size of data got written Status in pipewire package in Ubuntu: Triaged Status in pipewire package in Debian: Fix Released Bug description: I have this bug also if I install pipewire manaully on focal and jammy. I use a Java Application using the javax.sound package to get a output to the AudioSystem. I have an own Java library using the same and I poked around a bit: It uses Alsa as Output. The line object Java provides has the possibility to ask for the available bytes in the buffer. Normally with pulseaudio you can see the buffer getting filled and then, as the audio get's played back, recovering by the played back bytes amount. With pipewire-pulse on the other hand it just fills the buffer and reporting no more available bytes. But it plays back the bytes successfully written to the buffer. Meaning its unable to write more, as the available buffer size never recovers, even though the already written ones have been played just fine. I have checked the behavior also on Debain-testing, Manjaro and Fedora. Fedora is the only distro without this problem. Fedora has the package pipewire-alsa in its repositories and installed, which is not available on the other distros. If I have understood it correctly, the alsa functionality should be included into the default pipewire-pulse now, but for some reason fedora decided to keep the extra package? So I'd really like to see pipewire-pulse being the default in the future, but this has to be fixed somehow. For reference, here's an issue on the pipewire gitlab I've filed already about this: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2255 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: pipewire-pulse 0.3.48-1ubuntu1 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: Thu May 26 14:58:40 2022 InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: pipewire UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1975823/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
This bug was fixed in the package fonts-noto-color-emoji - 2.038-1 --- fonts-noto-color-emoji (2.038-1) unstable; urgency=medium * New upstream release (LP: #1989626) - This major update introduces support for the Unicode 15 standard https://blog.emojipedia.org/whats-new-in-unicode-15-0/ * Bump minimum nototools * Bump Standards-Version to 4.6.1 -- Jeremy Bicha Fri, 16 Sep 2022 07:19:16 -0400 ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: Triaged => Fix Released -- 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/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Triaged Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - node-unicode-data utf8proc maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+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 1980545] Re: Update evolution-data-server to 3.44.4
I installed evolution-data-server 3.44.4-0ubuntu1 on Ubuntu 22.04 LTS and verified that both GNOME Calendar and Evolution are still working correctly. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1980545 Title: Update evolution-data-server to 3.44.4 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.4/NEWS The current version in Ubuntu 22.04 LTS is 3.44.2. Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Jammy: Confirmed Status in ubuntu-settings source package in Kinetic: Fix Released Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
Ludovic, We'll get a fresh install up and running and provide the output you have requested. -- 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/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Changed in: ubuntu-seeds Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Jammy: Confirmed Status in ubuntu-settings source package in Kinetic: Fix Released Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
** Changed in: ubuntu-seeds Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: Fix Committed Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Jammy: New Status in ubuntu-settings source package in Kinetic: Fix Released Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1990005] Re: Visible columns option missing function
Thank, that should be reported upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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 1990005] Re: Visible columns option missing function
** Attachment removed: "nautilus-columns.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+attachment/5616600/+files/nautilus-columns.txt -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?
Sadly, that wasn't it... still does the same (Only at start from "cold"? is it?) -- 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/1988658 Title: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize? Status in pulseaudio package in Ubuntu: New Bug description: $ cat /etc/os-release NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal 3 to 5 of 10 boot occasions stops prematurely. dmesg (included here, I assume) indicates a pulseaudio failure stopping the booting. I have NOT investigated further (knowledge limit). This very latest bootup seemed to indicate that there is something waiting on the keyboard, as I got all the way "up" after beating repeatedly - alternating - on ESC and ENTER --- dmesg tail on this boot --- 4 sec pause from previous line (at 9 secs) [ 13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 13.444031] usb usb3: root hub lost power or was reset [ 13.444032] usb usb4: root hub lost power or was reset [ 13.557170] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61) [ 17.001076] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 17.105681] rfkill: input handler disabled [ 28.694324] Bluetooth: RFCOMM TTY layer initialized [ 28.694328] Bluetooth: RFCOMM socket layer initialized [ 28.694331] Bluetooth: RFCOMM ver 1.11 [ 28.922797] rfkill: input handler enabled [ 29.043050] Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [ 31.669031] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 31.907300] rfkill: input handler disabled [ 41.959736] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 78.940840] usb usb3: root hub lost power or was reset [ 78.940841] usb usb4: root hub lost power or was reset [ 929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit [ 929.174669] usb usb3: root hub lost power or was reset [ 929.174671] usb usb4: root hub lost power or was reset -- end --- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.13 ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Sun Sep 4 08:19:01 2022 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: G731GU.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G731GU 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.ec.firmware.release: 0.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G731GU_G731GU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1989726] Re: Only a quarter of the screen showing in VirtualBox
gnome-2048 is a 'sliding tile puzzle game' which doesn't seem appropriate looking at your screenshot and reading the bug description. I'm moving this to gnome-shell which will bring this bug report to the attention of the Desktop Team. ** Package changed: gnome-2048 (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: jammy -- 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/1989726 Title: Only a quarter of the screen showing in VirtualBox Status in gnome-shell package in Ubuntu: New Bug description: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989726/+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 1990010] [NEW] VA error: resource allocation failed
Public bug reported:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and a
snap built from source.
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[389969:389969:0916/112615.469140:ERROR:vaapi_video_decode_accelerator.cc(129)]
{"code":6,"data":{},"group":"VaapiStatusCode","message":"","stack":[{"file":"media/gpu/vaapi/vaapi_picture_native_pixmap_ozone.cc","line":67}]}
[390012:14:0916/112615.469740:INFO:decoder.cc(32)] VpxVideoDecoder
[390012:14:0916/112615.470169:INFO:decoder.cc(44)] Dav1dVideoDecoder
[390012:14:0916/112615.471713:INFO:decoder.cc(29)] FFmpegVideoDecoder
[390012:14:0916/112615.471819:INFO:decoder.cc(29)] FFmpegVideoDecoder
Note the message: "DdiMediaUtil_AllocateSurface:378: Unsupported
modifier."
I am on wayland, and use these chromium flags:
export CHROMIUM_FLAGS="--enable-logging=stderr --use-gl=egl --enable-
features=VaapiVideoDecoder,VaapiVideoEncoder --disable-
features=UseChromeOSDirectVideoDecoder --ignore-gpu-blocklist --disable-
gpu-driver-bug-workaround --ozone-platform=wayland"
The video that fails: the 1080p/60 version downloaded from here:
https://github.com/chthomos/video-media-samples/
I will figure out which is the "unsupported modifier" and report back,
here.
Note: currently gmmlib and media-driver have failing debug builds, but I have
created pull requests to both:
https://github.com/intel/media-driver/pull/1491
https://github.com/intel/gmmlib/pull/97
CPU: 12600k
GPU: Intel Alderlake_s (Gen12)
Snap built with: core20
Host OS: Ubuntu Kinetic
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
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/1990010
Title:
VA error: resource allocation failed
Status in chromium-browser package in Ubuntu:
New
Bug description:
When I play a H264/AAC video with HW decoding enabled on Alderlake
12600k, I get the error:
vaCreateSurfaces (import mode) failed, VA error: resource allocation
failed
After which, chromium will proceed to play the video without HW
acceleration using ffmpeg.
This is both with using the pre-built snap from channel beta/hwacc and
a snap built from source.
To get more information on this VA error, I built the snap with debug
versions of gmmlib and media-driver (latest git) using the latest git
from valib as well.
The log output from chromium now mentions why the allocation fails:
[390012:14:0916/112615.428584:INFO:decoder.cc(41)] DecryptingVideoDecoder
[389969:390095:0916/112615.445970:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449426:INFO:decoder.cc(65)] VDAVideoDecoder
[390012:14:0916/112615.449500:INFO:decoder.cc(65)] VDAVideoDecoder
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.467062:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.467212:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[LIBVA]:CRITICAL - DdiMediaUtil_AllocateSurface:378: Unsupported modifier.
[389969:389969:0916/112615.468871:ERROR:vaapi_wrapper.cc(2389)]
vaCreateSurfaces (import mode) failed, VA error: resource allocation failed
[389969:389969:0916/112615.468987:ERROR:vaapi_picture_native_pixmap_ozone.cc(66)]
Failed creating VASurface for NativePixmap
[Desktop-packages] [Bug 1989726] [NEW] Only a quarter of the screen showing in VirtualBox
You have been subscribed to a public bug: Only the top left quarter of my Ubuntu 22.04.1 desktop is showing on VirtualBox 6.1.30. I've installed Guest Additions CD. apt updated and restarted twice. I've tried Xubuntu and Kubuntu 22.04 and they both work without any errors. Screenshot here: https://i.stack.imgur.com/KI0YO.png ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Only a quarter of the screen showing in VirtualBox https://bugs.launchpad.net/bugs/1989726 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989656] Re: Unable to logout or switch user on Ubuntu 22.04
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Tags added: jammy -- 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/1989656 Title: Unable to logout or switch user on Ubuntu 22.04 Status in gnome-shell package in Ubuntu: New Bug description: - Whenever attempting to logout user or switch user, process is stuck on a black blank screen with flickering horizontal cursor. Have to restart pc to exit state. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989656/+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 1989656] [NEW] Unable to logout or switch user on Ubuntu 22.04
You have been subscribed to a public bug: - Whenever attempting to logout user or switch user, process is stuck on a black blank screen with flickering horizontal cursor. Have to restart pc to exit state. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- Unable to logout or switch user on Ubuntu 22.04 https://bugs.launchpad.net/bugs/1989656 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989676] Re: Save As dialog cannot receive focus
This bug has reported against evince, a document viewer, but Firefox seems to be the intended application so moving... ** Package changed: evince (Ubuntu) => firefox (Ubuntu) ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1989676 Title: Save As dialog cannot receive focus Status in firefox package in Ubuntu: New Bug description: How to reproduce: 1. Open firefox 2. Ctrl+s Expected behavior: The "Save As" dialog opens. I can edit the file name, click on the left-side menu to change directory, click on the save button, close the dialog. Bug: The "Save As" dialog box is open. The "on mouse over" events work (elements are highlighted when the mouse is over) but clicking on any element has no effect. I cannot edit the filename, save the document, close the dialog box, ... I can click on the "+" button of the main window and open a new tab, but the dialog box stays on top. When I have a tab open that plays a video or some music, the playing doesn't stop. Firefox doesn't seem to freeze, it just keeps this dialog box open on top. I have to pkill firefox. Additional information: `wmctrl -l` lists multiple "Save as" windows. My computer: Dell XPS 15 My system: $ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 $ firefox --version Mozilla Firefox 104.0.2 $ apt-cache policy firefox firefox: Installed: (none) Candidate: 1:1snap1-0ubuntu2 Version table: 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓base chromium 105.0.5195.52 2076 latest/stable canonical✓- code e7f30e38 107latest/stablevscode✓ classic core 16-2.57.1 13741 latest/stable canonical✓core core18 20220831 2566 latest/stable canonical✓base core20 20220826 1623 latest/stable canonical✓base firefox104.0.2-1 1810 latest/stable/… mozilla✓ - gnome-3-38-20040+git.891e5bc 115latest/stable/… canonical✓- gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓- helm 3.7.0 353latest/stable snapcrafters classic snap-store 41.3-63-gbd822db 592latest/stable/… canonical✓- snapd 2.57.116778 latest/stable canonical✓snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓- $ snap info firefox name: firefox summary: Mozilla Firefox web browser publisher: Mozilla✓ store-url: https://snapcraft.io/firefox contact: https://support.mozilla.org/kb/file-bug-report-or-feature-request-mozilla license: unset description: | Firefox is a powerful, extensible web browser with support for modern web application technologies. commands: - firefox - firefox.geckodriver snap-id: 3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk tracking: latest/stable/ubuntu-22.04 refresh-date: 8 days ago, at 00:27 CEST channels: latest/stable:104.0.2-12022-09-06 (1810) 185MB - latest/candidate: 105.0-1 2022-09-13 (1842) 187MB - latest/beta: 105.0b9-12022-09-12 (1836) 187MB - latest/edge: 106.0a1 2022-09-14 (1845) 192MB - esr/stable: 91.13.0esr-1 2022-09-02 (1791) 161MB - esr/candidate:102.3.0esr-1 2022-09-12 (1839) 183MB - esr/beta: ↑ esr/edge: 102.2.0esr-2 2022-09-02 (1793) 182MB - installed: 104.0.2-1 (1810) 185MB - ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 09:16:40 2022 InstallationDate: Installed on 2022-06-30 (76 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1989676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1988020] Re: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of file on stdin at conffile prompt
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: speech-dispatcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1988020 Title: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of file on stdin at conffile prompt Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: Suddenly the issue came in although didn't find any problem running ubuntu so far. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: speech-dispatcher 0.11.1-1 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 AptOrdering: gir1.2-gtk-3.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Aug 29 11:13:06 2022 ErrorMessage: end of file on stdin at conffile prompt InstallationDate: Installed on 2020-10-14 (683 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.0.9 SourcePackage: speech-dispatcher Title: package speech-dispatcher 0.11.1-1 failed to install/upgrade: end of file on stdin at conffile prompt UpgradeStatus: Upgraded to jammy on 2022-08-18 (10 days ago) modified.conffile..etc.speech-dispatcher.modules.mary-generic.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1988020/+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 1990005] Re: Visible columns option missing function
Adding screenshot ** Attachment added: "nautilus-visible-columns.png" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+attachment/5616613/+files/nautilus-visible-columns.png -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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 1990005] [NEW] Visible columns option missing function
Public bug reported: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "nautilus-columns.txt" https://bugs.launchpad.net/bugs/1990005/+attachment/5616600/+files/nautilus-columns.txt -- 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/1990005 Title: Visible columns option missing function Status in nautilus package in Ubuntu: New Bug description: In Ubuntu 20.04 nautilus setting Preferences > List Columns was affecting display on ALL the folders and was possible to remove the column 'Star' while in Ubuntu 22.10 nautilus 1:43~rc-1ubuntu1 setting 'Visible Columns' affect only the current folder and can't remove the 'Star' column. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 20:00:16 2022 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1064, 734)' InstallationDate: Installed on 2022-09-08 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220908) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 python3-nautilus 4.0~alpha-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1990005/+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 1988644] Updated stack trace from duplicate bug 1990002
Package: network-manager 1.39.90-1ubuntu3 ProcCmdline: /usr/sbin/NetworkManager --no-daemon -- 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/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1990000] gnome-shell crashed with SIGSEGV in __GI_getenv()
StacktraceTop: __GI_getenv (name=0x7fb42b5af43b "STEMD_DEVICE_VERIFY_SYSFS", name@entry=0x7fb42b5af439 "SYSTEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/getenv.c:84 __GI___libc_secure_getenv (name=name@entry=0x7fb42b5af439 "SYSTEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/secure-getenv.c:29 getenv_bool_secure (p=0x7fb42b5af439 "SYSTEMD_DEVICE_VERIFY_SYSFS") at ../src/basic/env-util.c:769 device_set_syspath (device=0x7fb3d0157500, _syspath=_syspath@entry=0x7fb3d00404b0 "/sys/devices/platform", verify=verify@entry=true) at ../src/libsystemd/sd-device/sd-device.c:221 sd_device_new_from_syspath (ret=ret@entry=0x7fb3d0157360, syspath=syspath@entry=0x7fb3d00404b0 "/sys/devices/platform") at ../src/libsystemd/sd-device/sd-device.c:264 ** Tags removed: need-amd64-retrace -- 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/199 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~rc-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Sep 17 01:24:15 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 43~rc-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7fb42e23f13d <__GI_getenv+173>: cmp (%rbx),%r12w PC (0x7fb42e23f13d) ok source "(%rbx)" (0x556030920c76) not located in a known VMA region (needed readable region)! destination "%r12w" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7fb42b5af43b "STEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/getenv.c:84 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/199/+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 1990002] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1988644 *** https://bugs.launchpad.net/bugs/1988644 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1988644, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1990002/+attachment/5616558/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616560/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616571/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616572/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616573/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616575/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1990002/+attachment/5616576/+files/ThreadStacktrace.txt ** Tags removed: need-amd64-retrace -- 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/1990002 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Sep 13 22:54:12 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 600 169.254.0.0/16 dev nordlynx scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990002/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
clear all or related to network manager only? -- 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/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1990002] [NEW] NetworkManager crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1988644 *** https://bugs.launchpad.net/bugs/1988644 Public bug reported: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Sep 13 22:54:12 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 600 169.254.0.0/16 dev nordlynx scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1988644 NetworkManager crashed with SIGABRT in g_assertion_message_expr() -- 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/1990002 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Sep 13 22:54:12 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 600 169.254.0.0/16 dev nordlynx scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990002/+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 1989997] Re: gnome-control-center crashed with SIGSEGV on "Colors"
*** This bug is a duplicate of bug 191 *** https://bugs.launchpad.net/bugs/191 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #191, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1989997/+attachment/5616534/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616536/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616538/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616539/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616540/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616541/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1989997/+attachment/5616542/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 191 gnome-control-center crashed with SIGSEGV in cc_color_device_set_expanded() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1989997 Title: gnome-control-center crashed with SIGSEGV on "Colors" Status in gnome-control-center package in Ubuntu: New Bug description: After a distro upgrade from Jammy to Kinetic (I know, I know, what am I doing?), gnome-control-center appears to open fine. However, switching to the Color Profiles pane causes it to segfault out. Description:Ubuntu Kinetic Kudu (development branch) Release:22.10 gnome-control-center: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://za.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status What You Expected To Happen: Color profiles pane to open and display current display device color profile. What Actually Happened: Color profile pane opened stating there was no display device to configure, then Settings crashed outright. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 19:01:48 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-09-06 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) JournalErrors: -- No entries -- ProcCmdline: gnome-control-center ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x5652c3340e58:cmpl $0x1,0x28(%rax) PC (0x5652c3340e58) ok source "$0x1" ok destination "0x28(%rax)" (0x0028) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libcolord.so.2 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1989997/+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 1990000] [NEW] gnome-shell crashed with SIGSEGV in __GI_getenv()
Public bug reported: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~rc-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Sep 17 01:24:15 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 43~rc-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7fb42e23f13d <__GI_getenv+173>:cmp (%rbx),%r12w PC (0x7fb42e23f13d) ok source "(%rbx)" (0x556030920c76) not located in a known VMA region (needed readable region)! destination "%r12w" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7fb42b5af43b "STEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/getenv.c:84 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A separator: ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic need-amd64-retrace package-from-proposed ** Information type changed from Private to Public -- 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/199 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() Status in gnome-shell package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-shell 43~rc-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Sep 17 01:24:15 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 43~rc-2ubuntu2 SegvAnalysis: Segfault happened at: 0x7fb42e23f13d <__GI_getenv+173>: cmp (%rbx),%r12w PC (0x7fb42e23f13d) ok source "(%rbx)" (0x556030920c76) not located in a known VMA region (needed readable region)! destination "%r12w" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: __GI_getenv (name=0x7fb42b5af43b "STEMD_DEVICE_VERIFY_SYSFS") at ./stdlib/getenv.c:84 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 ?? () from /lib/x86_64-linux-gnu/libudev.so.1 Title: gnome-shell crashed with SIGSEGV in __GI_getenv() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/199/+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 1989989] [NEW] Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)
Public bug reported: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1989989 Title: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7) Status in alsa-driver package in Ubuntu: New Bug description: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I have the same problem on a Yoga 7 Gen 7 AMD (14ARB7), which may be the same problem. @pjungkamp In order to test on my machine, can I just apply the same set of patches (¹ and ²), or do I need to do something like search/replace, or I just can't apply them at all? Thanks! ¹=https://github.com/PJungkamp/yoga9-linux/blob/main/kernel-patches/0006-ALSA-hda-realtek-Add-quirk-for-Lenovo-Yoga9-14IAP7.patch ²=https://github.com/PJungkamp/yoga9-linux/blob/main/kernel-patches/0007-ALSA-hda-realtek-Add-quirk-for-Yoga-devices.patch -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
Cool! Thanks for testing :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
This bug was fixed in the package ubuntu-settings - 22.10.1 --- ubuntu-settings (22.10.1) kinetic; urgency=medium * Add ubuntu-raspi-settings-desktop package, adding z3fold and zstd modules to the Ubuntu Desktop on Raspberry Pi (LP: #1977764) * Add ubuntu-raspi-settings-server package, adding 99-fake-cloud.cfg to the Ubuntu Server on Raspberry Pi (LP: #1989807) * Moved network-manager and polkit settings (which are desktop-specific) from ubuntu-raspi-settings to ubuntu-raspi-settings-desktop * Bump standards version to current (4.6.0.1) -- Dave Jones Wed, 20 Jul 2022 11:55:13 +0100 ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Jammy: New Status in ubuntu-settings source package in Kinetic: Fix Released Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1989807] Re: Move raspi cloud-init configuration to ubuntu-settings
This bug was fixed in the package ubuntu-settings - 22.10.1 --- ubuntu-settings (22.10.1) kinetic; urgency=medium * Add ubuntu-raspi-settings-desktop package, adding z3fold and zstd modules to the Ubuntu Desktop on Raspberry Pi (LP: #1977764) * Add ubuntu-raspi-settings-server package, adding 99-fake-cloud.cfg to the Ubuntu Server on Raspberry Pi (LP: #1989807) * Moved network-manager and polkit settings (which are desktop-specific) from ubuntu-raspi-settings to ubuntu-raspi-settings-desktop * Bump standards version to current (4.6.0.1) -- Dave Jones Wed, 20 Jul 2022 11:55:13 +0100 ** Changed in: ubuntu-settings (Ubuntu Kinetic) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1989807 Title: Move raspi cloud-init configuration to ubuntu-settings Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Jammy: New Status in ubuntu-settings source package in Kinetic: Fix Released Bug description: Currently /etc/cloud/cloud.cfg.d/99-fake_cloud.cfg (which exists to disable "real" cloud sources on the raspi images) is hacked into the images from livecd-rootfs. It would be preferable to have this in a server-specific variant of the ubuntu-raspi-settings package. To avoid dpkg conflicts, the file should be differently named (99-fake-cloud.cfg would be sufficient) with a maintscript tweak to remove the old name. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1989807/+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 1981148] Re: Focusing the filename in GTK's portal file dialog triggers search
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981148 Title: Focusing the filename in GTK's portal file dialog triggers search Status in firefox package in Ubuntu: Confirmed Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1981148] Re: Focusing the filename in GTK's portal file dialog triggers search
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981148 Title: Focusing the filename in GTK's portal file dialog triggers search Status in firefox package in Ubuntu: Confirmed Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1989515] Re: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic
I confirmed that the fix works: Firstly I compiled `gdal` and now it could be built successfully; secondly I wrote a simple program to include `goo/gmem.h` and didn't see the compile error anymore. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1989515 Title: "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic Status in poppler package in Ubuntu: Fix Released Bug description: Somehow "goo/GooCheckedOps.h" is missing in 0.62.0-2ubuntu2.13 on Ubuntu Bionic but "goo/gmem.h" still has the statement `#include "GooCheckedOps.h"`. As a result, a compile error will happen when compiling code that uses poppler: /usr/include/poppler/goo/gmem.h:31:11: fatal error: GooCheckedOps.h: No such file or directory I'm using Ubuntu 18.04 and currently having 0.62.0-2ubuntu2.12 (the previous version) installed. I confirmed that "goo/gmem.h" doesn't have the `#include "GooCheckedOps.h"` statement. I found this issue when I was compiling gdal on my Docker container. The Docker container was installed the problematic version 0.62.0-2ubuntu2.13 and I ran into the "No such file or directory" error. I compiled on both Amd64 and AArch64 and I ran into the same error on both platforms. By reading the diff between 2.12 and 2.13 (https://launchpadlibrarian.net/622079418/poppler_0.62.0-2ubuntu2.12_0.62.0-2ubuntu2.13.diff.gz), the patch looks quite right. But when I examined the contents of the built `.deb` packages, I didn't find the file "goo/GooCheckedOps.h". Kind of weird, because the problem seems to be caused by applying "CVE-2022-38784-pre.patch" in half: the first part that creates "goo/GooCheckedOps.h" was not applied during the build process and the second part that modifies "goo/gmem.h" was applied. Any thoughts? Ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1989515/+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 1981148] Re: Focusing the filename in GTK's portal file dialog triggers search
I can confirm that the issue also affects Chrome and Chromium: https://bugs.launchpad.net/ubuntu/+source/ubuntu-unity-meta/+bug/1972130 Reports also mention Unity, it seems to be a system-wide issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981148 Title: Focusing the filename in GTK's portal file dialog triggers search Status in firefox package in Ubuntu: Confirmed Status in lubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-mate-meta package in Ubuntu: Confirmed Bug description: I'm still wondering why my Ubuntu forces the snap version of Firefox onto me, despite apt-pinning, but OK, I guess being frustrated about that would be a lost cause. In any case: The snap version of Firefox that my Ubuntu has decided to install despite my apt-pinning has a bug in the saving dialog. I've recorded a video and left it online, here: https://anonfiles.com/X4ec15w7y3/simplescreenrecorder-2022-07-10_15.57.54_mkv Following protocol: 1) $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 2) $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu2 Candidate: 1:1snap1-0ubuntu2 Version table: *** 1:1snap1-0ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 102.0.1+build1-0ubuntu0.18.04.1 999 500 http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages 500 https://ppa.launchpadcontent.net/ubuntu-mozilla-security/ppa/ubuntu bionic/main amd64 Packages (note how Ubuntu doesn't give a damn about the pin priority, but whatever) 3) I'm trying to save a downloaded document. 3.1) Firefox opens the save dialogue. 3.2) I would like to enter a filename into the filename bar 4) following 3.1: 4.2) When I try to change the filename, the focus immediately jumps to the search bar and the dialogue for some reason tries to search for the entered letters on the drive. I can click back to focus on the filename bar, sometimes I can manage to type one or two letters, before the focus jumps, again. This does not happen with the version I installed using apt, but which repeatedly gets removed by the Ubuntu updating process, to install the snap version, which sadly never seems to work without problems. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sun Jul 10 16:00:53 2022 InstallationDate: Installed on 2022-03-07 (125 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981148/+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 1989976] [NEW] wishlist: Passkeys should be supported
Public bug reported: Starting from 2022 the main big tech companies introduce Passkeys. Or in the more official name Fido Multi-device credentials. Basically this is a webauthn login, but the private key is distributed among all the devices in a persons Google, Microsoft and iCloud account. If a person wants to login in on a device not in the account a QR code should be scanned after which the computers do some cryptographic magic via Bluetooth. And the new device also has the private key. This method is supposed to be a lot safer and more convenient than the usual passwords. As far as I know this system is open. My wish is that Ubuntu and Linux in general also will support this Passkeys thing. Regards, Martijn. See : https://fidoalliance.org/multi-device-fido-credentials/ https://developers.google.com/identity/fido https://developer.apple.com/passkeys/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: fido passkeys webauthn wishlist -- 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/1989976 Title: wishlist: Passkeys should be supported Status in firefox package in Ubuntu: New Bug description: Starting from 2022 the main big tech companies introduce Passkeys. Or in the more official name Fido Multi-device credentials. Basically this is a webauthn login, but the private key is distributed among all the devices in a persons Google, Microsoft and iCloud account. If a person wants to login in on a device not in the account a QR code should be scanned after which the computers do some cryptographic magic via Bluetooth. And the new device also has the private key. This method is supposed to be a lot safer and more convenient than the usual passwords. As far as I know this system is open. My wish is that Ubuntu and Linux in general also will support this Passkeys thing. Regards, Martijn. See : https://fidoalliance.org/multi-device-fido-credentials/ https://developers.google.com/identity/fido https://developer.apple.com/passkeys/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1989976/+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 1989971] [NEW] Correctly initialize a variable to avoid errors
Public bug reported: * Impact The error tracked got some reports of issues since 0.9 was SRUed to focal which has been halting the update. * Test Case Check the error tracker for focal reported issue, the one which started with the 0.9 SRU should stop being reported after the update. Confirm that the boltctl correctly list authorized devices and that connecting a new one triggers a prompt on the desktop, then that settings correctly include the newly authorized device * Regression potential The patch only correctly initialize the syspath variable of the device structure to null. If that was not handled correctly by the code the service could crash or fail to detect properly connected devices. ** Affects: bolt (Ubuntu) Importance: Low Assignee: Sebastien Bacher (seb128) Status: Fix Released ** Changed in: bolt (Ubuntu) Importance: Undecided => Low ** Changed in: bolt (Ubuntu) Status: New => Fix Released ** Changed in: bolt (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1989971 Title: Correctly initialize a variable to avoid errors Status in bolt package in Ubuntu: Fix Released Bug description: * Impact The error tracked got some reports of issues since 0.9 was SRUed to focal which has been halting the update. * Test Case Check the error tracker for focal reported issue, the one which started with the 0.9 SRU should stop being reported after the update. Confirm that the boltctl correctly list authorized devices and that connecting a new one triggers a prompt on the desktop, then that settings correctly include the newly authorized device * Regression potential The patch only correctly initialize the syspath variable of the device structure to null. If that was not handled correctly by the code the service could crash or fail to detect properly connected devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1989971/+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 1989962] Re: Wired headphones keep disconnecting after update to Jammy
** Package changed: ubuntu => alsa-driver (Ubuntu) -- 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/1989962 Title: Wired headphones keep disconnecting after update to Jammy Status in alsa-driver package in Ubuntu: New Bug description: I've got a weird problem with my wired headset not working after the update to 22.04. The headset is wired in via the headphone jack and was working fine until the update to Jammy. Now, every time I plug in, it doesn't even recognize that it has been plugged in and I get no pop up to select "Headset". Some times, after plugging in a long time, it recognizes it and the headset works. But after a few mins, it gets disconnected again. I've tried many things but nothing has worked so far. It is not an issue with the headphone as I've tried with other ones and the same issue persists. Please help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1989962/+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 1989962] [NEW] Wired headphones keep disconnecting after update to Jammy
You have been subscribed to a public bug: I've got a weird problem with my wired headset not working after the update to 22.04. The headset is wired in via the headphone jack and was working fine until the update to Jammy. Now, every time I plug in, it doesn't even recognize that it has been plugged in and I get no pop up to select "Headset". Some times, after plugging in a long time, it recognizes it and the headset works. But after a few mins, it gets disconnected again. I've tried many things but nothing has worked so far. It is not an issue with the headphone as I've tried with other ones and the same issue persists. Please help. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Wired headphones keep disconnecting after update to Jammy https://bugs.launchpad.net/bugs/1989962 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 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 1988488] Re: Screen freeze at the moment of login
** This bug is no longer a duplicate of bug 1988473 [SRU] VirtualBox 6.1.34 guests crash with kernel 5.15.0-47 ** Package changed: systemd (Ubuntu) => gdm3 (Ubuntu) ** Changed in: gdm3 (Ubuntu) Status: Confirmed => New -- 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/1988488 Title: Screen freeze at the moment of login Status in gdm3 package in Ubuntu: New Bug description: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1988488/+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 1988488] [NEW] Screen freeze at the moment of login
You have been subscribed to a public bug: The problem started to appear 2 weeks ago after one of my daily updates. It also happens after I re-install the system from a freshly downloaded ISO file. The system freezes at the moment, it starts the gnome display manager. I file the bug-report after a partial upgrade just before I will reboot the system. If needed I can reboot in recovery mode, since the gnome display manager is not started in that case. I tried the continue button without effect and also "apt upgrade" and "apt dist-upgrade" do have the same effect I run the VM from the Host-OpenZFS file system, so I can restore to before the update. Recently I use a Virtualbox snapshot to restore the system to before the update/upgrade. If you need log files, let me know. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: systemd 251.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 1 19:42:04 2022 InstallationDate: Installed on 2022-05-28 (96 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220526) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=9eaf84b0-b69b-4760-80b5-310e3a258bda ro quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug kinetic wayland-session -- Screen freeze at the moment of login https://bugs.launchpad.net/bugs/1988488 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1989737] Re: beamer fails to handle the xcolor package options
** Changed in: tex-live Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: beamer fails to handle the xcolor package options Status in tex-live: Fix Released Status in texlive-base package in Ubuntu: New Status in texlive-base source package in Jammy: Won't Fix Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/tex-live/+bug/1989737/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
Okay, this is at least something. The list doesn't seem terrible - the 'maybe more universe packages' worries me but I'll assume you'll perform due diligence and take care of all that are needed. FFe/UIFe approved! ** Changed in: glib2.0 (Ubuntu) Status: New => Triaged ** Changed in: fonts-noto-color-emoji (Ubuntu) Status: New => Triaged -- 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/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in glib2.0 package in Ubuntu: Triaged Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google released their updated fonts-noto-color-emoji Friday. We also need to update glib so that new non-emoji Unicode characters are handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - node-unicode-data utf8proc maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1989626/+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 1989953] Re: to update media key session
Can you please give a more detailed description of the problem? E.g. what does "rejected" mean? Bonus points to a step by step guide to reproduce the problem. ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/1989953 Title: to update media key session Status in chromium-browser package in Ubuntu: Incomplete Bug description: the chromium needs to update the media key session cause it rejected the Binge website by playing the movie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989953/+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 1989964] [NEW] Segmentation fault crocus_dri.so (X server dies)
Public bug reported: The desktop session is running for 0 or more days. Suddenly the X server dies, and login screen reappears. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 16 14:45:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/sun--vg-root ro SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.release: 2.59 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.59 dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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: mesa (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 mesa in Ubuntu. https://bugs.launchpad.net/bugs/1989964 Title: Segmentation fault crocus_dri.so (X server dies) Status in mesa package in Ubuntu: New Bug description: The desktop session is running for 0 or more days. Suddenly the X server dies, and login screen reappears. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libgl1-mesa-dri 22.0.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Fri Sep 16 14:45:54 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [103c:18e4] MachineType: Hewlett-Packard HP EliteDesk 800 G1 TWR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-47-generic root=/dev/mapper/sun--vg-root ro SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/16/2015 dmi.bios.release: 2.59 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L01 v02.59 dmi.board.name: 18E4 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL01v02.59:bd03/16/2015:br2.59:svnHewlett-Packard:pnHPEliteDesk800G1TWR:pvr:rvnHewlett-Packard:rn18E4:rvr:cvnHewlett-Packard:ct6:cvr:skuC8N27AV: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G1 TWR dmi.product.sku: C8N27AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 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:
[Desktop-packages] [Bug 1988378] Re: Firefox allows a user to alter/delete a third party website cookie
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** Changed in: firefox (Ubuntu) Status: New => Invalid -- 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/1988378 Title: Firefox allows a user to alter/delete a third party website cookie Status in firefox package in Ubuntu: Invalid Bug description: I was in conflict with a certain technological company. I usually browsed their website, downloaded a few PDF files, and contacted with them via a Yahoo mail account using the Firefox browser. Some of the emails from the company had graphic signatures. At a certain date where my contract with the company ended, and I choosed not to renew the contract, I wasn't able to access my Yahoo mail account using the bookmark, and I had to enter my Yahoo mail password. If the user doesn't remember a website's password, this can be unpleasant. I have a Yahoo mail account for years, and this never happened to me. It looks like the vulnerability is that a developer from company X can write code on a website, a PDF file, or linked to an email, that will alter/delete a cookie that belongs to website Y. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1988378/+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 1989729] Re: Problem with graphics card
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1989729 Title: Problem with graphics card Status in xorg package in Ubuntu: New Bug description: Hi,Names Hamdaan. I have installed Ubuntu on my PC about 4-5 days ago. At first I didn't seem to notice, But as I used my PC I've been noticing that it seems that my PC's graphics card is not working as efficient as before. But when I read the driver name I got to know that it has not downloaded the correct Driver software , and I don't know how to fix that?. Thanks in advance for answering. IN CASE YOU NEED IT: PC MODEL: Acer Aspire E1-572 MEMORY : 4.0 GiB PROCESSER: Intel® Core™ i5-4200U CPU @ 1.60GHz × 4 OS TYPE : 64x ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 17:46:25 2022 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: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics Controller [1025:0775] InstallationDate: Installed on 2022-09-13 (1 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Aspire E1-572 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic root=UUID=fcb232d7-2139-4cee-b321-7332acc47658 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/02/2014 dmi.bios.release: 2.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HW dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.17:bd09/02/2014:br2.17:efr2.17:svnAcer:pnAspireE1-572:pvrV2.17:rvnAcer:rnEA50_HW:rvrV2.17:cvnAcer:ct10:cvrChassisVersion:skuAspireE1-572_0775_V2.17: dmi.product.family: SharkBay System dmi.product.name: Aspire E1-572 dmi.product.sku: Aspire E1-572_0775_V2.17 dmi.product.version: V2.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1989729/+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 1989953] Re: to update media key session
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** 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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1989953 Title: to update media key session Status in chromium-browser package in Ubuntu: New Bug description: the chromium needs to update the media key session cause it rejected the Binge website by playing the movie To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1989953/+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 1989959] [NEW] Incorrect ESM coverage information
Public bug reported: Software Properties says that Extended Security Maintenance provides security updates for over 3 Ubuntu packages, see lines 1269 and 1346 in data/gtkbuilder/main.ui. According to https://ubuntu.com/16-04, Canonical provides extended security maintenance for binary packages that reside in the "main" Ubuntu repository, which contains about 7000 architecture-specific packages depending on the Ubuntu release. Moreover, ESM is only provided for a part of packages, not for all packages in the "main" repository. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1989959 Title: Incorrect ESM coverage information Status in software-properties package in Ubuntu: New Bug description: Software Properties says that Extended Security Maintenance provides security updates for over 3 Ubuntu packages, see lines 1269 and 1346 in data/gtkbuilder/main.ui. According to https://ubuntu.com/16-04, Canonical provides extended security maintenance for binary packages that reside in the "main" Ubuntu repository, which contains about 7000 architecture-specific packages depending on the Ubuntu release. Moreover, ESM is only provided for a part of packages, not for all packages in the "main" repository. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1989959/+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 1988836] Re: Enable the open NVIDIA kernel modules
Kernel rework is proposed at: https://lists.ubuntu.com/archives/kernel- team/2022-September/133205.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and harfbuzz for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 - harfbuzz (we might not update harfbuzz since the current kinetic version is so old) Other packages needed but don't affect UI - node-unicode-data utf8proc maybe more universe packages + + Declined changes + + harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details - Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. + Google released their updated fonts-noto-color-emoji Friday. - We also need to update glib and harfbuzz for the new release so that new - composite emoji like "pink heart" display correctly. + We also need to update glib so that new non-emoji Unicode characters are + handled correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 - - https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. UI affecting packages fonts-noto-color-emoji glib2.0 Other packages needed but don't affect UI - node-unicode-data utf8proc maybe more universe packages Declined changes harfbuzz - doesn't appear to be a critical need and our kinetic version is too old. harfbuzz will be updated for Ubuntu 23.04 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. -- You received this bug notification because you are a member of
[Desktop-packages] [Bug 1989737] Re: beamer fails to handle the xcolor package options
Apparently upstream don't want us to cherry-pick the fix. It's probably fine legally, but I don't think it's worth getting into that given that I was only volunteering my time to try and help. Setting Won't Fix since it seems that this is unlikely to get fixed in Jammy then. I've not checked the status in the development release. If an Ubuntu developer wants to drive fixing this, or a volunteer finds an Ubuntu developer willing to sponsor a fix, then feel free to reopen. ** Changed in: texlive-base (Ubuntu Jammy) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: beamer fails to handle the xcolor package options Status in tex-live: Unknown Status in texlive-base package in Ubuntu: New Status in texlive-base source package in Jammy: Won't Fix Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/tex-live/+bug/1989737/+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 1989737] Re: beamer fails to handle the xcolor package options
Note that if we are not updating the version number the license requires they mark it as not the same beamer as everyone else has. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: beamer fails to handle the xcolor package options Status in tex-live: Unknown Status in texlive-base package in Ubuntu: New Status in texlive-base source package in Jammy: Triaged Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/tex-live/+bug/1989737/+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 1989737] Re: beamer fails to handle the xcolor package options
Upstream fix here: https://github.com/josephwright/beamer/commit/f769f2ff60f3ade9b920f743ff65b46e5013758a ** Summary changed: - Bug in beamer with fix in v3.66 + beamer fails to handle the xcolor package options ** Also affects: texlive-base (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: texlive-base (Ubuntu Jammy) Status: New => Triaged ** Bug watch added: github.com/josephwright/beamer/issues #759 https://github.com/josephwright/beamer/issues/759 ** Also affects: tex-live via https://github.com/josephwright/beamer/issues/759 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: beamer fails to handle the xcolor package options Status in tex-live: Unknown Status in texlive-base package in Ubuntu: New Status in texlive-base source package in Jammy: Triaged Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/tex-live/+bug/1989737/+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 1989737] Re: Bug in beamer with fix in v3.66
** Summary changed: - Package option (for xcolor) is not being properly used in beamer + Bug in beamer with fix in v3.66 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1989737 Title: beamer fails to handle the xcolor package options Status in tex-live: Unknown Status in texlive-base package in Ubuntu: New Status in texlive-base source package in Jammy: Triaged Bug description: There is a bug in beamer v3.65 which is fixed in beamer v3.66. A full description along with the workaround you currently have to use is given at https://tex.stackexchange.com/questions/641909/package- option-for-xcolor-is-not-being-properly-used-in-beamer . It would be great if an updated version of texlive with the newer version of beamer could be packaged up for jammy. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: texlive-full 2021.20220204-1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 15 15:59:03 2022 InstallationDate: Installed on 2020-08-03 (773 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: texlive-base UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/tex-live/+bug/1989737/+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 1989325] Re: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1
@vanvugt: I've tried disabling all extensions but that did not have any correlation with crashes. It kept on crashing regardless, also before they were installed at all. It would be worrying that something quite high level can crash the entire window manager. It's disturbing. The culprit is Wayland itself, because a Window manager should never crash in total, regardless of what a single application or module is trying to do. It is interesting what triggers it, so we can get to the cause within Wayland @the nvidia drivers have all kinds of other issues in my hybrid setup. The nouveau driver has proven to be much more reliable out-of-the-box for this setup. It has been with other hardware for decades and still. Nvidia can't seem to get it right, even after version 1 million + 1. For that reason, I prefer my next laptop to not have a discrete graphics card at all -- 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/1989325 Title: gnome-shell crashes on Lenovo Thinkpad P50 after upgrade to 22.04.1 Status in gnome-shell package in Ubuntu: Incomplete Bug description: I upgrade to Ubuntu 22.04 recently, and while upgrading and updating I also got a new bios version (1.69) for my Lenovo Thinkpad P50 laptop. Since then gnome-shell has been very unstable, crashing regularly on minor changes, like plugging in a monitor or going to suspend mode. Update: I just found out that the bug is not reproducable when logged in with Xorg instead of Wayland (https://askubuntu.com/questions/1428898/lenovo-p50-crashes-gnome- shell-regularly-after-upgrade-to-ubuntu-22-04-1-using) So we got a workaround and a culprit: Wayland ... in conjunction with something quite typical for my hardware maybe(?), Lenovo Thinkpad P50 (20ENCTO1WW) with Quadro M2000M discrete graphics ... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.4-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 12 09:49:57 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-09-09 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1989325/+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 1989626] Re: UIFe: fonts-noto-color-emoji & other updates for Unicode 15
** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and harfbuzz for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. Likely affected packages fonts-noto-color-emoji - nototools (current version was updated for Unicode 15 in August so may already be new enough) glib2.0 harfbuzz node-unicode-data + utf8proc maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. ** Description changed: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other platforms that will be quickly adopting the new emoji characters. The release happened too late for related upstream releases to happen by Ubuntu's User Interface Freeze on September 15 and be packaged. Therefore, I request a UIFe for Ubuntu 22.10 for Unicode 15 packages. More details Google will be releasing a new version of fonts-noto-color-emoji "later this week" but it looks like it won't be released in time for Ubuntu's User Interface Freeze. We also need to update glib and harfbuzz for the new release so that new composite emoji like "pink heart" display correctly. https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2877 https://github.com/harfbuzz/harfbuzz/pull/3797 There are probably some other minor universe packages that we should sync from Debian if we see they are related to Unicode 15. I don't have packaging ready for these changes yet but I'm requesting the UIFe early. - Likely affected packages + UI affecting packages fonts-noto-color-emoji glib2.0 - harfbuzz + harfbuzz (we might not update harfbuzz since the current kinetic version is so old) + + Other packages needed but don't affect UI + - node-unicode-data utf8proc maybe more universe packages 22.04 LTS - We have done SRUs of new fonts-noto-color-emoji releases to older LTSes before. We may do it again but that will be one or more separate bugs. References -- https://blog.emojipedia.org/whats-new-in-unicode-15-0/ https://developers.googleblog.com/2022/09/updates-to-emoji-new- characters-animation-colors-and-more.html https://unicode.org/versions/Unicode15.0.0/ Email to Docs List: https://lists.ubuntu.com/archives/ubuntu-doc/2022-September/020889.html I don't believe translators need to be notified about this UIFe but let me know if I should email them anyway. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1989626 Title: UIFe: fonts-noto-color-emoji & other updates for Unicode 15 Status in fonts-noto-color-emoji package in Ubuntu: New Bug description: Justification - Unicode 15 was release September 13. This is an annual release. It's expected that the latest Ubuntu will support the latest stable Unicode release. This is required for compatibility with Internet communications with other
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
** Also affects: nvidia-graphics-drivers-515 (Ubuntu) Importance: Undecided Status: New -- 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/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: New Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+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 1989946] Re: Fullscreen image viewer uses only small window size
** Description changed: When viewing images in fullscreen, software randomly switches to drawing image in a small subsection of the screen (see img in attachment). Once software is in this new state it does not revert to updating the full screen. Quitting and re-entering fullscreen temporarily solves the issue. I have observed the issue both in - eog - - geeky + - geeqie I have not seen this issue in any other fullscreen software I use. I am running - Ubuntu 22.04.1 - Linux 5.15.0-48-generic - X.Org X Server 1.21.1.3 - The Laptop has the following GPU: - Intel Skylake GT2 [HD Graphics 520] -- (Mesa 22.0.5) - NVIDIA GM108GLM [Quadro K620M / Quadro M500M] -- (Driver Version: 515.65.01) (It is running in NVIDIA on-demand PRIME profile) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 10:16:46 2022 InstallationDate: Installed on 2021-09-14 (366 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: eog UpgradeStatus: Upgraded to jammy on 2022-04-29 (140 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1989946 Title: Fullscreen image viewer uses only small window size Status in eog package in Ubuntu: New Bug description: When viewing images in fullscreen, software randomly switches to drawing image in a small subsection of the screen (see img in attachment). Once software is in this new state it does not revert to updating the full screen. Quitting and re-entering fullscreen temporarily solves the issue. I have observed the issue both in - eog - geeqie I have not seen this issue in any other fullscreen software I use. I am running - Ubuntu 22.04.1 - Linux 5.15.0-48-generic - X.Org X Server 1.21.1.3 The Laptop has the following GPU: - Intel Skylake GT2 [HD Graphics 520] -- (Mesa 22.0.5) - NVIDIA GM108GLM [Quadro K620M / Quadro M500M] -- (Driver Version: 515.65.01) (It is running in NVIDIA on-demand PRIME profile) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 10:16:46 2022 InstallationDate: Installed on 2021-09-14 (366 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: eog UpgradeStatus: Upgraded to jammy on 2022-04-29 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1989946/+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 1971058] Re: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status
** Bug watch added: github.com/ubuntu/yaru/issues #3629 https://github.com/ubuntu/yaru/issues/3629 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3629 Importance: Unknown Status: Unknown ** Tags removed: impish ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1971058 Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Confirmed Bug description: Can't install do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 21.10 Package: yaru-theme-gnome-shell 21.10.2 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Apr 30 18:40:19 2022 Dependencies: ErrorMessage: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-03-27 (399 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu2 apt 2.3.9 SourcePackage: yaru-theme Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: new yaru-theme-gnome-shell package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to impish on 2022-04-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1971058/+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 1970012] Re: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: el subproceso nuevo paquete yaru-theme-gnome-shell script pre-installation devolvió el código de
*** This bug is a duplicate of bug 1971058 *** https://bugs.launchpad.net/bugs/1971058 Ubuntu 21.10 is no longer supported. Please try Ubuntu 22.04. ** Bug watch added: github.com/ubuntu/yaru/issues #3636 https://github.com/ubuntu/yaru/issues/3636 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3636 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1970012 Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: el subproceso nuevo paquete yaru-theme-gnome-shell script pre- installation devolvió el código de salida de error 1 Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: New Bug description: sale error ProblemType: Package DistroRelease: Ubuntu 21.10 Package: yaru-theme-gnome-shell 21.10.2 ProcVersionSignature: Ubuntu 5.13.0-40.45-generic 5.13.19 Uname: Linux 5.13.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu71.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Apr 23 00:03:59 2022 Dependencies: ErrorMessage: el subproceso nuevo paquete yaru-theme-gnome-shell script pre-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2022-01-19 (93 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.3.9 SourcePackage: yaru-theme Title: package yaru-theme-gnome-shell 21.10.2 failed to install/upgrade: el subproceso nuevo paquete yaru-theme-gnome-shell script pre-installation devolvió el código de salida de error 1 UpgradeStatus: Upgraded to impish on 2022-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1970012/+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 1989946] [NEW] Fullscreen image viewer uses only small window size
Public bug reported: When viewing images in fullscreen, software randomly switches to drawing image in a small subsection of the screen (see img in attachment). Once software is in this new state it does not revert to updating the full screen. Quitting and re-entering fullscreen temporarily solves the issue. I have observed the issue both in - eog - geeky I have not seen this issue in any other fullscreen software I use. I am running - Ubuntu 22.04.1 - Linux 5.15.0-48-generic - X.Org X Server 1.21.1.3 The Laptop has the following GPU: - Intel Skylake GT2 [HD Graphics 520] -- (Mesa 22.0.5) - NVIDIA GM108GLM [Quadro K620M / Quadro M500M] -- (Driver Version: 515.65.01) (It is running in NVIDIA on-demand PRIME profile) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 10:16:46 2022 InstallationDate: Installed on 2021-09-14 (366 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: eog UpgradeStatus: Upgraded to jammy on 2022-04-29 (140 days ago) ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages ** Attachment added: "x11 fullscreen bug" https://bugs.launchpad.net/bugs/1989946/+attachment/5616399/+files/bugx11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1989946 Title: Fullscreen image viewer uses only small window size Status in eog package in Ubuntu: New Bug description: When viewing images in fullscreen, software randomly switches to drawing image in a small subsection of the screen (see img in attachment). Once software is in this new state it does not revert to updating the full screen. Quitting and re-entering fullscreen temporarily solves the issue. I have observed the issue both in - eog - geeky I have not seen this issue in any other fullscreen software I use. I am running - Ubuntu 22.04.1 - Linux 5.15.0-48-generic - X.Org X Server 1.21.1.3 The Laptop has the following GPU: - Intel Skylake GT2 [HD Graphics 520] -- (Mesa 22.0.5) - NVIDIA GM108GLM [Quadro K620M / Quadro M500M] -- (Driver Version: 515.65.01) (It is running in NVIDIA on-demand PRIME profile) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: eog 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 10:16:46 2022 InstallationDate: Installed on 2021-09-14 (366 days ago) InstallationMedia: Kubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) SourcePackage: eog UpgradeStatus: Upgraded to jammy on 2022-04-29 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1989946/+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 1951210] Re: libreoffice help doesn't open in firefox (404 error on file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Hi Chris, that's expected, because the fix has only been committed to
the repo, it's not in any release yet.
If you feel adventurous, you could use snapd from the edge channel
("snap refresh --channel=latest/edge snapd"), but it's not something I
recommend to keep active, so if you feel like trying the latest version
to verify whether the issue is really fixed you are very welcome to do
so, but after doing that I'd recommend you to return to the stable
version (same command as above, just with "latest/stable" as the
channel) and live with this bug until the next major release.
--
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/1951210
Title:
libreoffice help doesn't open in firefox (404 error on
file:///tmp/lu417531j7po.tmp/NewHelp0.html)
Status in libreoffice package in Ubuntu:
Fix Released
Status in snapd package in Ubuntu:
Fix Committed
Status in libreoffice source package in Jammy:
Fix Released
Status in snapd source package in Jammy:
Confirmed
Bug description:
Ubuntu jammy live QA-test on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
Opened LibreOffice Writer as random apps in QA-test.
Hit F1 to call help, and all I get is an error
URL: file:///tmp/lu417531j7po.tmp/NewHelp0.html
---
File not found
Firefox can’t find the file at /tmp/lu417531j7po.tmp/NewHelp0.html.
Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.
---
Firefox opens as a snap; but it isn't accessing the data from
LibreOffice.
Reported first at https://forum.snapcraft.io/t/firefox-snap-breaks-
libreoffice-deb/27537
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libreoffice-writer 1:7.2.2-0ubuntu0.21.10.1
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.465+canary3.3
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 17 04:46:33 2021
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (2026)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210/+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 1989937] Re: Nautilus crash when opening an aes file
❯ file admin.kubeconfig.aes admin.kubeconfig.aes: openssl enc'd data with salted password I will ask how it was created -- 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/1989937 Title: Nautilus crash when opening an aes file Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on an aes file, nautilus crash (without opening anything) ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 08:40:43 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'none', 'none']" b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1501, 899)' InstallationDate: Installed on 2020-11-19 (665 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) JournalErrors: sept. 16 08:40:43 username-xps-13 org.gnome.Nautilus[1687693]: free(): invalid pointer ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-09-02 (13 days ago) UserGroups: adm audio cdrom dialout dip docker i2c input lpadmin lxd microk8s plugdev sambashare sudo uucp usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1989937/+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 1979096] Re: gnome-shell search can't launch apps if dock auto-hide is enabled
Okay, I just discovered that it seems to be related to display scaling as well. I normally run with scaling set to 200% on my laptop as I find everything a bit small otherwise. Under this scaling, it does not work correctly. If I set the scaling back to 100%, then it works as expected. -- 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/1979096 Title: gnome-shell search can't launch apps if dock auto-hide is enabled Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: The problem happens, when I enable the dock to hide automatically. With this enabled, it is not possible to run the programs through the search. But when disabled, it is possible to search and run the programs. Here's the video of the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 17 18:21:45 2022 DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388] InstallationDate: Installed on 2021-04-15 (428 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago) dmi.bios.date: 03/04/2017 dmi.bios.release: 8.15 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M LX/BR dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1979096/+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 1989937] Re: Nautilus crash when opening an aes file
Thank you for your bug report. Is that a specific file or any 'aes' content? Could you perhaps attach an example to the bug? ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1989937 Title: Nautilus crash when opening an aes file Status in nautilus package in Ubuntu: Incomplete Bug description: When clicking on an aes file, nautilus crash (without opening anything) ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 08:40:43 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'none', 'none']" b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1501, 899)' InstallationDate: Installed on 2020-11-19 (665 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) JournalErrors: sept. 16 08:40:43 username-xps-13 org.gnome.Nautilus[1687693]: free(): invalid pointer ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-09-02 (13 days ago) UserGroups: adm audio cdrom dialout dip docker i2c input lpadmin lxd microk8s plugdev sambashare sudo uucp usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1989937/+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 1989937] Re: Nautilus crash when opening an aes file
** Information type changed from Private to Public -- 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/1989937 Title: Nautilus crash when opening an aes file Status in nautilus package in Ubuntu: New Bug description: When clicking on an aes file, nautilus crash (without opening anything) ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: nautilus 1:43~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 16 08:40:43 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.icon-view' b'captions' b"['size', 'none', 'none']" b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' b'org.gnome.nautilus.preferences' b'show-create-link' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(1501, 899)' InstallationDate: Installed on 2020-11-19 (665 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) JournalErrors: sept. 16 08:40:43 username-xps-13 org.gnome.Nautilus[1687693]: free(): invalid pointer ProcCmdline: /usr/bin/nautilus --gapplication-service Signal: 6 SourcePackage: nautilus UpgradeStatus: Upgraded to kinetic on 2022-09-02 (13 days ago) UserGroups: adm audio cdrom dialout dip docker i2c input lpadmin lxd microk8s plugdev sambashare sudo uucp usr_lib_nautilus: file-roller 43~alpha-1 nautilus-extension-gnome-terminal 3.45.90-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1989937/+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
