[Desktop-packages] [Bug 1961508] Re: Dock displaying over window after resuming from blank screen
FYI: My temporary workaround is to just have the Dock to auto-hide (for Ubuntu 22.04). This way there are no windows that might get stuck underneath the Dock. This essentially solves the issue in a simple way, but the only downside is that some folks prefer to see their Dock all the time. -- 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/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841354] Re: Show a "Confirm" dialog window when deleting files
I'm aware this is a very dated thread, but I absolutely agree with Greg here. As a plasma user making my way to Gnome, I don't expect the full customization that I'm accustomed to; however philosophical ideologies taking a toggle for something like this seems a bit ridiculous and overstepping. -- 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/1841354 Title: Show a "Confirm" dialog window when deleting files Status in nautilus package in Ubuntu: Opinion Bug description: Currently files are deleted instantly when pressing "Del" key. I need a confirmation dialog window. "yes/no" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1841354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956005]
Still present in Firefox 120.0 -- 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/1956005 Title: Firefox Snap won't open links to WhatsApp API Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Confirmed Bug description: The .deb version of Firefox handles links to WhatsApp API (https://api.whatsapp.com/send/?phone=) without any problem: these links open the WhatsApp web client. Snap version of Firefox doesn't know how to handle these links. It opens the pop up "Choose an application to open whatsapp lnks" that only shows the option System Handler (which fails opening them if selected). Choosing Firefox is not possible as /bin and similar folders are out of range for the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1956005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 224697] Re: Disable hibernation if swap is on file
** Changed in: pm-utils (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/224697 Title: Disable hibernation if swap is on file Status in pm-utils package in Ubuntu: Fix Released Status in pm-utils source package in Hardy: Fix Released Status in pm-utils source package in Intrepid: Fix Released Status in pm-utils package in Debian: Fix Released Bug description: Binary package hint: pm-utils If any swap device is on file, hibernation should be disabled. There were reports of Wubi users (swap is on file in such setups) ending up with a frozen system. It should be a matter of going through the swapon -s list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/224697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047146] Re: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full-Screen App Behavior
** Package changed: ubuntu => gnome-desktop (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2047146 Title: Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full- Screen App Behavior Status in gnome-desktop package in Ubuntu: New Bug description: # System Details Report --- ## Report details - **Date generated:** 2023-12-21 14:00:57 ## Hardware Information: - **Hardware Model:** ASUSTeK COMPUTER INC. N552VW - **Memory:** 32,0 GiB - **Processor:** Intel® Core™ i7-6700HQ × 8 - **Graphics:**NVIDIA GeForce GTX 960M - **Graphics 1:** NVIDIA GeForce GTX 960M - **Disk Capacity:** 1,5 TB ## Software Information: - **Firmware Version:**N552VW.304 - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.1 - **Windowing System:**X11 - **Kernel Version:** Linux 6.5.0-14-generic Dear Ubuntu Development Team, I recently managed to install the Ubuntu image with the kernel version 6.6.7. Before installing Ubuntu 23.10, I noticed logs related to the configuration of the Linux 6.6.7 kernel, which, however, did not boot successfully on my system. After successfully installing Ubuntu 23.10, I removed the newly installed 6.6.7 kernel and reverted to a more stable version of the kernel (version 6) that boots without any issues. However, I've encountered a unique problem post-installation. When I minimize applications, their icons appear in the upper right corner of the horizontal toolbar as expected. However, the mouse cursor behaves oddly around these icons. Even if I move the cursor slightly away from an icon (about a hundred pixels or so), and click on an area of the desktop (not on the toolbar itself), it unexpectedly activates the corresponding minimized application. This issue, which did not occur before, is not urgent but becomes increasingly inconvenient over time. Furthermore, in certain applications like Spotify, I sometimes encounter another issue where the window control buttons (close, maximize, minimize) disappear, and the application enters a full-screen mode, akin to a video game. This behavior seems sporadic, and I'm unsure how to consistently resolve it. Could these issues be related to screen settings or other system configurations? Also, is the full-screen behavior a known bug? Any guidance on avoiding or rectifying these problems would be greatly appreciated. Thank you for your attention to these matters. Best regards, Luigi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2047146/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047146] [NEW] Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full-Screen App Behavior
You have been subscribed to a public bug: # System Details Report --- ## Report details - **Date generated:** 2023-12-21 14:00:57 ## Hardware Information: - **Hardware Model:** ASUSTeK COMPUTER INC. N552VW - **Memory:** 32,0 GiB - **Processor:** Intel® Core™ i7-6700HQ × 8 - **Graphics:**NVIDIA GeForce GTX 960M - **Graphics 1:** NVIDIA GeForce GTX 960M - **Disk Capacity:** 1,5 TB ## Software Information: - **Firmware Version:**N552VW.304 - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.1 - **Windowing System:**X11 - **Kernel Version:** Linux 6.5.0-14-generic Dear Ubuntu Development Team, I recently managed to install the Ubuntu image with the kernel version 6.6.7. Before installing Ubuntu 23.10, I noticed logs related to the configuration of the Linux 6.6.7 kernel, which, however, did not boot successfully on my system. After successfully installing Ubuntu 23.10, I removed the newly installed 6.6.7 kernel and reverted to a more stable version of the kernel (version 6) that boots without any issues. However, I've encountered a unique problem post-installation. When I minimize applications, their icons appear in the upper right corner of the horizontal toolbar as expected. However, the mouse cursor behaves oddly around these icons. Even if I move the cursor slightly away from an icon (about a hundred pixels or so), and click on an area of the desktop (not on the toolbar itself), it unexpectedly activates the corresponding minimized application. This issue, which did not occur before, is not urgent but becomes increasingly inconvenient over time. Furthermore, in certain applications like Spotify, I sometimes encounter another issue where the window control buttons (close, maximize, minimize) disappear, and the application enters a full-screen mode, akin to a video game. This behavior seems sporadic, and I'm unsure how to consistently resolve it. Could these issues be related to screen settings or other system configurations? Also, is the full-screen behavior a known bug? Any guidance on avoiding or rectifying these problems would be greatly appreciated. Thank you for your attention to these matters. Best regards, Luigi ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Issues Encountered with Ubuntu 23.10 - Icon Minimization and Full-Screen App Behavior https://bugs.launchpad.net/bugs/2047146 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop 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 2047137] Re: nvidia 390 driver from ppa segfault
** Description changed:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
- But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
+ But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
- Then, in lightdm log an error with segfault appears.
+ Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
- ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
- ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
- ModulePath "/usr/lib/x86_64-linux-gnu/"
- ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
- ModulePath "/usr/lib/xorg/modules/extensions"
- ModulePath "/usr/lib/xorg/modules/drivers"
- ModulePath "/usr/lib/xorg/modules/input"
- ModulePath "/usr/lib/xorg/modules"
+ ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
+ ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
+ ModulePath "/usr/lib/x86_64-linux-gnu/"
+ ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
+ ModulePath "/usr/lib/xorg/modules/extensions"
+ ModulePath "/usr/lib/xorg/modules/drivers"
+ ModulePath "/usr/lib/xorg/modules/input"
+ ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
- Identifier "nvidia"
- MatchDriver "nvidia-drm"
- Driver "nvidia"
- Option "AllowEmptyInitialConfiguration"
+ Identifier "nvidia"
+ MatchDriver "nvidia-drm"
+ Driver "nvidia"
+ Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
- BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
- nvidia/390.157, 6.5.0-14-generic, x86_64: installed
- virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
+ nvidia/390.157, 6.5.0-14-generic, x86_64: installed
+ virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
- NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
-Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
+ NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
+ Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
- LANG=ru_RU.UTF-8
- LANGUAGE=ru_RU
- PATH=(custom, no user)
- SHELL=/bin/bash
- XDG_RUNTIME_DIR=
+ LANG=ru_RU.UTF-8
+ LANGUAGE=ru_RU
+ PATH=(custom, no user)
+ SHELL=/bin/bash
+ XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
[Desktop-packages] [Bug 2047154] Re: [drm] *ERROR* flip_done timed out
** Summary changed: - Xorg freeze amdgpu drm + [drm] *ERROR* flip_done timed out -- 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/2047154 Title: [drm] *ERROR* flip_done timed out Status in xorg package in Ubuntu: New Bug description: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: PW OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 2> gru 21 16:32:46 karol.home.prv kernel: RSP:
[Desktop-packages] [Bug 2047154] [NEW] Xorg freeze amdgpu drm
Public bug reported: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:25 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CRTC:84:crtc-0] commit wait timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:36 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [CONNECTOR:119:HDMI-A-1] commit wait timed out gru 21 16:32:40 karol.home.prv dbus-daemon[1317]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=2> gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* flip_done timed out gru 21 16:32:46 karol.home.prv kernel: amdgpu :0c:00.0: [drm] *ERROR* [PLANE:67:plane-5] commit wait timed out gru 21 16:32:46 karol.home.prv kernel: [ cut here ] gru 21 16:32:46 karol.home.prv kernel: WARNING: CPU: 3 PID: 100858 at /var/lib/dkms/amdgpu/6.2.4-1664922.22.04/build/amd/amdgpu/../di> gru 21 16:32:46 karol.home.prv kernel: Modules linked in: xt_recent tls xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_i> gru 21 16:32:46 karol.home.prv kernel: reed_solomon pstore_zone efi_pstore sunrpc ip_tables x_tables autofs4 ib_uverbs ib_core amdgp> gru 21 16:32:46 karol.home.prv kernel: CPU: 3 PID: 100858 Comm: Xorg Tainted: P W OE 6.2.0-26-generic #26~22.04.1-Ubuntu gru 21 16:32:46 karol.home.prv kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X470 Master SLI, BIOS P4.40 03/29> gru 21 16:32:46 karol.home.prv kernel: RIP: 0010:amdgpu_dm_atomic_commit_tail+0x3b20/0x4200 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: Code: ff 4c 89 9d 78 fc ff ff ba 01 00 00 00 31 f6 4c 89 95 80 fc ff ff 41 b9 01 00 00 00 50 5> gru 21 16:32:46 karol.home.prv kernel: RSP: 0018:b5fb50ee7818 EFLAGS: 00010002 gru 21 16:32:46 karol.home.prv kernel: RAX: 0246 RBX: 00013195 RCX: gru 21 16:32:46 karol.home.prv kernel: RDX: RSI: RDI: gru 21 16:32:46 karol.home.prv kernel: RBP: b5fb50ee7ba0 R08: R09: gru 21 16:32:46 karol.home.prv kernel: R10: 0002 R11: R12: 0246 gru 21 16:32:46 karol.home.prv kernel: R13: R14: 9710a5d8d118 R15: 9710a5d8d000 gru 21 16:32:46 karol.home.prv kernel: FS: 7f3267b4ea80() GS:97179eac() knlGS: gru 21 16:32:46 karol.home.prv kernel: CS: 0010 DS: ES: CR0: 80050033 gru 21 16:32:46 karol.home.prv kernel: CR2: 55ef7d6bfb20 CR3: 000250f4e000 CR4: 003506e0 gru 21 16:32:46 karol.home.prv kernel: Call Trace: gru 21 16:32:46 karol.home.prv kernel: gru 21 16:32:46 karol.home.prv kernel: commit_tail+0xc5/0x1a0 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: ? drm_atomic_helper_swap_state+0x246/0x380 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_helper_commit+0x137/0x160 [drm_kms_helper] gru 21 16:32:46 karol.home.prv kernel: drm_atomic_commit+0x99/0xd0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx___drm_printfn_info+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_mode_obj_set_property_ioctl+0x179/0x430 [drm] gru 21 16:32:46 karol.home.prv kernel: ? drm_mode_createblob_ioctl+0xff/0x130 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl_kernel+0xc3/0x160 [drm] gru 21 16:32:46 karol.home.prv kernel: drm_ioctl+0x27b/0x4c0 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pfx_drm_mode_obj_set_property_ioctl+0x10/0x10 [drm] gru 21 16:32:46 karol.home.prv kernel: ? __pm_runtime_suspend+0x7b/0x110 gru 21 16:32:46 karol.home.prv kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] gru 21 16:32:46 karol.home.prv kernel: __x64_sys_ioctl+0x9d/0xe0 gru 21 16:32:46 karol.home.prv kernel: do_syscall_64+0x5c/0x90 gru 21 16:32:46 karol.home.prv kernel: ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: ? exit_to_user_mode_prepare+0x3b/0xd0 gru 21 16:32:46 karol.home.prv kernel: ? syscall_exit_to_user_mode+0x2a/0x50 ? do_syscall_64+0x69/0x90 gru 21 16:32:46 karol.home.prv kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc gru 21 16:32:46 karol.home.prv kernel: RIP: 0033:0x7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 2> gru 21 16:32:46 karol.home.prv kernel: RSP: 002b:7ffedd454d30 EFLAGS: 0246 ORIG_RAX: 0010 gru 21 16:32:46 karol.home.prv kernel: RAX: ffda RBX: 7ffedd454dc0 RCX: 7f3267f1a75f gru 21 16:32:46 karol.home.prv kernel: RDX: 7ffedd454dc0 RSI: c01864ba RDI: 000e gru 21 16:32:46 karol.home.prv kernel: RBP: c01864ba R08: 0084 R09: gru 21 16:32:46 karol.home.prv kernel: R10:
[Desktop-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Also affects: nvidia-graphics-drivers-390 (Ubuntu)
Importance: Undecided
Status: New
--
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/2047137
Title:
nvidia 390 driver from ppa segfault
Status in nvidia-graphics-drivers-390 package in Ubuntu:
New
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
[Desktop-packages] [Bug 2047150] [NEW] [MIR] roc-toolkit
Public bug reported: [Availability] The package roc-toolkit is already in Ubuntu universe. The package roc-toolkit build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/roc-toolkit [Rationale] - The package roc-toolkit is required in Ubuntu main to be able to make the corresponding plugin in pipewire available - The corresponding plugin will not be used by default in Ubuntu but we still want it available. We could split it to a new binary that would go to universe but then it would need to be manually installed and force us to carry a packaging delta over Debian. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The request is about promoting the libroc0.3 binary, roc-toolkit-tools will stay in universe - The package roc-toolkit is required in Ubuntu main no later than Feb 29 due to the Noble Feature Freeze [Security] - No CVEs/security issues in this software in the past - no `suid` or `sgid` binaries - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Debian/Ubuntu/Upstream and has no downstream reports The upstream tracker has mostly feature requests and no really important problems - Ubuntu https://bugs.launchpad.net/ubuntu/+source/roc-toolkit/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=roc-toolkit - Upstream's bug tracker https://github.com/roc-streaming/roc-toolkit/issues - The package has important open bugs, listing them: TBD - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package runs a test suite on build time, if it fails it makes the build fail, link to build log https://launchpadlibrarian.net/702614513/buildlog_ubuntu-noble-amd64.roc-toolkit_0.3.0+dfsg-5_BUILDING.txt.gz python3 scripts/scons_helpers/timeout-run.py 300 bin/x86_64-pc-linux-gnu/roc-test-core .. .. .. OK (118 tests, 118 ran, 86418 checks, 0 ignored, 0 filtered out, 11 ms) - The package does not run an autopkgtest currently but a patch will be provided to add the upstream testsuite as an autopkgtest: TBD - The package does have not failing autopkgtests right now [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer - This package does not has important lintian warnings # lintian --pedantic roc-toolkit_0.3.0+dfsg-4_amd64.changes W: roc-toolkit-tools: groff-message troff::132: warning: cannot select font 'C' [usr/share/man/man1/roc-copy.1.gz:1] W: roc-toolkit-tools: groff-message troff::144: warning: cannot select font 'C' [usr/share/man/man1/roc-copy.1.gz:2] W: roc-toolkit-tools: groff-message troff::156: warning: cannot select font 'C' [usr/share/man/man1/roc-copy.1.gz:3] W: roc-toolkit-tools: groff-message ... use "--tag-display-limit 0" to see all (or pipe to a file/program) P: roc-toolkit source: package-does-not-install-examples [src/public_api/examples/] - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to debian/rules https://salsa.debian.org/multimedia-team/roc- toolkit/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - There are further dependencies that are not yet in main, MIR for them is at https://bugs.launchpad.net/ubuntu/+source/speexdsp/+bug/2047149 [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - The owning team will be desktop-packages and I have their acknowledgement for that commitment - The future owning team is already subscribed to the package - This does not use static builds - This does not use vendored code - The package has been built in the archive more recently than the last test rebuild [Background information] The Package description explains the package well Upstream Name is roc-toolkit Link to upstream project https://github.com/roc-streaming/roc-toolkit/ ** Affects: roc-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to roc-toolkit in Ubuntu.
[Desktop-packages] [Bug 2047149] [NEW] [MIR] speexdsp
Public bug reported: [Availability] The package speexdsp is already in Ubuntu universe. The package speexdsp build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/speexdsp The corresponding case in main as part of speex until Lunar and then split out. [Rationale] - The package speexdsp is required in Ubuntu main as a depends of roc-toolkit which we want to MIR as a new pipewire (optional) requirement - The corresponding plugin will not be used by default in Ubuntu but we still want it available. We could split it to a new binary that would go to universe but then it would need to be manually installed and force us to carry a packaging delta over Debian. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The package speexdsp is required in Ubuntu main no later than Feb 29 due to the Noble Feature Freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024). - Package does not expose any external endpoints - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install - The package is maintained well in Debian/Ubuntu/Upstream and has no open bug downstream and a few minor ones upstream - Ubuntu https://bugs.launchpad.net/ubuntu/+source/speexdsp/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=speexdsp - Upstream's bug tracker, https://gitlab.xiph.org/xiph/speexdsp/-/issues - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't provide any. Also it's an audio codec implementation so not something easily testable in CI. - The package has a simple buildtest autopkgtest for the library but can't really be tested in CI for the same reason as build tets. [Quality assurance - packaging] - debian/watch is present and works - debian/control defines a correct Maintainer TODO-: - This package has no important lintian warnings # lintian --pedantic speexdsp_1.2.1-1_amd64.changes P: speexdsp source: silent-on-rules-requiring-root [debian/control] P: speexdsp source: trailing-whitespace [debian/changelog:11] - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to debian/rules https://salsa.debian.org/multimedia- team/speexdsp/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - The owning team will be desktop-packages and I have their acknowledgement for that commitment - The future owning team is already subscribed to the package - This does not use static builds - This does not use vendored code - This package is not rust based - The package has been built in the archive more recently than the last test rebuild [Background information] The Package description explains the package well Upstream Name is speexdsp Link to upstream project https://gitlab.xiph.org/xiph/speexdsp ** Affects: speexdsp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speexdsp in Ubuntu. https://bugs.launchpad.net/bugs/2047149 Title: [MIR] speexdsp Status in speexdsp package in Ubuntu: New Bug description: [Availability] The package speexdsp is already in Ubuntu universe. The package speexdsp build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/speexdsp The corresponding case in main as part of speex until Lunar and then split out. [Rationale] - The package speexdsp is required in Ubuntu main as a depends of roc-toolkit which we want to MIR as a new pipewire (optional) requirement - The corresponding plugin will not be used by default in Ubuntu but we still want it available. We could split it to a new binary that would go to universe but then it would need to be manually installed and force us to carry a packaging delta over Debian. - There is no other/better way to solve this that is already in main or should go universe->main instead of this. - The package speexdsp is required in Ubuntu main
[Desktop-packages] [Bug 2012698] Re: Plymouth is stuck on a plain black screen
** Changed in: plymouth Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2012698 Title: Plymouth is stuck on a plain black screen Status in Plymouth: Fix Released Status in plymouth package in Ubuntu: New Bug description: Plymouth never displays anything -- the boot process is a plain black screen. Workaround: Tap Esc once to see text mode. Tap Esc a second time to get the Plymouth graphical screen. I only figured that out when I had been waiting too long for the disk decryption prompt. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth 22.02.122-3ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass Date: Fri Mar 24 13:50:04 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2023-03-24 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317) MachineType: LENOVO 21CBCTO1WW ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2023 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET71W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CBCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrN3AET71W(1.36):bd01/31/2023:br1.36:efr1.17:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CBCTO1WW dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2012698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025526] Re: Printer is not available in chromium snap
Hello all, I have been having the same problem (CUPS printer not showing/being available on Chromium), and seem to have fixed it as follows:- Open CUPS administration page (localhost:631/admin) under Server settings, enable 'Allow printing from the Internet' (I also have 'Allow remote administration' enabled, but I don't think this matters) Click 'Change Settings' The printer now appears in the Print dialog, under 'More...' options, and can be selected (and, more importantly, will print!) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025526 Title: Printer is not available in chromium snap Status in chromium-browser package in Ubuntu: Confirmed Status in cups package in Ubuntu: Confirmed Bug description: My printer is not available in chromium. I had the same problem in firefox but fixed it with the following command: sudo snap connect firefox:cups-control However this did not work with the chromium snap. I got the following error: snap "chromium" has no plug named "cups-control" My printer is a network printer and is automatically detected by my Kubuntu install. It works out of the box with all native apps and flatpaks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902148] Re: [snap] launchers in app's dock menu do launch general LO
Hi, Is there any progress on this? It's still an open issue in Noble snap. -- 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/1902148 Title: [snap] launchers in app's dock menu do launch general LO Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Focal: Won't Fix Bug description: LO 7.0.2 Ubuntu Focal 1) right-click on LO icon in dock (white LO icon which does launch the home page with apps and recent docs) 2) select e.g. Calc It does launch general LO (home page with apps and recent docs), not Calc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1902148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047144] [NEW] Black screen stays forever after inactivity
Public bug reported: IMPORTANT this only happens with WAYLAND but i couldn't choose wayland in the bug report options. On my Ubuntu 22.04.03 I have set the time for my screen to go black/shut off in case of inactivity in the energy settings (to save energy) to 5 minutes. So I go back to my computer after 10 minutes or so and the screen is black like it should be. Problem is, that I can't turn the screen on or what I really mean is: get back to the desktop. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19 18:56:32 UTC 2023 GCC version: ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 21 13:08:29 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CoffeeLake-H GT2 [UHD Graphics 630] [1462:120f] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 1060 Mobile] [1462:120f] InstallationDate: Installed on 2023-10-22 (59 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS73 Stealth 8RE ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=e4b68fb9-8f19-4768-9b90-c84e28ec65ef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2019 dmi.bios.release: 1.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17B5IMS.110 dmi.board.asset.tag: Default string dmi.board.name: MS-17B5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17B5IMS.110:bd05/17/2019:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnGS73Stealth8RE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17B5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17B5.1: dmi.product.family: GS dmi.product.name: GS73 Stealth 8RE dmi.product.sku: 17B5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2047144 Title: Black screen stays forever after inactivity Status in xorg package in Ubuntu: New Bug description: IMPORTANT this only happens with WAYLAND but i couldn't choose wayland in the bug report options. On my Ubuntu 22.04.03 I have set the time for my screen to go black/shut off in case of inactivity in the energy settings (to save energy) to 5 minutes. So I go back to my computer after 10 minutes or
[Desktop-packages] [Bug 2047137] Re: nvidia 390 driver from ppa segfault
** Summary changed:
- ubuntu 390 driver from ppa segfault
+ nvidia 390 driver from ppa segfault
--
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/2047137
Title:
nvidia 390 driver from ppa segfault
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were
working). On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi"
X config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect
memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event
daemon; the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2047137/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 2018672] Re: Gnome 44: GDM background configurable with gsettings
** Changed in: gnome-shell (Ubuntu Lunar) Status: Triaged => Won't Fix -- 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/2018672 Title: Gnome 44: GDM background configurable with gsettings Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Lunar: Won't Fix Bug description: [Description] The prior implementation of exposing the login screen background setting via `gsettings` is not working as expected in Gnome 44 and Ubuntu 23.04. Specifically, the background image is infact set, however, the default Gnome theme appears as an overlay on top of the com.ubuntu.login-screen schema. This appears as the default grey background with a remarkably high alpha value of 0.975 from my inspection. If you set a very high contrast background image, you can just make out the outline in beneath the greeter. My expectation would be that we can set the greeter parameters using the provided gsettings keys, and set the background-color to transparent to only display the configured background-picture-uri key. gdm@zen:~$ gsettings list-keys com.ubuntu.login-screen background-color background-picture-uri background-repeat background-size [Test Case] 1. Boot a desktop session 2. Verify that the default aubergine background is displayed in the greeter. 3. Login as the administrator of the machine 4. Install systemd-container 5. Switch to the GDM user: $ sudo machinectl shell gdm@ /bin/bash 6. Apply a different background with the command: $ gsettings set com.ubuntu.login-screen background-picture-uri 'file:///usr/share/backgrounds/Lunar-lobster-side_by_Gixo-light.png' 7. Logout 8. Verify that the image 'Lunar-lobster-side_by_Gixo-light.png' is displayed as the background of the greeter. 9. Observe the remaining grey overlay with high alpha value. After login, the background image is briefly displayed without the overlay before initiating the user gnome shell session. [Further Investigation] PRATAP-KUMAR has done some excellent work overcoming this with their GitHub project, and it appears that modifying the Gnome theme with this script correctly sets the transparency. However, perhaps there are two layers to the greeter, and even though the background image is set, the additional layer is not exposed for configuration via gsettings. https://github.com/PRATAP-KUMAR/ubuntu-gdm-set- background/blob/main/ubuntu-gdm-set- background-23.04-transparent#L168-L171 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2047137] [NEW] ubuntu 390 driver from ppa segfault
Public bug reported:
I tried to build and install package form binaries, nvidia-graphics-drivers-390
(390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I commented blacklist
in /usr/lib/modprobe.d/nvidia-graphics-drivers.conf.
But I want to use nvidia driver like on 22.10 (on 22.04/22.10 it were working).
On 23.04/23.10 it crashes.
There is an error in xorg log, it runs wrong mode, and writes:
[34.950] (II) NVIDIA(0): Validated MetaModes:
[34.950] (II) NVIDIA(0): "DFP-1:nvidia-auto-select"
[34.950] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[34.956] (--) NVIDIA(0): DPI set to (81, 80); computed from "UseEdidDpi" X
config
[34.956] (--) NVIDIA(0): option
[34.957] (II) NVIDIA: Using 6144.00 MB of virtual memory for indirect memory
[34.957] (II) NVIDIA: access.
[34.959] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon;
the daemon
...
[35.115] (II) Initializing extension DRI2
[35.115] (II) Initializing extension GLX
[35.115] (II) Initializing extension GLX
[35.115] (II) Indirect GLX disabled.
Then, in lightdm log an error with segfault appears.
I tried different configs of xorg, so I made a conclusion that nvidia drivers
are built wrong again.
My /etc/X11/xorg.conf.d/10-nvidia.conf:
Section "Files"
ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
ModulePath "/usr/lib/x86_64-linux-gnu/vdpau"
ModulePath "/usr/lib/x86_64-linux-gnu/"
ModulePath "/usr/lib/modules/6.5.0-14-generic/updates/dkms"
ModulePath "/usr/lib/xorg/modules/extensions"
ModulePath "/usr/lib/xorg/modules/drivers"
ModulePath "/usr/lib/xorg/modules/input"
ModulePath "/usr/lib/xorg/modules"
EndSection
Section "OutputClass"
Identifier "nvidia"
MatchDriver "nvidia-drm"
Driver "nvidia"
Option "AllowEmptyInitialConfiguration"
EndSection
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Dec 21 16:55:06 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
nvidia/390.157, 6.5.0-14-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-14-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 430] [1043:83c3]
InstallationDate: Installed on 2023-12-16 (5 days ago)
InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=ru_RU.UTF-8
LANGUAGE=ru_RU
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=554b729e-40d0-453e-8bb7-a893de671152 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2010
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.name: IC780M-A2
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: ECS
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd11/03/2010:br8.15:svnECS:pnIC780M-A2:pvr1.0:rvnECS:rnIC780M-A2:rvr1.0:cvnECS:ct3:cvr:sku:
dmi.product.name: IC780M-A2
dmi.product.version: 1.0
dmi.sys.vendor: ECS
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug false-gpu-hang freeze mantic ubuntu
** Attachment added: "xorg log"
https://bugs.launchpad.net/bugs/2047137/+attachment/5731603/+files/Xorg.0.log
--
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/2047137
Title:
ubuntu 390 driver from ppa segfault
Status in xorg package in Ubuntu:
New
Bug description:
I tried to build and install package form binaries,
nvidia-graphics-drivers-390 (390.157-0ubuntu8).
Now, I am writing this bug report with nouveau, because I
[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
This bug was fixed in the package gcr - 3.41.1-4 --- gcr (3.41.1-4) unstable; urgency=medium * debian/patches/gitlab_meson_resource.patch: - cherry pick a fix proposed upstream to fix a regression in the port to meson where one the gresource files isn't include anymore which is needed for pkcs11 certificates import. (lp: #1771880) Thanks Damjan Jovanovic for working on the issue -- Sebastien Bacher Wed, 20 Dec 2023 10:59:16 +0100 ** Changed in: gcr (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gcr package in Ubuntu: Fix Released Status in gnome-keyring package in Ubuntu: Triaged Status in seahorse package in Ubuntu: Triaged Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
