[Desktop-packages] [Bug 1968743] [NEW] Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu
Public bug reported: Very simple to repro. Starting Xubuntu 20.04 (bug still present in 22.04): 1. Open rhythmbox 2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window) 3. Nothing happens This was working fine in Xubuntu 18.04 This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu") Upstream claims it should be working and it works under GNOME: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 Uname: Linux 5.13.7+ x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 12 11:39:22 2022 InstallationDate: Installed on 2017-12-22 (1572 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1968743 Title: Rhythmbox Close & Quit shortcuts not working (Ctrl+W / Ctrl+Q) in Xubuntu Status in rhythmbox package in Ubuntu: New Bug description: Very simple to repro. Starting Xubuntu 20.04 (bug still present in 22.04): 1. Open rhythmbox 2. Hit Ctrl+Q (Quit) or Ctrl+W (Close window) 3. Nothing happens This was working fine in Xubuntu 18.04 This bug can be reproduced in the Live USB version (i.e. "Try Xubuntu") Upstream claims it should be working and it works under GNOME: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1961 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rhythmbox 3.4.4-1ubuntu2 Uname: Linux 5.13.7+ x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Apr 12 11:39:22 2022 InstallationDate: Installed on 2017-12-22 (1572 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: rhythmbox UpgradeStatus: Upgraded to focal on 2022-04-07 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1968743/+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 1881494] Re: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Hi, I'm just passing by. Regarding amdgpu issues related with Ryzen / Vega iGPU, there are a couple steps you can try: 1. Try a newer firmware blob. Download e.g. 1a. Download the latest firmware and unpack it https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20200519.tar.gz 1b. Backup your /lib/firmware folder 1c. sudo make install A newer firmware could fix the issue (it did for me on Ubuntu 18.04). If this fixes your problem, remember to freeze the linux-firmware package otherwise the next update will overwrite your changes and instability will come back. 2. Try a newer libdrm. Kernel updates for amdgpu go hand in hand with libdrm, but sometimes backports get these out of sync, or you try a mainline kernel but without a mainline libdrm. Download latest libdrm from https://gitlab.freedesktop.org/mesa/drm compile it and replace your Ubuntu's installation with your custom build one -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: [amdgpu] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. Also the computer never really goes into standby. The cpu fan is running all the time and the power button is fully lighted up. Nevertheless, I need to press CTRL to "wake" it, so I can access it via SSH. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). What didn't help: Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async Upgrading kernel from 5.4 to: 5.6.0-1010-oem Using the kernel parameters no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush and doing echo mem > /sys/power/state before suspend made the system acutally not crash. Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. I'll try to find the minimal combination of kernel parameters. nomodeset seems to be essential, but not sufficient. Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.p
[Desktop-packages] [Bug 1791452] Re: screen tearing in some games (fullscreen and windowed)
Try the following: xrandr --output DVI-D-0 --set TearFree 1 You may need a different output e.g. HDMI-A-0 You can list your outputs by just running "xrandr" Apply the TearFree option to all of your monitors and try again -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1791452 Title: screen tearing in some games (fullscreen and windowed) Status in xorg-server package in Ubuntu: Triaged Bug description: examples of games where I extreme screen tearing: - Cities: Skylines - Crusader Kings II ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Sep 8 19:42:44 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290/390] [1002:67b1] (rev 80) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Hawaii PRO [Radeon R9 290/390] [1458:22bd] InstallationDate: Installed on 2018-08-05 (34 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c34f72e1-74aa-410a-a0c7-b7ce55ad8b93 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H87 Pro4 dmi.board.vendor: ASRock 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.:bvrP2.20:bd08/03/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.7-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.7-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1791452/+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 1639180] Re: no login possible after update to nvidia 304.132
I can confirm this bug still persists in latest package 304.134 on XUbuntu 16.04 LTS. The card is nForce 6150SE OpenGL does not work, but I can login to xfce because it does not need a compositor. Version 304.131 works OK. It was listed in aptitude for some reason, so I could just downgrade. I cannot use nouveau on this card because it hard-crashes (entire screen becomes filled with lots of lines in a slightly diagonal screen gray & blue pattern, stops responding, only solution is to do a hard reset) when doing "intensive" graphics usage (intensive = opening a web browser and browser one or two pages). I didn't try PPA nouveau with latest drivers, just the ones provided by stock Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1639180 Title: no login possible after update to nvidia 304.132 Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Released Status in nvidia-graphics-drivers-legacy-304xx package in Debian: Fix Released Bug description: Ubuntu 16.04 LTS NVIDIA driver: - nvidia-graphics-drivers-304 - update to version 304.132 dpkg.log: upgrade nvidia-304-updates:amd64 304.131-0ubuntu3 304.132-0ubuntu0.16.04.2 - reboot - lightdm login screen - login - a few seconds some flickering - and the lightdm login screen appears again It is not possible to login. Unity is not loading. .xsession-errors: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 155 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 34 Current serial number in output stream: 35 See also bug 1634802 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
+1 to ask for a backport to 14.04. It's getting pretty annoying.
It happens every time I plug my iPad Mini 3 to the USB; it gets worst if
the system boots with the iPad already plugged ("System problem
detected" will show up as soon as I'm logged in, my screen resolution
will be wrong, then goes right, and the text is rendered differently, as
if missing antialias or using a different font)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1305699
Title:
upowerd crashed with SIGSEGV in service_client_free()
Status in upower package in Ubuntu:
Fix Released
Bug description:
it looks like nothing happend. When I switch on the PC and after loging in
this window with 'report an error/bug' appeard. so I guess it is minor.
thanks for doing :)
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: upower 0.9.23-2ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic i686
ApportVersion: 2.14.1-0ubuntu1
Architecture: i386
Date: Wed Apr 9 15:37:43 2014
ExecutablePath: /usr/lib/upower/upowerd
InstallationDate: Installed on 2014-04-04 (5 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta i386
(20140326)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:
SegvAnalysis:
Segfault happened at: 0xb74e9919 : mov
(%esi),%eax
PC (0xb74e9919) ok
source "(%esi)" (0x302e) not located in a known VMA region (needed
readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
property_list_service_client_free () from
/usr/lib/i386-linux-gnu/libimobiledevice.so.4
lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4
?? ()
g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: upowerd crashed with SIGSEGV in service_client_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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
