[Desktop-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
Hi Timo, A similar crash is observed in mesa-egl and it is resolved in Mesa master branch. Please refer the bug: https://bugs.launchpad.net/mesa/+bug/1946621 Can you help backporting the fix to "Focal" series. -- 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/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1946621] Re: Crash in libegl-mesa0 (eglReleaseThread)
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5466 https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/5466 Importance: Unknown Status: Unknown -- 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/1946621 Title: Crash in libegl-mesa0 (eglReleaseThread) Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: Crash in libegl-mesa0 (in eglReleaseThread API), please find the backtrace: #0 0xf7c86ac4 in __GI___pthread_mutex_lock (mutex=mutex@entry=0x8) at pthread_mutex_lock.c:67 #1 0xf4a7d110 in mtx_lock (mtx=0x8) at ../include/c11/threads_posix.h:223 #2 eglReleaseThread () at ../src/egl/main/eglapi.c:1713 #3 0xf6c115b8 in eglReleaseThread () at /lib/aarch64-linux-gnu/libEGL.so.1 #4 0xf7fdac00 in () at /lib/ld-linux-aarch64.so.1 #5 0xf7b4284c in __run_exit_handlers (status=0, listp=0xf7c76680 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at exit.c:108 #6 0xf7b429dc in __GI_exit (status=) at exit.c:139 #7 0xf7b2d094 in __libc_start_main (main= 0x3530 , argc=13, argv=0xf488, init=, fini=, rtld_fini=, stack_end=) at ../csu/libc-start.c:342 #8 0x4014 in _start () It crashes at: https://github.com/mesa3d/mesa/blob/mesa-21.0.3/src/egl/main/eglapi.c#L1713. 'disp' pointer is being NULL in this case. Actually nvidia's EGL backend is being loaded by glvnd in this case. But the eglReleaseThread() implementation of glvnd calls the eglReleaseThread() API of all the vendors, that's how it end-up calling the eglReleaseThread() API of Mesa backend. Refer: https://github.com/NVIDIA/libglvnd/blob/master/src/EGL/libegl.c#L806 lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 21.0.3-0ubuntu0.3~20.04.2 Candidate: 21.0.3-0ubuntu0.3~20.04.2 Version table: *** 21.0.3-0ubuntu0.3~20.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 20.0.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1946621/+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 1910908] Re: Web-login page for captive portals not opening on public wireless networks
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1910908 Title: Web-login page for captive portals not opening on public wireless networks Status in network-manager package in Ubuntu: Expired Bug description: On Ubuntu 20.04.1 LTS Focal Fossa the web page to log on to public wireless networks does not open. Without this, it is not possible to access public networks in cafes and hotels. It neither works with Firefox, Chrome nor Konqueror. I could ping the gateway so the redirection to the web login page seems to fail. In Ubuntu 16.04 and Windows 10, the login page opens as expected on the same machine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.1 Uname: Linux 5.8.0-050800-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 10 18:11:46 2021 InstallationDate: Installed on 2015-11-05 (1893 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp src 192.168.1.136 metric 302 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto dhcp scope link src 192.168.1.136 metric 302 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-09-10 (122 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-02-11T22:32:49.282695 mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected full full /org/freedesktop/NetworkManager/Devices/2 Linksys01382 1 cdc94299-456e-46e1-8487-08b668336342 /org/freedesktop/NetworkManager/ActiveConnection/4 p2p-dev-wlp3s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1910908/+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 1943025] Re: [Dell Inspiron 5301] Touch pad
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1943025 Title: [Dell Inspiron 5301] Touch pad Status in gnome-shell package in Ubuntu: Expired Bug description: Hi ! I have a little problem with my Touch pad. When i'm going to the applications page and that i do anything, suddenly i can't scroll. When i run xinput list i see that touchpad is in DLL and not in Synaptics maybe it's the problem or not, it's like that i'm doing this report. Thank you for the help ! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 8 11:54:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fb] InstallationDate: Installed on 2021-09-07 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Dell Inc. Inspiron 5301 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic root=UUID=45878a68-e793-429d-a95b-fc468f5a9ba3 ro quiet splash i8042.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0R29K5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron5301:pvr:sku09FB:rvnDellInc.:rn0R29K5:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5301 dmi.product.sku: 09FB dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1943025/+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 1950060] Re: Unable to adjust screen backlight brightness on Google Pixelbook Eve
** Summary changed: - Unable to adjust screen backlight brightness + Unable to adjust screen backlight brightness on Google Pixelbook Eve ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1950060 Title: Unable to adjust screen backlight brightness on Google Pixelbook Eve Status in linux package in Ubuntu: New Bug description: The machine is Pixelbook 2017 Eve. OS is 21.10 fresh install and there is no way to adjust the screen backlight brightness. It is 100% all the time. IN 21.04 the solution was to add to kernel command line the i915.enable_dpcd_backlight=1 however this does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 6 22:38:37 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 615 [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Google, Inc. HD Graphics 615 [1ae0:2212] InstallationDate: Installed on 2021-11-06 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 003: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:564b Realtek Semiconductor Corp. WebCamera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Google Eve ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic root=/dev/mapper/vgubuntu-root ro i915.enable_dpcd_backlight=0 quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.14 dmi.board.name: Eve dmi.board.vendor: Google dmi.board.version: 1.0 dmi.chassis.type: 31 dmi.chassis.vendor: Google dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd08/06/2021:br4.14:efr0.0:svnGoogle:pnEve:pvr1.0:sku:rvnGoogle:rnEve:rvr1.0:cvnGoogle:ct31:cvr: dmi.product.family: Google_Eve dmi.product.name: Eve dmi.product.version: 1.0 dmi.sys.vendor: Google version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950060/+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 1950040] Re: Wayland Screensharing broken in Ubuntu 21.10
** No longer affects: ubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1950040 Title: Wayland Screensharing broken in Ubuntu 21.10 Status in gnome-shell package in Ubuntu: New Status in pipewire package in Ubuntu: New Status in xdg-desktop-portal package in Ubuntu: New Bug description: Freshly installed Ubuntu 21.10, screen sharing does not work with any browser, tested the following options: - Firefox snap - Firefox deb - Chromium snap - Chromium flatpak Steps to reproduce: 1. Go to https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/#7325517390736006 2. Select to share the whole desktop in the xdg-desktop-portal 3. Notice the orange screen share indicator in Gnome-Shell but actually nothing is shared in the browser. This should be handled high priority since this is a critical feature during the pandemic. Filed against ubuntu-meta since I don't know exactly which package to blame, whether it's pipewire, xdg-desktop portal or some problem directely with mutter / gnome-shell, please reassign accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950040/+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 1950026] Re: gnome-shell leaks mem, 13.8G virt, 1.3G reserved after few days of uptime
Also 'virt' memory is not real and should be ignored. I can't tell what you mean by "reserved" memory but next time you encounter the problem please run: ps auxw | grep gnome-shell and paste the output here. ** Summary changed: - gnome-shell leaks mem, 13.8G virt, 1.3G reserved after few days of uptime + gnome-shell leaks mem, 1.3G reserved after few days of uptime -- 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/1950026 Title: gnome-shell leaks mem, 1.3G reserved after few days of uptime Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell leaks memory like crazy. after 4 days of uptime it uses 13.8G virt and 1.3G reserved mem. This is after I switched to wayland to mitigate the same issue, but on X.org it was much more crazier - about 20G virt / 1.5G reserved after one-two days of uptime, only the leak was in X.org process (2 of them, greeter and main), not gnome- shell. p.s. I do understand that gnome is the best piece of software, and I just use it incorrectly - likely I have some extension or application that is at fault. The bug report is sort of rhetorical. p.p.s. Unmodified LTS system (focal). Started to manifest about a month ago, out of the blue, no changes... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Nov 6 01:50:41 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) monitors.xml: Error: path contained symlinks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950026/+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 1950026] Re: gnome-shell leaks mem, 13.8G virt, 1.3G reserved after few days of uptime
Thanks for the bug report. First please look in $HOME/.local/share/gnome-shell and ensure there is no directory named 'extensions'. If there is one then remove it and log in again. Similarly please open the 'Extensions' app and ensure you only find the three Ubuntu extensions listed. ** Tags added: gnome-shell-leak ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1950026 Title: gnome-shell leaks mem, 1.3G reserved after few days of uptime Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell leaks memory like crazy. after 4 days of uptime it uses 13.8G virt and 1.3G reserved mem. This is after I switched to wayland to mitigate the same issue, but on X.org it was much more crazier - about 20G virt / 1.5G reserved after one-two days of uptime, only the leak was in X.org process (2 of them, greeter and main), not gnome- shell. p.s. I do understand that gnome is the best piece of software, and I just use it incorrectly - likely I have some extension or application that is at fault. The bug report is sort of rhetorical. p.p.s. Unmodified LTS system (focal). Started to manifest about a month ago, out of the blue, no changes... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sat Nov 6 01:50:41 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) monitors.xml: Error: path contained symlinks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1950026/+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 677139] Hello, 677139
https://bit.ly/31wE2Ox
--
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/677139
Title:
[Realtek ID 275] Recording problem intenal micphone , internal laptop
speacker no not work., however when you use speacker or micphone via
jacks external audio works.
Status in alsa-driver package in Ubuntu:
Expired
Bug description:
internal laptop micophone, internal laptop speackers do not work.
external speackers and external micophone via jacks will work.
this is the i386 10.04 desktop version. on sony laptop
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: roger 1563 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 22'
Mixer name : 'Intel G45 DEVIBX'
Components : 'HDA:10ec0275,104d4100,0015
HDA:80862804,104d4100,0010'
Controls : 8
Simple ctrls : 4
Date: Thu Nov 18 13:43:31 2010
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
PackageArchitecture: all
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SelectedCard: 0 Intel HDA-Intel - HDA Intel
SourcePackage: alsa-driver
Symptom: audio
Title: [Realtek ID 275] Recording problem
dmi.bios.date: 12/16/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: R0270Q3
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnINSYDE:bvrR0270Q3:bd12/16/2009:svnSonyCorporation:pnVPCS111FM:pvrC103WRC4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCS111FM
dmi.product.version: C103WRC4
dmi.sys.vendor: Sony Corporation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+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 1875172] Re: geoclue polls wpasupplicant SSID list too often, resulting in lag and packet loss
I was getting poor latency on my system with an "Intel Corporation Wireless 8265 / 8275" adapter because Geoclue was initiating scans nearly continuously. This is caused by a bug which was fixed in a Geoclue 2.5.7: https://gitlab.freedesktop.org/geoclue/geoclue/-/commit/7b52291b6e45fbb93604b838a0ba02fbbde7cd39 Ubuntu 20.04 is still affected because the latest available version is 2.5.6. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1875172 Title: geoclue polls wpasupplicant SSID list too often, resulting in lag and packet loss Status in geoclue-2.0 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install GNOME Weather, or GNOME Clocks, or basically anything that determines your location 2. In GNOME Control Center > Privacy, enable Location Services (note that I am unsure about this part; it may not even be necessary) 3. Open the application requesting your location 4. Do something latency-sensitive on WiFi, like SSH or ping Hypothesis: When an application requesting your location is running in the background and location services are enabled, it seems to tell geoclue to use NetworkManager's D-Bus API for letting wpasupplicant scan for surrounding networks very often. This causes lots of latency spikes and visible lag. Typing characters in an SSH session is rather laggy, and running something as simple as mtr 192.168.1.1 will show that every ~20 seconds the latency is over 100ms and packet loss occurs, while it's normally around 1.5ms with no packet loss. There are probably lots of other issues caused by this as well. When a WiFi adapter scans for SSID's, it has to switch channels, delaying or dropping traffic in the meanwhile. This is what causes the lag and packet loss. On phones connected to LTE this may make sense, but on a laptop which uses WiFi as its active network, this is detrimental to the connection. Changing /etc/geoclue/geoclue.conf to disable WiFi scanning, solves this problem: [wifi] enable=false On Ubuntu 18.04, this setting was the default. On Ubuntu 20.04, it has changed to 'true'. Expected behaviour: Don't break WiFi for a location scan. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 $ apt-cache policy geoclue-2.0 geoclue-2.0: Installed: 2.5.6-0ubuntu1 Candidate: 2.5.6-0ubuntu1 Version table: *** 2.5.6-0ubuntu1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1875172/+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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Committed Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT 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-shell/+bug/1898005/+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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
Steve, IIRC this crash was fixed by *either* the gnome-shell or extension fix. So the original test case would fail only while *neither* of the two fixes were applied. The gnome-shell fix made the shell API more robust so as to protect itself from crashing in the presence of a buggy extension. The gnome-shell-extension-desktop-icons fix corrects the buggy extension. This is still worthwhile because it fixes a sudden and unnecessary spike of memory and CPU usage from unthrottled timer duplication. That IIRC could still cause instability in the extension/shell based on my memory of testing a year ago. However I've tried stress testing both with and without the fix on focal today and can't see any practical difference in performance. Only technically we shouldn't declare the fix as "released" until the series file is corrected to apply the patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Incomplete Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT 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-shell/+bug/1898005/+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 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::
Mike, Can you attach (part of) your syslog showing the bug? -- 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/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: Issue is explained in detail here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Dec 16 18:56:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-01 (258 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 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/1908429/+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 1949909] Re: Bluetooth crashes on resume from suspend
Thanks but none of those crashes are related to BlueZ. And even if you did have a BlueZ crash it wouldn't cause the computer to stop responding. If you can't find any more error reports like above then please: 1. Reproduce the bug again. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt 4. Attach the resulting text file here. ** Package changed: bluez (Ubuntu) => ubuntu ** Summary changed: - Bluetooth crashes on resume from suspend + Computer stops responding on resume from suspend ** Tags added: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949909 Title: Computer stops responding on resume from suspend Status in Ubuntu: Incomplete Bug description: Crash on resume from suspend. The following messages appear and the computer stops responding: ``` [ 26.227264] Bluetooth: hci0: Reading supported features failed (-16) [ 26.228275] Bluetooth: hci0: Setting Intel telemetry ddc write event mask failed (-95) ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 4 22:50:23 2021 InstallationDate: Installed on 2021-09-16 (49 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1949909/+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 1759526] Re: Enabling 'Auto-hide the Dock' moves the clock and desktop icons
** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1569 Importance: Unknown Status: Unknown -- 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/1759526 Title: Enabling 'Auto-hide the Dock' moves the clock and desktop icons Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Bug description: The clock and desktop icons are moved 1 slot to the left when enabling Auto-hide the Dock. Reproduce: - Open the Settings > Dock - Enable Auto-hide the Dock If disabling Auto-hide, the clock and desktop icons are moved in the opposite direction (to the right). In certain situations this can make the desktop icons go off screen. Reproduce: - Open the Settings > Dock - Enable Auto-hide the Dock - Place a icon on the right edge of the screen - Disable Auto-hide the Dock Expected behavior: The clock should never move. Desktop icons that are overlapped by the launcher can move when disabling auto-hide, if this exception is not feasible the icons should never move automatically. Important notes: - The steps to reproduce may be different in later versions of Ubuntu - The Dock needs to be positioned on the left of the screen in order that the described issues are seen. However, that is the default position on installation. - Positioning the dock at the bottom or right of the screen may yield different issues or none at all. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1759526/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil
** Changed in: ssl-cert (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1945774 Title: openssl: breaks ssl-cert installation: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom Status in hplip package in Ubuntu: New Status in ssl-cert package in Ubuntu: New Status in ssl-cert package in Debian: Fix Released Bug description: Imported from Debian bug http://bugs.debian.org/990228: Package: openssl Version: 3.0.0~~alpha16-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package causes other package to fail installation/upgrading. From the attached log (scroll to the bottom...): ... Setting up openssl (3.0.0~~alpha16-1) ... Setting up libbsd0:amd64 (0.11.3-1) ... Setting up readline-common (8.1-2) ... Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ... Setting up libgdbm6:amd64 (1.19-2) ... Setting up postgresql-client-common (226) ... Setting up libedit2:amd64 (3.1-20210522-1~exp1) ... Setting up libreadline8:amd64 (8.1-2) ... Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ... Setting up libllvm11:amd64 (1:11.0.1-2) ... Setting up ssl-cert (1.1.0+nmu1) ... Could not create certificate. Openssl output was: Generating a RSA private key ..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+ ..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+ Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key' - Warning: No -copy_extensions given; ignoring any extensions in the request Cannot write random bytes: 8022CB35777F:error:127A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom dpkg: error processing package ssl-cert (--configure): installed ssl-cert package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of postgresql-common: postgresql-common depends on ssl-cert (>= 1.0.11); however: Package ssl-cert is not configured yet. ... Hmm, well, yes, /dev/urandom is not a regular file. It's a character device node. cheers, Andreas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+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 1923459] Re: evince doesn't show filename or PDF title on the title bar
This is reported at https://gitlab.gnome.org/GNOME/evince/-/issues/1583 (thanks to Michaël Berteaux @Mikenux at https://gitlab.gnome.org/GNOME/evince/-/issues/996). The bug is solved in Evince 40.2, and it looks like Ubuntu 21.10 has Evince 40.4-2, which would include the fix. However, this is worth backporting, please: it's really a weird nuisance for one of the core applications on a desktop computer. ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #1583 https://gitlab.gnome.org/GNOME/evince/-/issues/1583 ** Bug watch added: gitlab.gnome.org/GNOME/evince/-/issues #996 https://gitlab.gnome.org/GNOME/evince/-/issues/996 -- 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/1923459 Title: evince doesn't show filename or PDF title on the title bar Status in evince package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+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 1923459] Re: evince doesn't show filename or PDF title on the title bar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New => Confirmed -- 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/1923459 Title: evince doesn't show filename or PDF title on the title bar Status in evince package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1723 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Importance: Unknown Status: Unknown ** Also affects: tracker (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1917152 Title: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Status in tracker package in Ubuntu: New Bug description: Affected version Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and versions ago) I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 1.5 month ago on Gitlab Gnome without any answer nor review: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Resume: File moved with "Cut" from a window with an active search filter, and pasted in another folder on a second Nautilus window (not a subfolder), still appears on the first original screen (list is not automatically updated) - and if deleted from here, actually they disappear from the new folder ! It can occur to loose important documents - I often make direct shift-deletes, without recycler storage... Steps to reproduce I open a Nautilus window, go to a folder and make a search filter, for example 20 files appear on the window which name contains my search filter. If I select one of them, make Cut / Ctrl-X, open a new Nautilus window, go to another folder (which is not a subfolder of the first) and make Paste / Ctrl-V, it wells copy the file in the new folder. If I switch to the first Nautilus window with the original folder and search filter active, the moved file still appears on the list and I can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so I shift-delete it, it disappears from the list and only 19 files remain. Current behavior But… If I go to the second Nautilus window and the 2nd folder, the file has also disappeared from it ! File in the first window was "transformed" to a link instead of being removed, and suppressing it also deletes the file in its new folder - in my case, I lost several documents like this because of Shift-Delete and not trash use. Expected behavior After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) moved from the first one should not be still visible in the search list, there should be an automatic refresh. If I do a Copy-Paste instead of a Cut-Paste, problem does not occur: delete only removes file in the fist original folder, not on the second. If I close the search filter, it's also OK, file(s) moved no more visible. And of course, if after Cut I stay in the same Nautilus window and go to another folder to paste, no problem: bug only occurs in case of a second window opened. Thanks in advance and best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1917152/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Downgrading to libexiv2-27 0.27.2-8ubuntu2 solved the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1935770] Re: [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back
Some times I do the following: I connect my laptop to a screen with HDMI cable and in the settings set audio output to the HDMI. Later I disconnect the HDMI cable without doing anything to the sound settings and turn off the PC. When I turn on the PC again it thinks that the sound should still go to the HDMI, even though it's no longer connected. Going in to the sound settings the Output Device drop-down is blank, so it obviously knows that the HDMI is disconnected, but it just doesn't make any sound. That's the main issue I have. Not switching to HDMI sound on connecting the HDMI might be the best default, I'm not sure, but at least you might have some other preference for where you want your sound to come from when you connect it. But when you disconnect, the sound can no longer come from the HDMI, so you never want it to keep to the HDMI output, you always want it to switch to something else. My intuition about what should happen when you connect HDMI: If the current output is trough built in speakers it should automatically switch to HDMI. If the current output is trough mini-jack or other output (meaning the person is using a headset or external speakers), it should keep the current setting and not switch to HDMI. -- 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/1935770 Title: [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back Status in alsa-driver package in Ubuntu: Confirmed Bug description: When connecting a HDMI output the Audio Output won't switch automatically to the HDMI output from the Built in Speakers, it is required to enter the Settings and switch manually. When disconnecting the HDMI output the audio output won't come back to the built in Speakers as it was previously before connecting the HDMI output. I understand that may be intentional, however I do believe the audio auto switch output to HDMI when a cable is connected and then back to previously default output when HDMI is disconnected should be the default, if a different audio output would be required than a manually setting may be ok. Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabriciolb 1497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 11 10:32:46 2021 InstallationDate: Installed on 2021-06-02 (38 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [80YH, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.47 dmi.modalias: dmi:bvnLENOVO:bvr4WCN47WW:bd06/30/2020:br1.47:efr1.47:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935770/+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 1935770] Re: [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1935770 Title: [Sound Output Built in Speaker to HDMI] No auto switch from Speaker to HDMI and back Status in alsa-driver package in Ubuntu: Confirmed Bug description: When connecting a HDMI output the Audio Output won't switch automatically to the HDMI output from the Built in Speakers, it is required to enter the Settings and switch manually. When disconnecting the HDMI output the audio output won't come back to the built in Speakers as it was previously before connecting the HDMI output. I understand that may be intentional, however I do believe the audio auto switch output to HDMI when a cable is connected and then back to previously default output when HDMI is disconnected should be the default, if a different audio output would be required than a manually setting may be ok. Thanks, ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabriciolb 1497 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 11 10:32:46 2021 InstallationDate: Installed on 2021-06-02 (38 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [80YH, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2020 dmi.bios.release: 1.47 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN47WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.ec.firmware.release: 1.47 dmi.modalias: dmi:bvnLENOVO:bvr4WCN47WW:bd06/30/2020:br1.47:efr1.47:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.sku: LENOVO_MT_80YH_BU_idea_FM_ dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935770/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder
It seems that search results are given by Tracker, which is a separate app dedicated to searching. This is a config option / design choice. To fix this, Nautilus would need to ping D-Bus that the file has moved, Tracker see's this event and updates it's cache and again notifies D-Bus that this event has happened. Nautilus needs to subscribe to this (not just a one time fetch) and update any view which shows this file. -- 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/1917152 Title: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder Status in nautilus package in Ubuntu: New Bug description: Affected version Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and versions ago) I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 1.5 month ago on Gitlab Gnome without any answer nor review: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Resume: File moved with "Cut" from a window with an active search filter, and pasted in another folder on a second Nautilus window (not a subfolder), still appears on the first original screen (list is not automatically updated) - and if deleted from here, actually they disappear from the new folder ! It can occur to loose important documents - I often make direct shift-deletes, without recycler storage... Steps to reproduce I open a Nautilus window, go to a folder and make a search filter, for example 20 files appear on the window which name contains my search filter. If I select one of them, make Cut / Ctrl-X, open a new Nautilus window, go to another folder (which is not a subfolder of the first) and make Paste / Ctrl-V, it wells copy the file in the new folder. If I switch to the first Nautilus window with the original folder and search filter active, the moved file still appears on the list and I can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so I shift-delete it, it disappears from the list and only 19 files remain. Current behavior But… If I go to the second Nautilus window and the 2nd folder, the file has also disappeared from it ! File in the first window was "transformed" to a link instead of being removed, and suppressing it also deletes the file in its new folder - in my case, I lost several documents like this because of Shift-Delete and not trash use. Expected behavior After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) moved from the first one should not be still visible in the search list, there should be an automatic refresh. If I do a Copy-Paste instead of a Cut-Paste, problem does not occur: delete only removes file in the fist original folder, not on the second. If I close the search filter, it's also OK, file(s) moved no more visible. And of course, if after Cut I stay in the same Nautilus window and go to another folder to paste, no problem: bug only occurs in case of a second window opened. Thanks in advance and best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917152/+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 1917152] Re: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder
Problem is still present on Ubuntu 21.10 with Nautilus 40.2 -- 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/1917152 Title: File moved with Cut-Paste from a search filter still appears on original screen and if deleted disappears from new folder Status in nautilus package in Ubuntu: New Bug description: Affected version Nautilus 3.38 on Ubuntu 20.10 (but I also saw this bug some months and versions ago) I don't know if it's a specific Ubuntu bug or an upstream one, I reported it 1.5 month ago on Gitlab Gnome without any answer nor review: https://gitlab.gnome.org/GNOME/nautilus/-/issues/1723 Resume: File moved with "Cut" from a window with an active search filter, and pasted in another folder on a second Nautilus window (not a subfolder), still appears on the first original screen (list is not automatically updated) - and if deleted from here, actually they disappear from the new folder ! It can occur to loose important documents - I often make direct shift-deletes, without recycler storage... Steps to reproduce I open a Nautilus window, go to a folder and make a search filter, for example 20 files appear on the window which name contains my search filter. If I select one of them, make Cut / Ctrl-X, open a new Nautilus window, go to another folder (which is not a subfolder of the first) and make Paste / Ctrl-V, it wells copy the file in the new folder. If I switch to the first Nautilus window with the original folder and search filter active, the moved file still appears on the list and I can open it. I think I've made an error (Ctrl-C instead of Ctrl-X) so I shift-delete it, it disappears from the list and only 19 files remain. Current behavior But… If I go to the second Nautilus window and the 2nd folder, the file has also disappeared from it ! File in the first window was "transformed" to a link instead of being removed, and suppressing it also deletes the file in its new folder - in my case, I lost several documents like this because of Shift-Delete and not trash use. Expected behavior After Cut - Paste, in the case of 2 Nautilus windows are opened, the file(s) moved from the first one should not be still visible in the search list, there should be an automatic refresh. If I do a Copy-Paste instead of a Cut-Paste, problem does not occur: delete only removes file in the fist original folder, not on the second. If I close the search filter, it's also OK, file(s) moved no more visible. And of course, if after Cut I stay in the same Nautilus window and go to another folder to paste, no problem: bug only occurs in case of a second window opened. Thanks in advance and best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917152/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
This is not just darktable. I have files that work fine, while some other always crash. The only constant is that all files were created on a Nikon camera. Files that crash include some, but not all: Raw NEF; JPEGs created by processing NEF files on Windows using Nikon software; JPEGs created directly by camera. If I take a jpeg file that crashes, convert it to bmp or tiff, and try to open with gwenview, the file still crashes. That also points to the exiv bug. When run on a konsole, the crash is always: terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 Running Kubuntu 20.04 LTS and libexiv2-27:amd64 0.27.2-8ubuntu2.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1950092] [NEW] firefox: all bookmarks lost after snap upgrade to 701
Public bug reported: Today Firefox was updated to snap version 701. After that: * the toolbar settings are lost * all bookmarks are lost In my home directory I find: .mozilla/firefox/iw40rvsn.default-release-1 .mozilla/firefox/yr14p2lb.default .mozilla/firefox/k2x43jhu.default-release .mozilla/firefox/53wtq3js.default-release-2 Why would the snap create a new profile? Best regards Heinrich ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1950092 Title: firefox: all bookmarks lost after snap upgrade to 701 Status in firefox package in Ubuntu: New Bug description: Today Firefox was updated to snap version 701. After that: * the toolbar settings are lost * all bookmarks are lost In my home directory I find: .mozilla/firefox/iw40rvsn.default-release-1 .mozilla/firefox/yr14p2lb.default .mozilla/firefox/k2x43jhu.default-release .mozilla/firefox/53wtq3js.default-release-2 Why would the snap create a new profile? Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1950092/+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 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
The NVIDIA GeForce GT 330M device has vendor id 0x10de and device id 0x0a29 and revision 0x00a2. ROM (/firmware) version is listed as "3560". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 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-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+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 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
According to Apple Mac OS X info this hardware is as follows: MacBook Pro (15-inch, Mid 2010) CPU: 2.53 GHz Intel Core i5 RAM: 4 GB 1067 MHz DDR3 GPU: Intel HD Graphics, 288 MB The hardware *also* has NVIDIA GeForce GT 330M connected (according to OS X self-diagnostics) via 16x PCIe and it has 256 MB of RAM (Mac OS X cannot tell if this is dedicated RAM or part of system RAM like with integrated intel graphics). I believe that the OS X automaticaly switches between these GPUs according to system needs. I would guess that this is also tried by Jammy livecd and it hangs. I guess for this old hardware, automatically turning off the NVIDIA GPU and using just the Intel Graphics could be a good option if the switching is not stable. According to /proc/cpuinfo the Linux kernel successfully run the CPU up to 3.1 GHz so CPU frequency control did work absolutely fine. All the above tests were done with jammy nightly build from date 2021-11-05 obtained here: http://cdimage.ubuntu.com/ubuntukylin/daily- live/current/ and I did write the ISO image to USB memory stick using Ubuntu "Startup Disk Creator" software. I know that some newer MacBooks no longer support booting from USB memory simply by holding down ALT while booting the computer but for this hardware that still appears to work just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 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-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage
[Desktop-packages] [Bug 1950088] Re: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
Here's the full journalctl log for livecd debugging session I reported above. It appears that nautilus was totally hanging because I failed to ever open any file manager windows even after waiting for a long time. Firefox did eventually start and started to work until I tried to open file picker to attach a file to this bug - after that Firefox never recovered either. ** Attachment added: "sudo journalctl --since "2 days ago" after trying to investigate the issue and switching virtual terminals many times" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+attachment/5538674/+files/2021-11-07-journalctl.full.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 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-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1950088/+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 1950089] [NEW] package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also i
Public bug reported: (synaptic:6993): Gtk-CRITICAL **: 08:37:31.489: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. (synaptic:6993): Gtk-CRITICAL **: 08:37:33.262: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. Trying to upgrade from 21.04 to 21.10 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: gir1.2-signon-2.0 (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 7 08:31:03 2021 DuplicateSignature: package:gir1.2-signon-2.0:(not installed) Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-cZZliD/035-gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 ErrorMessage: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 InstallationDate: Installed on 2017-04-05 (1676 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: libsignon-glib Title: package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsignon-glib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute need-duplicate-check package-conflict -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1950089 Title: package gir1.2-signon-2.0 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/python3/dist- packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Status in libsignon-glib package in Ubuntu: New Bug description: (synaptic:6993): Gtk-CRITICAL **: 08:37:31.489: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. (synaptic:6993): Gtk-CRITICAL **: 08:37:33.262: ../../../../gtk/gtktreeview.c:5602 (gtk_tree_view_bin_draw): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. Trying to upgrade from 21.04 to 21.10 ProblemType: Package DistroRelease: Ubuntu 21.04 Package: gir1.2-signon-2.0 (not installed) ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Nov 7 08:31:03 2021 DuplicateSignature: package:gir1.2-signon-2.0:(not installed) Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /tmp/apt-dpkg-install-cZZliD/035-gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 ErrorMessage: trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 InstallationDate: Installed on 2017-04-05 (1676 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: libsignon-glib
[Desktop-packages] [Bug 1950088] [NEW] jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6, 2)
Public bug reported: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 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-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211105) MachineType: Apple Inc. MacBookPro6,2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:skuSystemSKU#:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy reproducible ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1950088 Title: jammy: noveau driver hangs for minutes when Firefox is started (live cd/usb, MacBookPro6,2) Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: I tried to use nightly build of Ubuntu 22.04 (jammy) on an old MacBook Pro and if I start with failsafe graphics everything seems to work really well. However, if I boot with default livecd configuration the GPU will hang when I try to launch Firefox. According to journalctl logs it appears that noveau driver or kernel DRM hangs for a long time and the computer appears totally frozen. I can still switch to terminal by pressing Ctrl-Alt-Fn-F3 and waiting a couple of minutes. Waiting for a long time (maybe 10 minutes) the system appears to work correctly again without rebooting the system. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-nouveau 1:1.0.17-1build1 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-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CasperVersion: 1.465 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 13:19:38 2021 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical
[Desktop-packages] [Bug 1934579] Re: Nautilus crashes when opening places from the dock contextmenu
This affects me too.. any updates ? -- 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/1934579 Title: Nautilus crashes when opening places from the dock contextmenu Status in nautilus package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 21.04, Nautilus crashes every time I try to open a second folder by right-clicking on the Nautilus icon in the "Favorites" left sidebar (i.e., launch panel) and selecting a bookmarked "Places" folder. Normally, this would open a second Nautilus window for the selected folder, but instead, any open Nautilus windows disappear and no window opens for the selected folder. In other words, Nautilus crashes. This did not occur on Ubuntu 20.10. This AskUbuntu post describes the same issue: https://askubuntu.com/questions/1344175/nautilus-crashes-when-trying- to-open-another-window-by-right-clicking-the-nautil If, instead, I right-click the Nautilus icon, select "New Window" and then select the desired "Places" folder from the left sidebar of the newly opened window, Nautilus does not crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jul 4 13:36:13 2021 InstallationDate: Installed on 2020-02-05 (514 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-06-30 (4 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1934579/+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 1732991] Re: I can't use mouse buttons to navigate Ubuntu Desktop Guide
Fixed in 21.10. ** Changed in: yelp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1732991 Title: I can't use mouse buttons to navigate Ubuntu Desktop Guide Status in yelp package in Ubuntu: Fix Released Bug description: Extra mouse buttons work elsewhere in the system, e.g., in Nautilus and Firefox, but not in the Desktop Guide. I'd expect to be able to browse forwards and backwards with the extra mouse buttons. I suspect that this is a bug. Tested in Ubuntu 17.10, Wayland session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1732991/+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 1950075] Re: nautilus crashes when 1 window is open and open new window directly to folder
syslog, dmesg and strace for bug #1950075 ** Attachment added: "1950075.tar.xz" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+attachment/5538650/+files/1950075.tar.xz -- 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/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+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 1947746] Re: [Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F
I noticed that the file /etc/udev/rules.d/70-snap.firefox.rules does not
have any rules for the Trezor devices.
In my Trezor rules file, /etc/udev/rules.d/51-trezor.rules, that can be
downloaded from https://data.trezor.io/udev/51-trezor.rules, I appended
the FireFox snap TAG to one of the existing lines to get, for example:
KERNEL=="hidraw*", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="53c1",
MODE="0660", GROUP="plugdev", TAG+="uaccess", TAG+="udev-acl",
TAG+="snap_firefox_firefox"
Unplug/replug the device and then try again in FireFox. That worked for me.
So, the fix is probably for FireFox to include the Trezor U2F device configs in
whatever winds up generating /etc/udev/rules.d/70-snap.firefox.rules
--
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/1947746
Title:
[Snap] Ubuntu Firefox installed from snap cannot use Trezor U2F
Status in firefox package in Ubuntu:
New
Bug description:
Trezor U2F security key doesn't work with firefox snap after updating
to Ubuntu 21.10, but works with apt debian firefox package.
Steps to reproduce:
1) Insert Trezor U2F security key in USB port.
2) Launch `run snap firefox` (it is the default on Ubuntu 21.10)
3) Test https://demo.yubico.com/webauthn-technical/registration
It works well on Ubuntu 21.04 and on traditional apt debian
installation.
$ snap list firefox
Name Version Rev Tracking Publisher Notes
firefox 93.0-1 631 latest/stable mozilla✓ -
$ snap connections firefox
Interface PlugSlot
Notes
audio-playbackfirefox:audio-playback :audio-playback
-
audio-record firefox:audio-record:audio-record
-
avahi-observe firefox:avahi-observe :avahi-observe
-
browser-support firefox:browser-sandbox :browser-support
-
camerafirefox:camera :camera
-
content[gnome-3-38-2004] firefox:gnome-3-38-2004
gnome-3-38-2004:gnome-3-38-2004 -
content[gtk-3-themes] firefox:gtk-3-themes
gtk-common-themes:gtk-3-themes -
content[icon-themes] firefox:icon-themes
gtk-common-themes:icon-themes-
content[sound-themes] firefox:sound-themes
gtk-common-themes:sound-themes -
cups-control firefox:cups-control:cups-control
-
dbus - firefox:dbus-daemon
-
desktop firefox:desktop :desktop
-
desktop-legacyfirefox:desktop-legacy :desktop-legacy
-
gsettings firefox:gsettings :gsettings
-
hardware-observe firefox:hardware-observe:hardware-observe
-
home firefox:home:home
-
joystick firefox:joystick-
-
mpris - firefox:mpris
-
network firefox:network :network
-
network-observe firefox:network-observe -
-
openglfirefox:opengl :opengl
-
personal-filesfirefox:dot-mozilla-firefox :personal-files
-
removable-media firefox:removable-media :removable-media
-
screen-inhibit-controlfirefox:screen-inhibit-control
:screen-inhibit-control -
system-files firefox:etc-firefox-policies:system-files
-
system-packages-doc firefox:system-packages-doc
:system-packages-doc -
u2f-devices firefox:u2f-devices :u2f-devices
-
unity7firefox:unity7 :unity7
-
upower-observefirefox:upower-observe :upower-observe
-
wayland firefox:wayland :wayland
-
x11 firefox:x11 :x11
-
$ cat /etc/os-release
PRETTY_NAME="Ubuntu 21.10"
NAME="Ubuntu"
VERSION_ID="21.10"
VERSION="21.10 (Impish Indri)"
VERSION_CODENAME=impish
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
[Desktop-packages] [Bug 1950075] Re: nautilus crashes when 1 window is open and open new window directly to folder
From bug #1950083 1) Ubuntu Jammy Jellyfish (development branch) 20211107 daily-live 2) nautilus (1:40.2-1ubuntu1) 3) A new window should open 4) Files crashes altogether ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 16:16:50 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2021-11-07 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211107) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f846593510f: mov 0x8(%rbp),%rax PC (0x7f846593510f) ok source "0x8(%rbp)" (0x5570009c) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_display_error_trap_push () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_screen_supports_net_wm_hint () from /lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with SIGSEGV in gdk_x11_display_error_trap_push() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf separator: usr_lib_nautilus: evince 41.2-1 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share 0.7.3-2ubuntu4 ** Attachment added: "Screencast from 11-07-2021 04:24:47 PM.webm" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+attachment/5538649/+files/Screencast%20from%2011-07-2021%2004%3A24%3A47%20PM.webm -- 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/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+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 1279380] Re: [14.04] [Gnome-Settings-Daemon] unable to save default audio output device
This bug is still present in Ubuntu 21.10 (and 21.04 and 20.10 for what I have personally verified). Is there any update for it? ** Summary changed: - [14.04] [Gnome-Settings-Daemon] unable to save default audio output device + [21.10] [Gnome-Settings-Daemon] unable to save default audio output device ** Summary changed: - [21.10] [Gnome-Settings-Daemon] unable to save default audio output device + [14.04][21.10] [Gnome-Settings-Daemon] unable to save default audio output device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1279380 Title: [14.04][21.10] [Gnome-Settings-Daemon] unable to save default audio output device Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: When more than one audio output source are available, gnome-settings usually picks the 1st one on the list. There is no way to save any alternate choice. For example I have: HDMI/DisplayPort2 Built-in Audio Digital Output (S/PDIF) Built-in Audio Analog Output Built-in Audio. The default output each time the system boots is set to HDMI/DisplayPort2 Built-in Audio and I have to manually change it to Analog Output Built-in Audio to which my PC speakers are connected. There is no "save this as default" option on this screen. So, I have do this each time I boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 12 09:18:30 2014 InstallationDate: Installed on 2013-04-10 (308 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-02-08 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1279380/+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 1950075] Re: nautilus crashes when 1 window is open and open new window directly to folder
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: Confirmed Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1950075/+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 1950075] [NEW] nautilus crashes when 1 window is open and open new window directly to folder
Public bug reported: Description:Ubuntu 21.10 Release:21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Description changed: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 - When I have 1 window or more opened from nautilus and left click on bar + When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' - b'org.gnome.nautilus.window-state' b'maximized' b'true' - b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" + b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' + b'org.gnome.nautilus.window-state' b'maximized' b'true' + b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=es_ES.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: - evince40.4-2 - file-roller 3.40.0-2 - nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 - nautilus-share0.7.3-2ubuntu4 + evince40.4-2 + file-roller 3.40.0-2 + nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 + nautilus-share0.7.3-2ubuntu4 -- 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/1950075 Title: nautilus crashes when 1 window is open and open new window directly to folder Status in nautilus package in Ubuntu: New Bug description: Description: Ubuntu 21.10 Release: 21.10 GNOME nautilus 40.2 When I have 1 window or more opened from nautilus and right click on bar icon and then click a folder like Downloads ord Desktop all windows are suddenly closed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 7 10:17:06 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(890, 548)' b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-11-06 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller
[Desktop-packages] [Bug 1741074]
> S2(Serious) Major functionality/product severely impaired and a satisfactory workaround does not exist -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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 1741074]
Flatpak counterpart: bug 1621763. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+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
