[Desktop-packages] [Bug 1904819] Re: gnome-shell uses 100% cpu when screen blanked
Thanks for the bug report. Your system log is certainly full of a lot of messages so it's easy to believe you might have high CPU too. But I can't tell what part of gnome-shell they came from. Since so many bugs are caused by extensions, and nobody else is reporting this issue, the first thing we need to check is all: 'alternate-...@gnome-shell-extensions.gcampax.github.com', 'dash-to- d...@micxgx.gmail.com', 'screenshot-window-sizer@gnome-shell- extensions.gcampax.github.com', 'gsconn...@andyholmes.github.io' Please uninstall or just disable all of them in the Extensions app, then log out and log in again. Does the problem still occur? If so then it might be this: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3098 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: performance ** Tags added: regression-release ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3098 Importance: Unknown Status: Unknown -- 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/1904819 Title: gnome-shell uses 100% cpu when screen blanked Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Recently I've noticed gnome-shell eating 100% of the CPU when the screen is blanked due to the session going idle. This seems to have started happening sometime after upgrading to groovy back when it was still in beta. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:04:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-13 (828 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-24 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1904819/+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 1713775] Re: [USB-Audio - Logitech BRIO, recording] fails on suspend/resume
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/1713775 Title: [USB-Audio - Logitech BRIO, recording] fails on suspend/resume Status in alsa-driver package in Ubuntu: Confirmed Bug description: My Logitech BRIO webcam's mic doesn't pass audio after suspend/resume cycles on my desktop. The ALSA interfaces are present and the mic devices appear in pulseaudio and the Ubuntu audio settings applet, but no audio is seen via arecord or the volume meter in the audio settings applet. It doesn't happen on every suspend/resume and I'm trying to establish the pattern. I think it may be that this happens only on suspend/resume where a handle to the mic was left open. For example, it took 3 suspend/resume cycles to generate this error report, and the one that finally reproed the issue was the one where I left the mic selection panel of the audio settings panel open. I think the open handle to the mic to supply the volume meter may have been what broke it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: rhett 421 F...m pulseaudio /dev/snd/controlC2: rhett 421 F pulseaudio /dev/snd/controlC0: rhett 421 F pulseaudio /dev/snd/controlC1: rhett 421 F pulseaudio CurrentDesktop: Unity Date: Tue Aug 29 12:53:04 2017 InstallationDate: Installed on 2016-11-21 (280 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Logitech BRIO - Logitech BRIO Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Logitech BRIO, recording] fails after a while UpgradeStatus: Upgraded to xenial on 2017-07-24 (36 days ago) dmi.bios.date: 09/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2202 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2202:bd09/19/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1713775/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi @E (mantsje), Just try one of the patches mentioned here (e.g. #179). My touchpad also was making click events when moving fingers on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Desktop-packages] [Bug 1904819] [NEW] gnome-shell uses 100% cpu when screen blanked
Public bug reported: Recently I've noticed gnome-shell eating 100% of the CPU when the screen is blanked due to the session going idle. This seems to have started happening sometime after upgrading to groovy back when it was still in beta. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:04:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-13 (828 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-24 (55 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy wayland-session -- 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/1904819 Title: gnome-shell uses 100% cpu when screen blanked Status in gnome-shell package in Ubuntu: New Bug description: Recently I've noticed gnome-shell eating 100% of the CPU when the screen is blanked due to the session going idle. This seems to have started happening sometime after upgrading to groovy back when it was still in beta. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Thu Nov 19 17:04:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-08-13 (828 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RebootRequiredPkgs: linux-image-5.8.0-26-generic linux-base linux-image-5.8.0-28-generic linux-base RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-24 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904819/+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 402892] Re: Mouse cursor gets stuck in "drag and drop" mode
I discovered a way to consistently trigger this. I don't know if all these steps are necessary, but it works for me consistently this way. Configuration: - Ubuntu MATE 20.10 - caja version 1.24.0 - Evolution version 3.38.1-1 Steps to Reproduce: 1. In Evolution, open the 'Compose Message' window. I have it set by default to 'Plain Text' editing mode, and attachment bar collapsed. 2. Open caja and navigate to the desired file. 3. drag & drop the file in the message body. This should result in the full file path URI being displayed as the message. 4. press `CTRL+Z` (Undo). 5. Now drag the same file again, over the message body, into the (collapsed) attachment bar. 6. Your mouse should now be stuck in DND mode, requiring `pkill caja` to release it. -- 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/402892 Title: Mouse cursor gets stuck in "drag and drop" mode Status in OpenShot Video Editor: New Status in X.Org X server: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in rapidsvn package in Ubuntu: Confirmed Bug description: Binary package hint: rapidsvn When clicking on the Bookmark root or on one of the bookmarks below the mouse cursor gets stuck in "drag n drop" mode, blocking all keyboard entry and also mouse clicks for the the whole GUI (systemwide). Unfortunately I cannot provide any debug or other information, as I have to reboot everytime. I am running Ubuntu 9.04 with compiz enabled. Many thanks in advance for your help with this problem, /nxT To manage notifications about this bug go to: https://bugs.launchpad.net/openshot/+bug/402892/+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 1904777] Re: Xorg randomly crashes under xrdp
Or just look in your system journal for "Assertion". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg randomly crashes under xrdp Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm using xrdp to log into a remote machine. Since upgrading it to 20.04, my sessions started failing randomly. They would either not start at all, or get interrupted hours later. Here's a backtrace I found in a .xorgxrdp.log [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off [ 92697.915] rdpInDeferredRepeatCallback: [ 92697.916] rdpkeybChangeKeyboardControl: [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off [ 92712.569] (EE) [ 92712.586] (EE) Backtrace: [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c] [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7ffa5424f41f] [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7ffa5408c18b] [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7ffa5406b859] [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a] [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7ffa5407cf36] [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5559b0103095] [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5559b01046e2] [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4] [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5559affd6f34] [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4] [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7ffa5406d0b3] [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e] [ 92712.621] (EE) [ 92712.621] (EE) Fatal server error: [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting [ 92712.621] (EE) [ 92712.623] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for additional information. [ 92712.623] (EE) [ 92712.627] rdpmouseControl: what 4 [ 92712.627] rdpkeybControl: what 4 [ 92712.629] rdpLeaveVT: [ 92712.634] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 18 20:07:37 2020 DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609] MachineType: HP ProLiant MicroServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 07/29/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.product.sku: 664447-425 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1904777] Re: Xorg randomly crashes under xrdp
Looks like an assertion failure so this is probably bug 1861609. Please try installing the debug symbols to see if that clarifies the situation next time it crashes. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg randomly crashes under xrdp Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm using xrdp to log into a remote machine. Since upgrading it to 20.04, my sessions started failing randomly. They would either not start at all, or get interrupted hours later. Here's a backtrace I found in a .xorgxrdp.log [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off [ 92697.915] rdpInDeferredRepeatCallback: [ 92697.916] rdpkeybChangeKeyboardControl: [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off [ 92712.569] (EE) [ 92712.586] (EE) Backtrace: [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c] [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7ffa5424f41f] [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7ffa5408c18b] [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7ffa5406b859] [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a] [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7ffa5407cf36] [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5559b0103095] [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5559b01046e2] [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4] [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5559affd6f34] [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4] [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7ffa5406d0b3] [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e] [ 92712.621] (EE) [ 92712.621] (EE) Fatal server error: [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting [ 92712.621] (EE) [ 92712.623] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for additional information. [ 92712.623] (EE) [ 92712.627] rdpmouseControl: what 4 [ 92712.627] rdpkeybControl: what 4 [ 92712.629] rdpLeaveVT: [ 92712.634] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 18 20:07:37 2020 DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609] MachineType: HP ProLiant MicroServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 07/29/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.product.sku: 664447-425 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
[Desktop-packages] [Bug 1899152] Re: [intel G33] Resolution limited to 1024x768
It looks like the system can't get the screen resolution information from the monitor over the VGA connection. This might be a connection problem or it might be a kernel bug. Please: 1. Run this command: grep . /sys/class/drm/*/modes > drmmodes.txt and attach the resulting text file here. 2. Try a different VGA cable if you can find one. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Invalid => New ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1899152 Title: [intel G33] Resolution limited to 1024x768 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-intel package in Ubuntu: Incomplete Bug description: Defaultly it is set to 1024x768. But my screen resolution is 1440x400. I tried using terminal to add newmode and saved with the desired resolution. When I aplied the new one, the system gets hanged everytime. Previuosly I used 14.04 version. Then there was no issue. I added newmode using terminal. And next it was fine. But now it is not allowing me to set. Please make this issue clear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 9 16:03:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2020-10-02 (6 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=948d3ae0-06d2-4522-8970-f6183d8b94fa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A 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/linux/+bug/1899152/+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 1904717] Re: Settings for external keyboard and mouse are not persisted
*** This bug is a duplicate of bug 1899206 *** https://bugs.launchpad.net/bugs/1899206 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1899206, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1899206 Input device settings not applied on hotplug/reconnect/resume in Xorg sessions -- 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/1904717 Title: Settings for external keyboard and mouse are not persisted Status in gnome-shell package in Ubuntu: New Bug description: The equipment I'm using is: - Laptop: Dell XPS 13 9380 - Mouse: Anker AK-UBA 2.4G Wireless Vertical Ergonomic Optical Mouse - Keyboard: Microsoft Sculpt Ergonomic Keyboard - Ubuntu version: 20.04.1 I often use an external mouse and keyboard. I have the mouse set to natural scrolling and the speed set to full. For the keyboard I remap Caps Lock to Esc (using Tweaks 3.34.0). What happens: When I connect the keyboard and mouse to the exact same USB ports as before I expect the above settings to persist. What should happen: The mouse and keyboard settings should persist. If you go to the mouse and keyboard settings, it appears as though they have persisted but in order for those settings to work they need to be toggled off and on again. Either the settings should actually persist or the mouse and keyboard settings should show the real applied settings, i.e. toggled off. This bug was not present prior to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904717/+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 1904765] Re: Resolution not set or inappropriate
*** This bug is a duplicate of bug 1899152 *** https://bugs.launchpad.net/bugs/1899152 We ignored bug 1899152 because you closed it :) I have now reopened bug 1899152 for this. ** This bug has been marked a duplicate of bug 1899152 [intel G33] Resolution limited to 1024x768 -- 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/1904765 Title: Resolution not set or inappropriate Status in xorg package in Ubuntu: New Bug description: The resolution is stuck at 1024x768. My screen can display 1440x900. I added the needed resolution to the settings. Even then it is not changing to the new. It is reverting back again and again to 1024x768. This is the second time I am reporting this issue to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2020-10-21 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ddc3d754-e174-4bc9-8cb7-7d4c277bb4e9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/xorg/+bug/1904765/+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 1904470] Re: Monitor fails to wake after lock when dash-to-panel is loaded
** Summary changed: - 100Hz monitor fails to wake after lock + Monitor fails to wake after lock when dash-to-panel is loaded ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash- to-panel (Ubuntu) ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: Incomplete => New -- 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/1904470 Title: Monitor fails to wake after lock when dash-to-panel is loaded Status in gnome-shell-extension-dash-to-panel package in Ubuntu: New Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1904470/+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 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
There is no mechanism to make it come faster. It's already on the way as a proposed groovy update: https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1 You can't get faster than that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+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 1766775] Re: Notifications do not disappear
** Changed in: gnome-shell (Ubuntu) Status: Fix Released => Confirmed -- 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/1766775 Title: Notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+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 1903230] Re: Mutter release 3.36.7
The only leak fix in 3.36.7 is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1449 but that one may never be noticeable so may not be the issue you describe. If you experience leaks then remove any extensions you have installed. If the problem keeps happening after that then open a new bug by running: ubuntu-bug gnome-shell -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Triaged Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+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 1890958] Re: exfat month modification time increasing by simple consulting with "properties"
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/1890958 Title: exfat month modification time increasing by simple consulting with "properties" Status in nautilus package in Ubuntu: Confirmed Bug description: Ubuntu 20.04, every updates done. Each time I insert the same SDXC (64 GB, exFAT) card in my PC and show the modification time of always the same file by right clicking on it and then selecting "properties" in nautilus I notice that the month modification time has increased with 1 month. And one year more when jumping from december to january. So, after several times inserting this card, that video file made april 28th 2020 shows now the modification time june 28th 2021, 14 months later. The modification time is important. It must be hold right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1890958/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive
... sorry, I never worked with repositories...
may someone check this:
https://code.launchpad.net/~arter97/+archive/ubuntu/exfat-dev
exfat-dkms - 5.8~2arter97~ubuntu20.04.1 (maybe also in the other versions?)
in the file misc.c:
void exfat_get_entry_time(struct exfat_sb_info *sbi, struct timespec64 *ts,
u8 tz, __le16 time, __le16 date, u8 time_cs)
{
u16 t = le16_to_cpu(time);
u16 d = le16_to_cpu(date);
ts->tv_sec = mktime64(1980 + (d >> 9), d >> 5 & 0x000F, d & 0x001F,
t >> 11, (t >> 5) & 0x003F, (t & 0x001F) << 1);
...
shouldn't it be in line 82/83
ts->tv_sec = mktime64(1980 + (d >> 9), ((d >> 5) - 1) & 0x000F, d &
0x001F,
t >> 11, (t >> 5) & 0x003F, (t & 0x001F) << 1);
???
as month is given from 0-11 as far as i know, but in exfat from 1-12
(https://docs.microsoft.com/en-us/windows/win32/fileio/exfat-
specification#748-timestamp-fields).
(other way round seems to be correct in lines 108-110:
time64_to_tm(ts->tv_sec, 0, );
t = (tm.tm_hour << 11) | (tm.tm_min << 5) | (tm.tm_sec >> 1);
d = ((tm.tm_year - 80) << 9) | ((tm.tm_mon + 1) << 5) | tm.tm_mday;
)
may someone check and fix this, as I don't know how.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872504
Title:
date modified is wrong for files on an exfat formatted drive
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
When using exfat formatted drives (e.g. my camera card) with focal
fossa any access causes the date modified to be set, even when it
would not normally be set, and it is set a month into the future.
Installing exfat-fuse and exfat-utils results in the correct
behaviour.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-release-upgrader-core 1:20.04.18
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 17:27:30 2020
InstallationDate: Installed on 2020-04-12 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive
The error occurs even without writing to the hard disk. I didn't find the exact procedure to reproduce the error, it seems to happen during mounting or unmounting, maybe only from nautilus, but even in this case I don't have the changes of the date any time. The Date doesn't change by 30 days but 1 month and there are only some files affected, but repeatedly. Even that not consistently. On my hard drive there is only one directory and the subdirectories affected: unmount + save remove from nautilus/mount automatically via entry in fstab, listings from terminal, from a single session on Nov 18 2020(!), here only the files "Fuga.blend1, Materials.blend1, Mixereinstellungen.vmsms" affeced - I have no idea, what the common feature may be. sebastian@osamu:/media/4tbp/Eigene Videoprojekte/Fuga BWV 863$ ls -l insgesamt 106752 -rwxr-xr-x 1 root root 1016 Dez 9 2020 Ablauf.txt -rwxr-xr-x 1 root root 2990398 Dez 5 2020 'BWV 863 (I, 18 gis-moll) Selbst.mp3' -rwxr-xr-x 1 root root 1325052 Dez 12 2020 Fuga.blend -rwxr-xr-x 1 root root 1325148 Jul 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root73990 Dez 9 2020 'Fuga BWV 863.aup' drwxr-xr-x 4 root root 131072 Dez 5 2020 'Fuga BWV 863_data' -rwxr-xr-x 1 root root 231661 Dez 18 2020 Fuga_take2.aup drwxr-xr-x 4 root root 131072 Dez 18 2020 Fuga_take2_data -rwxr-xr-x 1 root root 4376783 Dez 9 2020 'Leuchtender Boden Cycles.png' -rwxr-xr-x 1 root root 1185996 Dez 9 2020 Materials.blend -rwxr-xr-x 1 root root 1185996 Jul 9 2021 Materials.blend1 -rwxr-xr-x 1 root root 2966841 Dez 9 2020 MIDI.mp3 -rwxr-xr-x 1 root root 151 Jul 9 2021 Mixereinstellungen.vmsms -rwxr-xr-x 1 root root 249378 Dez 5 2020 Synchro.kdenlive drwxr-xr-x 2 root root 131072 Dez 18 2020 take2_video -rwxr-xr-x 1 root root84884 Dez 6 2020 Test1.kdenlive -rwxr-xr-x 1 root root 91579391 Jan 6 2021 Test1.webm drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test Alphaclips' drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test-Rohdaten' no file used, just removed and mounted again: -rwxr-xr-x 1 root root 1016 Dez 9 2020 Ablauf.txt -rwxr-xr-x 1 root root 2990398 Dez 5 2020 'BWV 863 (I, 18 gis-moll) Selbst.mp3' -rwxr-xr-x 1 root root 1325052 Dez 12 2020 Fuga.blend -rwxr-xr-x 1 root root 1325148 Aug 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root73990 Dez 9 2020 'Fuga BWV 863.aup' drwxr-xr-x 4 root root 131072 Dez 5 2020 'Fuga BWV 863_data' -rwxr-xr-x 1 root root 231661 Jan 18 2021 Fuga_take2.aup drwxr-xr-x 4 root root 131072 Dez 18 2020 Fuga_take2_data -rwxr-xr-x 1 root root 4376783 Dez 9 2020 'Leuchtender Boden Cycles.png' -rwxr-xr-x 1 root root 1185996 Dez 9 2020 Materials.blend -rwxr-xr-x 1 root root 1185996 Aug 9 2021 Materials.blend1 -rwxr-xr-x 1 root root 2966841 Dez 9 2020 MIDI.mp3 -rwxr-xr-x 1 root root 151 Aug 9 2021 Mixereinstellungen.vmsms -rwxr-xr-x 1 root root 249378 Dez 5 2020 Synchro.kdenlive drwxr-xr-x 2 root root 131072 Dez 18 2020 take2_video -rwxr-xr-x 1 root root84884 Dez 6 2020 Test1.kdenlive -rwxr-xr-x 1 root root 91579391 Jan 6 2021 Test1.webm drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test Alphaclips' drwxr-xr-x 2 root root 131072 Dez 5 2020 'Video Test-Rohdaten' ... -rwxr-xr-x 1 root root 1325148 Sep 9 2021 Fuga.blend1 -rwxr-xr-x 1 root root 1325148 Okt 9 2021 Fuga.blend1 And: sebastian@osamu:/media/4tbp/Eigene Videoprojekte/Fuga BWV 863$ find -newer Fuga_take2.aup -printf '%Ac %Cc %Tc %p\n' Mo 31 Dez 1979 01:00:00 CET Sa 09 Okt 2021 18:16:36 CEST Sa 09 Okt 2021 18:16:38 CEST ./Mixereinstellungen.vmsms Mo 31 Dez 1979 01:00:00 CET Sa 09 Okt 2021 17:12:02 CEST Sa 09 Okt 2021 20:28:58 CEST ./Materials.blend1 Mo 31 Dez 1979 01:00:00 CET Sa 06 Nov 2021 00:30:36 CET Sa 09 Okt 2021 20:30:06 CEST ./Fuga.blend1 -> last status change and last modification timestamp may change independently as in "Fuga.blend1", but not in the other two files. Hope that information helps to find the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr
[Desktop-packages] [Bug 1904793] [NEW] upower abruptly thinks battery has gone to 1% and hibernates
Public bug reported: Whenever I go on battery after 20-30 minutes upower will very abruptly think my battery is at 1% and force my laptop to hibernate. This seems to happen at random times, I've seen it when my battery was reported to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up forcing me to hard reset the machine. I suspect this is because upower thinks my battery is still at 1% when its not. My laptops firmware correctly reports the battery level and shows that I have plenty of power remaining. The last few times this happened I kept powertop up which shows that I do have plenty of power even when upower thinks I have none. Essentially this makes my laptop unusable on battery. Laptop: Lenovo X1 Carbon Extreme Gen 2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 13:59:24 2020 InstallationDate: Installed on 2019-12-29 (325 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1904793 Title: upower abruptly thinks battery has gone to 1% and hibernates Status in upower package in Ubuntu: New Bug description: Whenever I go on battery after 20-30 minutes upower will very abruptly think my battery is at 1% and force my laptop to hibernate. This seems to happen at random times, I've seen it when my battery was reported to be 90%, 76%, 45%, 25%, etc. If I try to resume Ubuntu locks up forcing me to hard reset the machine. I suspect this is because upower thinks my battery is still at 1% when its not. My laptops firmware correctly reports the battery level and shows that I have plenty of power remaining. The last few times this happened I kept powertop up which shows that I do have plenty of power even when upower thinks I have none. Essentially this makes my laptop unusable on battery. Laptop: Lenovo X1 Carbon Extreme Gen 2 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: upower 0.99.11-2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Nov 18 13:59:24 2020 InstallationDate: Installed on 2019-12-29 (325 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: upower UpgradeStatus: Upgraded to groovy on 2020-10-23 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1904793/+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 1842886] Re: Yaru-dark shell menus and dialogs are not dark
I followed this guide and it sorted me out: https://allthings.how/how- to-fully-enable-dark-mode-in-ubuntu-20-04-including-calendar -- 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/1842886 Title: Yaru-dark shell menus and dialogs are not dark Status in gnome-shell package in Ubuntu: Confirmed Bug description: When you selected a dark application theme, the gnome-shell top bar menus used to also switch to match the theme (ie light text on a dark background) - eg see the screenshot showing the top-bar calendar at https://micheleg.github.io/dash-to-dock/news/2015/03/01/approaching- gnome-3.16.html). This is no longer the case - see attached screenshot for yark-dark. It's the same with adwaita-dark. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 5 16:01:07 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-01 (65 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1842886/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
I can confirm this was fixed with version 340.108-0ubuntu5.20.10.2. The module failed to build after upgrading to groovy, but after installing the package from proposed it worked. uname -a: Linux ubuntu-desktop 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
This bug was fixed in the package gtk+3.0 - 3.24.23-1ubuntu2 --- gtk+3.0 (3.24.23-1ubuntu2) hirsute; urgency=medium * debian/patches/fontchooser_Fix_family-only_mode.patch: - Show regular monospace fonts in gnome-terminal's profile editor and not arbitrary font styles (LP: #1900729) -- Gunnar Hjalmarsson Mon, 02 Nov 2020 10:45:57 +0100 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Fix Committed Status in gnome-terminal source package in Groovy: Fix Released Status in gtk+3.0 source package in Groovy: Won't Fix Bug description: [Impact] When you want to select a monospace font in gnome-terminal's profile editor, it does not always show the regular font but rather an arbitrarily chosen one. The proposed gnome-terminal upload reverts an upstream commit, which means that all weights/styles for monospace fonts are shown. It takes us back to how it works in focal. [Test case] * Install the binaries built from gnome-terminal in groovy-proposed * Relogin * Open gnome-terminal -> Preferences and open the window for selecting a custom font for the profile. Find that it shows all available monospace fonts. Confirm for a few fonts that they can actually be selected without issues. [Where problems could occur] This is a one liner in gnome-terminal and does not affect other applications. So given a successful verification of the test case, this ought to be a safe change. [Other info] Please note that this particular change has not been made in hirsute. The reason is that we intend to follow upstream there, which means that the issue will be resolved through changes in gtk and pango. [Original description] trying to change the font in gnome-terminal, only the italics version of the ubuntu mono font is shown, as can be seen in the attachment. on the other hand, when changing fonts in the appearance settings, i can see all variants of the ubuntu fonts... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-terminal 3.38.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Oct 20 16:56:57 2020 InstallationDate: Installed on 2020-10-20 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201019.1) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
I meant HFP profile. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
... and DND from Nautilus to another Nautilus window work well. So Nautilus From/to Desktop only seems to freeze gnome. -- 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/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell in Ubuntu 20.10 (beta). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@pesso82 There is your problem. Those headphones do not support HSP 1.6 profile, only 1.5. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Hello, Same issue for me, I can't drag and drop since last upgrade to 20.10. For instance, drag file(s) from Desktop and drop to an open directory doesn't work. ...But drag file from Desktop and drop to an icon closed directory work. Dell OptiPlex-7010 Description:Ubuntu 20.10 Release:20.10 Codename: groovy -- 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/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell in Ubuntu 20.10 (beta). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
Yes, that’s the point I’m try to use JBL T450BT These are the available specs on official site Control and Connection Specifications Bluetooth profilesHFP v1.5, HSP v1.2, A2DP v1.2, AVRCP v1.4 Bluetooth frequency2.402GHz-2.48GHz Bluetooth transmitted modulationGFSK,π/4DQPSK, 8DPSK Bluetooth transmitter power0-4 d I don’t find mSBC information, so it’s supposed they don’t support mSBC What about Sony WH-CH700? They seems to support mSBC, but who knows.. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1904789] [NEW] [snap] Cannot confirm security exception
Public bug reported: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception Status in thunderbird package in Ubuntu: New Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+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 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Oh sorry - yes, it's a typo. Sorry! I use Ubuntu 20.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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 1904777] [NEW] Xorg randomly crashes under xrdp
Public bug reported: I'm using xrdp to log into a remote machine. Since upgrading it to 20.04, my sessions started failing randomly. They would either not start at all, or get interrupted hours later. Here's a backtrace I found in a .xorgxrdp.log [ 92697.914] rdpkeybChangeKeyboardControl: autoRepeat off [ 92697.915] rdpInDeferredRepeatCallback: [ 92697.916] rdpkeybChangeKeyboardControl: [ 92697.916] rdpkeybChangeKeyboardControl: autoRepeat off [ 92712.569] (EE) [ 92712.586] (EE) Backtrace: [ 92712.601] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5559b013811c] [ 92712.605] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7ffa5424f41f] [ 92712.608] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7ffa5408c18b] [ 92712.611] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7ffa5406b859] [ 92712.612] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 92712.612] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7ffa5406b71a] [ 92712.614] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7ffa5407cf36] [ 92712.615] (EE) 6: /usr/lib/xorg/Xorg (DRIMoveBuffersHelper+0xc15) [0x5559b0103095] [ 92712.615] (EE) 7: /usr/lib/xorg/Xorg (DRI2Authenticate+0xa2) [0x5559b01046e2] [ 92712.616] (EE) 8: /usr/lib/xorg/Xorg (DRI2GetParam+0x944) [0x5559b0105aa4] [ 92712.616] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5559affd6f34] [ 92712.617] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5559affdafc4] [ 92712.617] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7ffa5406d0b3] [ 92712.618] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2e) [0x5559affc4a2e] [ 92712.621] (EE) [ 92712.621] (EE) Fatal server error: [ 92712.621] (EE) Caught signal 6 (Aborted). Server aborting [ 92712.621] (EE) [ 92712.623] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 92712.623] (EE) Please also check the log file at ".xorgxrdp.16.log" for additional information. [ 92712.623] (EE) [ 92712.627] rdpmouseControl: what 4 [ 92712.627] rdpkeybControl: what 4 [ 92712.629] rdpLeaveVT: [ 92712.634] (EE) Server terminated with error (1). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.8-2ubuntu2.4 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Nov 18 20:07:37 2020 DistUpgraded: 2020-11-10 20:20:36,496 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company ProLiant MicroServer N36L [103c:1609] MachineType: HP ProLiant MicroServer ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=62bd3629-e229-4962-b11f-695a62533e9d ro quiet splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to focal on 2020-11-10 (7 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 07/29/2011 dmi.bios.vendor: HP dmi.bios.version: O41 dmi.chassis.type: 7 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO41:bd07/29/2011:svnHP:pnProLiantMicroServer:pvr:cvnHP:ct7:cvr: dmi.product.name: ProLiant MicroServer dmi.product.sku: 664447-425 dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1904777 Title: Xorg
Re: [Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
That one was a good one. Bluetooth gadget makers seem to be allergic to exactly specify what their gadgets really support. That's on one side extremely understandable, it would be mostly not understandable for humans, the Bluetooth standards involved are arcane, and even relatively experienced computer scientists that are not BT experts can be surprised from time to time, even if they tried to make themselves clever about BT. OTOH, it makes buying Bluetooth headsets slightly a risky business. Then it does not help that most host implementations are kind of not talkative about the connection that they negotiated with the head set. (I mean figuring out which codecs your headset supports involves capturing the traffic and analyzing that, that's state of the art in 2020 on Windows. Now that's user friendliness taken to the extreme, wouldn't you say? Now on Linux, bluez includes an utility that can tell you more about your headset. For whatever reason, Ubung don't include avinfo in their packages, I mean why burden users with details about their headsets?) So my process is sadly as follows: - Look at your headsets (choose BT 4.1/4.2 devices that usually makes sense), read reviews - Order it online - Test if I'm happy with it (on linux, avinfo can tell you about codecs supported, but connecting it to an Android device, doing an Internet based video call, and asking the other side how if you sounded "okay" is usally okay. Bad BT is usually identified as "you sounded really bad, like from the last century"). - If the headset is not okay, send it back. Sadly, the reality of not complete spec sheets on devices makes it basically impossible to know what you are buying beforehand, in general. Andreas Am Mi., 18. Nov. 2020 um 19:11 Uhr schrieb Davide Pessina < 1838...@bugs.launchpad.net>: > @65 - thank for explanation > > Could someone post a list of headsets with mSBC support? > > Price below 100€ if possible > > Specification are hard to find, and headset market is crowded... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838151 > > Title: > Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing > wide band speech support (Bluetooth A2DP codecs). > > To manage notifications about this bug go to: > https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
@65 - thank for explanation Could someone post a list of headsets with mSBC support? Price below 100€ if possible Specification are hard to find, and headset market is crowded... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: In Progress Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 1904769] [NEW] Installed chromium-browser does not work
Public bug reported: Since I need Chrome, I installed chromium-browser and snapd in aptitude. But Chrome didn't appear in the menu, and launching it from the console yields cassiopeia ~ > chromium-browser Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium cassiopeia ~ > snap install chromium error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory I would have thought that chromium-browser does install the chromium snap. So what does it mean, and how do I fix it? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => chromium-browser (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1904769 Title: Installed chromium-browser does not work Status in chromium-browser package in Ubuntu: New Bug description: Since I need Chrome, I installed chromium-browser and snapd in aptitude. But Chrome didn't appear in the menu, and launching it from the console yields cassiopeia ~ > chromium-browser Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium cassiopeia ~ > snap install chromium error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory I would have thought that chromium-browser does install the chromium snap. So what does it mean, and how do I fix it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1904769/+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 1904769] [NEW] Installed chromium-browser does not work
You have been subscribed to a public bug: Since I need Chrome, I installed chromium-browser and snapd in aptitude. But Chrome didn't appear in the menu, and launching it from the console yields cassiopeia ~ > chromium-browser Command '/usr/bin/chromium-browser' requires the chromium snap to be installed. Please install it with: snap install chromium cassiopeia ~ > snap install chromium error: cannot communicate with server: Post http://localhost/v2/snaps/chromium: dial unix /run/snapd.socket: connect: no such file or directory I would have thought that chromium-browser does install the chromium snap. So what does it mean, and how do I fix it? ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- Installed chromium-browser does not work https://bugs.launchpad.net/bugs/1904769 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904765] [NEW] Resolution not set or inappropriate
Public bug reported: The resolution is stuck at 1024x768. My screen can display 1440x900. I added the needed resolution to the settings. Even then it is not changing to the new. It is reverting back again and again to 1024x768. This is the second time I am reporting this issue to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2020-10-21 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ddc3d754-e174-4bc9-8cb7-7d4c277bb4e9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution 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/1904765 Title: Resolution not set or inappropriate Status in xorg package in Ubuntu: New Bug description: The resolution is stuck at 1024x768. My screen can display 1440x900. I added the needed resolution to the settings. Even then it is not changing to the new. It is reverting back again and again to 1024x768. This is the second time I am reporting this issue to you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 22:43:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] (rev 10) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics Controller [8086:29c2] InstallationDate: Installed on 2020-10-21 (28 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: OEM OEM ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=UUID=ddc3d754-e174-4bc9-8cb7-7d4c277bb4e9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.chassis.type: 3 dmi.chassis.vendor: OEM dmi.chassis.version: OEM dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/24/2018:svnOEM:pnOEM:pvrOEM:rvn:rn:rvr:cvnOEM:ct3:cvrOEM: dmi.product.name: OEM dmi.product.version: OEM dmi.sys.vendor: OEM version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
For a substantial amount of users Wayland is important as it has better performance and battery for integrated graphics. Having this bug unfixed and breaking graphical snaps including chromium (which does not have an apt package alternative) forces users to revert to X11/Xorg. What is the mechanism to increase the importance of this bug and expedite the release of the fix which has been available (unreleased) for almost a month. This was a known issue on release day of Groovy. How can I help? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.
All HP G1 Series won't have front combo jack! http://h10032.www1.hp.com/ctg/Manual/c03803181 http://h10032.www1.hp.com/ctg/Manual/c04570601 ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid -- 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/1597708 Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound. Status in alsa-driver package in Ubuntu: Invalid Bug description: The duplex mic/headphone port does not produce any sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 30 11:50:45 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio Symptom_Jack: Black Mic, Front Symptom_Type: No sound at all Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L04 v02.22 dmi.board.asset.tag: 1019155 dmi.board.name: 1825 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 1019155 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP EliteDesk 800 G1 DM dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1597708] Re: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound.
Check HP hardware manual says "When a device is plugged into the Microphone/Headphone Connector, a dialog box will pop up asking if you want to use the connector for a microphone Line-In device or a headphone. You can reconfigure the connector at any time by double-clicking the Audio Manager icon in the Windows taskbar." So, i think this jack is not combinated. -- 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/1597708 Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] Duplex mac/headphone port does not produce sound. Status in alsa-driver package in Ubuntu: Confirmed Bug description: The duplex mic/headphone port does not produce any sound. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 30 11:50:45 2016 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tuomov 6588 F pulseaudio /dev/snd/pcmC1D0p: tuomov 6588 F...m pulseaudio /dev/snd/controlC1: tuomov 6588 F pulseaudio Symptom_Jack: Black Mic, Front Symptom_Type: No sound at all Title: [HP EliteDesk 800 G1 DM, Realtek ALC221, Black Mic, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L04 v02.22 dmi.board.asset.tag: 1019155 dmi.board.name: 1825 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 1019155 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL04v02.22:bd07/16/2015:svnHewlett-Packard:pnHPEliteDesk800G1DM:pvr:rvnHewlett-Packard:rn1825:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.name: HP EliteDesk 800 G1 DM dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-06-28T14:28:35.250807 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1597708/+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 1904622] Re: boto3+s3 bucket fails
Have you tried reading your files with s3cmd or another tool? If that works, check permission keys etc.. If that does not work, I'd like a log file, please. This is going big and I only need a portion. Please run with -v9, redirect to a log file, then run: $ head -n 200 < log > log.head $ tail -n 200 < log > log.tail Attach, do NOT copy/paste, log.head and log.tail to this bug report. See green button below. ** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1904622 Title: boto3+s3 bucket fails Status in Duplicity: Incomplete Status in duplicity package in Ubuntu: New Bug description: I have a duplicity job that runs on multiple hosts, and am now having failures on my 20.04 hosts. The syntax for the job (as I am currently testing to debug) is: duplicity --dry-run list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Using the duplicity packages from focal/main duplicity=0.8.11.1612-1 And I installed the boto packages from focal/universe python3-boto3=1.9.253-1 python3-botocore=1.14.14+repack-1 This runs into the error: Using temporary directory $tmpDir/duplicity-iyhq3se4-tempdir Traceback (innermost last): File "/usr/bin/duplicity", line 106, in with_tempdir(main) File "/usr/bin/duplicity", line 92, in with_tempdir fn() File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1525, in main action = commandline.ProcessCommandLine(sys.argv[1:]) File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1175, in ProcessCommandLine globals.backend = backend.get_backend(args[0]) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in get_backend obj = get_backend_object(url_string) File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in get_backend_object return factory(pu) File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 85, in __init__ self.reset_connection() File "/usr/lib/python3/dist-packages/duplicity/backends/s3_boto3_backend.py", line 96, in reset_connection self.s3.meta.client.head_bucket(Bucket=self.bucket_name) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 357, in _api_call return self._make_api_call(operation_name, kwargs) File "/home/ubuntu/.local/lib/python3.8/site-packages/botocore/client.py", line 676, in _make_api_call raise error_class(parsed_response, operation_name) botocore.exceptions.ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I then tried the duplicity snap from the snap store, both the stable and edge builds, with the same issue: Main action: list-current duplicity 0.8.17 Args: /snap/duplicity/138/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden Main action: list-current duplicity 0.8.18.dev11 Args: /snap/duplicity/141/bin/duplicity --dry-run --ignore-errors list-current-files --name $name --s3-use-ia --archive-dir $archiveDir --tempdir $tmpDir --s3-multipart-chunk-size 256 --s3-use-multiprocessing --volsize 1024 --verbosity 8 boto3+s3://s3.amazonaws.com/bucket.name Linux duplicity 5.4.0-53-generic #59-Ubuntu SMP Wed Oct 21 09:38:44 UTC 2020 x86_64 x86_64 /snap/duplicity/141/usr/bin/python3 3.6.9 (default, Oct 8 2020, 12:12:24) [GCC 8.4.0] Attempt 1 failed. ClientError: An error occurred (403) when calling the HeadBucket operation: Forbidden I also tried to update the boto3/botocore packages by way of pip3: pip3 freeze | grep boto boto3==1.16.19 botocore==1.19.19 And lastly as a last ditch, I tried to pull the packages from the groovy/universe repo, bringing them to: python3-boto3 1.13.14-1
[Desktop-packages] [Bug 1904717] Re: Settings for external keyboard and mouse are not persisted
** Tags added: focal ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1904717 Title: Settings for external keyboard and mouse are not persisted Status in gnome-shell package in Ubuntu: New Bug description: The equipment I'm using is: - Laptop: Dell XPS 13 9380 - Mouse: Anker AK-UBA 2.4G Wireless Vertical Ergonomic Optical Mouse - Keyboard: Microsoft Sculpt Ergonomic Keyboard - Ubuntu version: 20.04.1 I often use an external mouse and keyboard. I have the mouse set to natural scrolling and the speed set to full. For the keyboard I remap Caps Lock to Esc (using Tweaks 3.34.0). What happens: When I connect the keyboard and mouse to the exact same USB ports as before I expect the above settings to persist. What should happen: The mouse and keyboard settings should persist. If you go to the mouse and keyboard settings, it appears as though they have persisted but in order for those settings to work they need to be toggled off and on again. Either the settings should actually persist or the mouse and keyboard settings should show the real applied settings, i.e. toggled off. This bug was not present prior to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904717/+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 1904717] [NEW] Settings for external keyboard and mouse are not persisted
You have been subscribed to a public bug: The equipment I'm using is: - Laptop: Dell XPS 13 9380 - Mouse: Anker AK-UBA 2.4G Wireless Vertical Ergonomic Optical Mouse - Keyboard: Microsoft Sculpt Ergonomic Keyboard - Ubuntu version: 20.04.1 I often use an external mouse and keyboard. I have the mouse set to natural scrolling and the speed set to full. For the keyboard I remap Caps Lock to Esc (using Tweaks 3.34.0). What happens: When I connect the keyboard and mouse to the exact same USB ports as before I expect the above settings to persist. What should happen: The mouse and keyboard settings should persist. If you go to the mouse and keyboard settings, it appears as though they have persisted but in order for those settings to work they need to be toggled off and on again. Either the settings should actually persist or the mouse and keyboard settings should show the real applied settings, i.e. toggled off. This bug was not present prior to Ubuntu 20.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal -- Settings for external keyboard and mouse are not persisted https://bugs.launchpad.net/bugs/1904717 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Mentioned in #15 there is a question about whether using the trackpad increases the amount of interrupts. For me it does do so! Placing my finger on the trackpad does generate mouse events, but it only rapidly generates click events non-stop. It cannot be used to move the pointer but just spams clicks. Would anybody know of a solution? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1904478] Re: [SRU] libreoffice 7.0.3 for groovy
** Also affects: libreoffice (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Groovy) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Groovy) Status: New => In Progress ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Heather Ellsworth (hellsworth) ** Changed in: libreoffice (Ubuntu Groovy) Assignee: (unassigned) => Heather Ellsworth (hellsworth) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1904478 Title: [SRU] libreoffice 7.0.3 for groovy Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Groovy: In Progress Bug description: [Impact] * LibreOffice 7.0.3 is in its third bugfix release of the 7.0 line: https://wiki.documentfoundation.org/ReleasePlan/7.0#7.0.3_release * Version 7.0.2 is currently released in groovy. For a list of fixed bugs compared to 7.0.2 see the list of bugs fixed in the release candidate (that's a total of 92 bugs): https://wiki.documentfoundation.org/Releases/7.0.3/RC1#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_70/1450/ * More information about the upstream QA testing can be found here: * Automated tests - https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests - https://wiki.documentfoundation.org/Development/UITests * Regression tests - https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests - https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/amd64/libr/libreoffice/20201110_032638_c4409@/log.gz * [arm64] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/arm64/libr/libreoffice/20201110_220300_5fc9e@/log.gz * [armhf] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/armhf/libr/libreoffice/20201110_083102_d4dab@/log.gz * [ppc64el] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/ppc64el/libr/libreoffice/20201110_054031_89cb8@/log.gz * [s390x] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-libreoffice-libreoffice-prereleases/groovy/s390x/libr/libreoffice/20201110_020527_366f6@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 92 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1904478/+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 1766775] Re: Notifications do not disappear
Hello, I think I just got this bug. System: 18.04.5 LTS Header's version: linux-headers-5.4.0-54-generic I don't know what I did to reproduce it. The gnome notifications can't be closed, even by clicking on the X or do not disappear. Right before, I was doing a system update with new headers. Then I rebooted, and I got issues regarding pcieport for about 20 minutes. Rebooted multiple times, and then, it went back normal except the notifications... I think you can deactivate the notification from the system's settings, then reboot, it should not annoying you, but it's annoying to not having the notification anymore :/ -- 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/1766775 Title: Notifications do not disappear Status in GNOME Settings Daemon: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: I frequently have notifications that do not disappear after being shown. This is particularly prevalent with power management notifications. Most of the time when I wake my computer from suspend, I see the following notification at the top: "Automatic suspend - Computer will suspend very soon because of inactivity." that never goes away. Presumably, this was shown before my computer went to sleep, and should have disappeared but didn't. I have to either click on the notification, or click on the time to open the notification menu to get it to disappear. Occasionally, the same behaviour occurs with other, random notifications. This is a long-standing issue for me, that I'm just now getting around to reporting. I'm on 17.10, gnome-shell 3.26.2-0ubuntu0.1, and running the gnome-session (not Ubuntu). I don't know if the issue is present on Gnome 3.28, but plan to find out once 18.04 final is released. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1766775/+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 1903230] Re: Mutter release 3.36.7
I use 2 Ubuntu 20.04 machines daily for work, and because of the significant uptime I have seen these memory leaks occur. I would greatly appreciate this update and can test once the SRU is available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Triaged Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+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 1890365] Re: [snap] Web Serial fails to access local device
The above PR was merged and should be part of the snapd 2.48 release.
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/1890365
Title:
[snap] Web Serial fails to access local device
Status in chromium-browser package in Ubuntu:
Fix Committed
Bug description:
A javascript-based web page works fine when accessed through Chrome,
fails to recognize that any devices exist when accessed from Chromium
on the same Unubtu 20.04 platform.
The code includes the following snippet:
const requestOptions = {
filters: [{ usbVendorId: 0x1881 }]
};
port = await navigator.serial.requestPort(requestOptions);
await port.open({ baudrate: 9600 });
writer = port.writable.getWriter();
reader = port.readable.getReader();
Under Chrome 84.0.4147.105 (Official Build) (64-bit), ttyACM0 device
is listed in the pop-up, is selectable, and can communicate. Under
Chromium 84.0.4147.105 (Official Build) snap (64-bit), the pop-up
contains only "No compatible devices found" message.
Experimental Web Features flag is enabled in both browsers.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+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 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "troubleshoot.txt" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435680/+files/troubleshoot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "core dump" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435681/+files/coredump-cups-browsed_20201118 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] Re: cups-browsed crashes when printing test page to remote printer
** Attachment added: "CUPS error_log" https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+attachment/5435679/+files/error_log_20201118_2131 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1904744] [NEW] cups-browsed crashes when printing test page to remote printer
Public bug reported: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cups-browsed log file" https://bugs.launchpad.net/bugs/1904744/+attachment/5435678/+files/cups-browsed_log_20201118_2131 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1904744 Title: cups-browsed crashes when printing test page to remote printer Status in cups-filters package in Ubuntu: New Bug description: 1) lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 2) apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://hk.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) I have several Ubuntu 20.04 LTS desktops configured to print to a CUPS print server with 4 printers. 3 of the printers work OK, the other one I can print a test page locally, I would expect sending a test page from one of the desktops would result in the test page printing. 4) but sending a test page from one of the desktops results in the client CUPS showing: Paused - "No destination host name supplied by cups-browsed for printer "Grassjewel", is cups-browsed running?" When I check on the desktop system: systemctl status cups-browsed cups-browsed.service - Make remote CUPS printers available locally Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Wed 2020-11-18 21:31:48 HKT; 23min ago Process: 22293 ExecStart=/usr/sbin/cups-browsed (code=dumped, signal=SEGV) Main PID: 22293 (code=dumped, signal=SEGV) Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Main process exited, code=dumped, status=11/SEGV Nov 18 21:31:48 Bobcat systemd[1]: cups-browsed.service: Failed with result 'core-dump'. Additional information: The 3 working printers are different manufacturer laser printers, on the network. The problem printer is an Epson dot-matrix printer connected to the CUPS server via a USB/Parallel converter. Log files and core dump attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1904744/+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 1897530] Autopkgtest regression report (xorg-server/2:1.20.8-2ubuntu2.5)
All autopkgtests for the newly accepted xorg-server (2:1.20.8-2ubuntu2.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: camitk/unknown (amd64) software-properties/0.98.9.3 (armhf) aptdaemon/1.1.1+bzr982-0ubuntu32.2 (amd64, armhf) libsoup2.4/2.70.0-1 (arm64) openjdk-8/8u275-b01-0ubuntu1~20.04 (armhf) ubuntu-release-upgrader/1:20.04.28 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#xorg-server [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1904732] Re: Chromium does not start
sudo rm /var/cache/fontconfig/*
rm ~/.cache/fontconfig/*
sudo fc-cache -r -v
rm -rf ~/snap/chromium/common/.cache/fontconfig/
seems to resolve issue
--
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/1904732
Title:
Chromium does not start
Status in chromium-browser package in Ubuntu:
New
Bug description:
user@local:~$ chromium
[7494:7494:1118/132907.917588:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process gpu-process.
Trace/Breakpoint ausgelöst
dmesg:
[ 823.745636] audit: type=1326 audit(1605702600.951:81): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.745848] audit: type=1326 audit(1605702600.951:82): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.745865] audit: type=1326 audit(1605702600.951:83): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.749614] audit: type=1326 audit(1605702600.955:84): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.912551] traps: chrome[7653] trap int3 ip:55d1d6309f02 sp:7ffc8963b160
error:0 in chrome[55d1d2d74000+76ab000]
user@local:~$ chromium --disable-gpu
Trace/Breakpoint ausgelöst
user@local:~$ chromium --disable-gpu --disable-software-rasterizer
Trace/Breakpoint ausgelöst
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAVw5cnRciwAg8bAQOANCF46joFqVRMnCYRUFShCACpQIGAswCpwIHAgQABAQEBKDyAoHCwI0AwIDYAB0QhAAAaAjqAGHE4LUBYLEUAB0QhAAAe/QAxPQ9MEQAKICAgICAg/ABFVjI0NTYKICAgICAgAbQCAyXxThAfBRQEEwMSAhEHFgYVIwkHB4MBAABmAwwAEACA4gB7AR2AGHEcFiBYLCUAB0QhAACeAR2A0HIcFiAQLCWAB0QhAACejArQiiDgLRAQPpYAB0QhAAAYjArQkCBAMSAMQFUAB0QhAAAYDg==
modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1920x1080i 1600x1200 1680x1050 1600x900
1280x1024 1280x800 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576
720x576 720x576 720x576i 720x576i 720x480 720x480 720x480 720x480 720x480
720x480i 720x480i 720x480i 720x480i 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAVwzcYAQEBASUTAQOAJh546sXFo1dKnCMSUFShCACBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/wA4MDc2ODA5OQogICAg/QA7PR9ACwAKICAgICAg/ABTMTkwMQogICAgICAgAGU=
modes: 1280x1024 1024x768 800x600 640x480 720x400
DRM.card0-HDMI-A-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
Date: Wed Nov 18 13:23:21 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 1,8T 1,2T 545G 69% /home
tmpfs tmpfs 16G 81M 16G 1% /dev/shm
/dev/sdb1 ext4 1,8T 1,2T 545G 69% /home
InstallationDate: Installed on 2016-04-30 (1663 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. B150-HD3P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash
snd_hda_intel.power_save=0 vt.handoff=7
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 86.0.4240.198
(d8a506935fc2273cfbac5e5b629d74917d9119c7-refs/branch-heads/4240@{#1431})
Snap.ChromiumVersion: Chromium 86.0.4240.198 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-17 (184 days ago)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F24e
dmi.board.asset.tag: Default string
dmi.board.name: B150-HD3P-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
[Desktop-packages] [Bug 1904732] [NEW] Chromium does not start
Public bug reported:
user@local:~$ chromium
[7494:7494:1118/132907.917588:ERROR:sandbox_linux.cc(374)] InitializeSandbox()
called with multiple threads in process gpu-process.
Trace/Breakpoint ausgelöst
dmesg:
[ 823.745636] audit: type=1326 audit(1605702600.951:81): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.745848] audit: type=1326 audit(1605702600.951:82): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.745865] audit: type=1326 audit(1605702600.951:83): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.749614] audit: type=1326 audit(1605702600.955:84): auid=1000 uid=1000
gid=1000 ses=2 pid=7786 comm="chrome"
exe="/snap/chromium/1399/usr/lib/chromium-browser/chrome" sig=0 arch=c03e
syscall=203 compat=0 ip=0x7fdbffb7ab9f code=0x5
[ 823.912551] traps: chrome[7653] trap int3 ip:55d1d6309f02 sp:7ffc8963b160
error:0 in chrome[55d1d2d74000+76ab000]
user@local:~$ chromium --disable-gpu
Trace/Breakpoint ausgelöst
user@local:~$ chromium --disable-gpu --disable-software-rasterizer
Trace/Breakpoint ausgelöst
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAVw5cnRciwAg8bAQOANCF46joFqVRMnCYRUFShCACpQIGAswCpwIHAgQABAQEBKDyAoHCwI0AwIDYAB0QhAAAaAjqAGHE4LUBYLEUAB0QhAAAe/QAxPQ9MEQAKICAgICAg/ABFVjI0NTYKICAgICAgAbQCAyXxThAfBRQEEwMSAhEHFgYVIwkHB4MBAABmAwwAEACA4gB7AR2AGHEcFiBYLCUAB0QhAACeAR2A0HIcFiAQLCWAB0QhAACejArQiiDgLRAQPpYAB0QhAAAYjArQkCBAMSAMQFUAB0QhAAAYDg==
modes: 1920x1200 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i
1920x1080i 1920x1080 1920x1080i 1920x1080i 1600x1200 1680x1050 1600x900
1280x1024 1280x800 1280x720 1280x720 1280x720 1280x720 1024x768 800x600 720x576
720x576 720x576 720x576i 720x576i 720x480 720x480 720x480 720x480 720x480
720x480i 720x480i 720x480i 720x480i 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAVwzcYAQEBASUTAQOAJh546sXFo1dKnCMSUFShCACBgAEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/wA4MDc2ODA5OQogICAg/QA7PR9ACwAKICAgICAg/ABTMTkwMQogICAgICAgAGU=
modes: 1280x1024 1024x768 800x600 640x480 720x400
DRM.card0-HDMI-A-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
Date: Wed Nov 18 13:23:21 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 1,8T 1,2T 545G 69% /home
tmpfs tmpfs 16G 81M 16G 1% /dev/shm
/dev/sdb1 ext4 1,8T 1,2T 545G 69% /home
InstallationDate: Installed on 2016-04-30 (1663 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. B150-HD3P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash
snd_hda_intel.power_save=0 vt.handoff=7
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 86.0.4240.198
(d8a506935fc2273cfbac5e5b629d74917d9119c7-refs/branch-heads/4240@{#1431})
Snap.ChromiumVersion: Chromium 86.0.4240.198 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to focal on 2020-05-17 (184 days ago)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F24e
dmi.board.asset.tag: Default string
dmi.board.name: B150-HD3P-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrF24e:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnB150-HD3P:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B150-HD3P
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start
[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive
... I have to add: exfat-fuse and exfat-utils are in the "newest version" 1.3.0-1 and the bug still exists! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1872504] Re: date modified is wrong for files on an exfat formatted drive
For it hasn't been corrected in the regular updates, I also confirm that it's still present on ubuntu 20.04, while using an external 4 TB hard drive. I'd like to emphasize the importance of this bug, for it may lead to complications and erroneous deletions if I used the drive for synchronizing folders between different systems. (older files have a date in the future so newer versions are deleted and "updated" !) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1872504 Title: date modified is wrong for files on an exfat formatted drive Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: When using exfat formatted drives (e.g. my camera card) with focal fossa any access causes the date modified to be set, even when it would not normally be set, and it is set a month into the future. Installing exfat-fuse and exfat-utils results in the correct behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Apr 13 17:27:30 2020 InstallationDate: Installed on 2020-04-12 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1900348] Re: Canon TS705 printer stopped working
This is not a problem of CUPS, Turboprint also uses CUPS. This is a problem of the printer driver. For me it looks like a problem of Canon's proprietary driver which you have used before you switched to Turboprint. With an update of your Ubuntu system some library or other file needed by Canon's driver got removed. Before paying for Turboprint you can try to create a new print queue for you printer, using another driver. Remove Canon's driver before trying this to not get your new print queue set up with Canon's driver again. ** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1900348 Title: Canon TS705 printer stopped working Status in cups package in Ubuntu: Invalid Bug description: My Canon TS705 printer stopped working in Ubuntu. Last time I used it was over a week ago so it could be something with the updates installed in the last two weeks. The printer queue says "filter failed". I've attached the cups log of the last print job. I already tried (besides rebooting) removing / installing the printer and reinstalling the canon driver package. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-51.56-generic 5.4.65 Uname: Linux 5.4.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Oct 18 20:42:50 2020 InstallationDate: Installed on 2019-09-20 (394 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190919) Lpstat: Gerät für CanonTS705: cnijbe2://canon/?port=usb=10746E MachineType: Dell Inc. Latitude 5591 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/CanonTS705.ppd'] failed with exit code 2: grep: /etc/cups/ppd/CanonTS705.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-51-generic root=UUID=c0cdf9a7-59c9-4ce4-8dfa-06ad760e34a5 ro quiet splash usbcore.autosuspend=-1 vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0CGP1G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd05/23/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0CGP1G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1900348/+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 1904470] Re: 100Hz monitor fails to wake after lock
Hi Daniel, You were correct! It was in fact dash to panel that was causing the issue. Disabled all extensions and log out/in, lock the machine -> wakes up without issue. Enable dash to panel, relog, lock -> cant wake up. Thanks for the assist and sorry for wasting your time. You can close this 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/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 897222]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/897222 Title: [Upstream] Picture moves to left importing Word .doc Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget -c https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611229/+files/Test%20case.doc -O testcase.doc && lowriter -nologo testcase.doc is the "X" picture in the top right on the document remains in the same place importing from Word (Word screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611268/+files/Test%20case.jpg ). 4) What happens is the X moves to the left (LO screenshot https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/897222/+attachment/2611239/+files/Libreoffice.png ). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: libreoffice-writer 1:3.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Mon Nov 28 14:24:02 2011 ProcEnviron: LANGUAGE=pl_PL:pl:en_GB:en PATH=(custom, user) LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to oneiric on 2011-10-18 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/897222/+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 1904470] Re: 100Hz monitor fails to wake after lock
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #1536 https://gitlab.gnome.org/GNOME/mutter/-/issues/1536 -- 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/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] Re: 100Hz monitor fails to wake after lock
Thanks. Please also run: lspci -kv > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. With the information provided so far I have two ideas: 1. Some of your extensions may be the problem. Since we find so many bugs are caused by extensions, this is one of the first thing to check. Please uninstall or disable via the Extensions app all of these: 'dash-to-pa...@jderose9.github.com', 'un...@hardpixel.eu', 'user-theme @gnome-shell-extensions.gcampax.github.com', 'openweather- extens...@jenslody.de', 'gnome-shell-screens...@ttll.de', 'extensi...@abteil.org', 'gTile@vibou', 'panel- o...@berend.de.schouwer.gmail.com' then log out and in again. 2. I am reminded of this new bug, so you should keep an eye on it: https://gitlab.gnome.org/GNOME/mutter/-/issues/1536 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1536 https://gitlab.gnome.org/GNOME/mutter/-/issues/1536 -- 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/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904709] [NEW] Nautilus crash on filtering files over samba mount points
Public bug reported: When I open Nautilus and navigate over a samba mount point and do this, nautilus crashes: 1. Go to a samba mount point 2. Start typing something to filter results 3. Drag mouse to select all the text you have typed 4. Start typing again to change filter and nautillus crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 09:47:35 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' b'org.gnome.nautilus.window-state' b'initial-size' b'(1133, 727)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-10-29 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1904709 Title: Nautilus crash on filtering files over samba mount points Status in nautilus package in Ubuntu: New Bug description: When I open Nautilus and navigate over a samba mount point and do this, nautilus crashes: 1. Go to a samba mount point 2. Start typing something to filter results 3. Drag mouse to select all the text you have typed 4. Start typing again to change filter and nautillus crash ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 18 09:47:35 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'206' b'org.gnome.nautilus.window-state' b'initial-size' b'(1133, 727)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-10-29 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904709/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
Daniel, the problem is this is not reproducible problem. It just appears out of the blue when using remmina for few days. I will try to collect more info next time freeze appears. -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
Thanks. Unfortunately that didn't collect the information I had hoped. Please: 1. Reboot fresh and then reproduce the freeze again ASAP. 2. Reboot again and then run: journalctl -b-1 > freshprevboot.txt lspci -kv > lspci.txt and attach the resulting text files here. 3. Please also try uninstalling or disabling these extensions via the Extensions app: 'hidetop...@mathieu.bidon.ca' 'user-theme-gnome-extension' then log out and in again, just in case either of those are the problem. P.S. Your log shows you are experiencing performance bug 1849142 so you might like to also install the proposed fix for that. -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1883160] Re: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem
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/1883160 Title: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: My headphones stopped playing sound a few days ago, except for the occasional 'pop' when I select them as output. The laptop speakers still work when they're select as output. I've tried unplugging other devices, rebooting, plugging my headphone jack out and back in. When I plug my headphone into a different laptop running 18.04 they work fine. What's odd to me is that Ubuntu seems eager to select my Yeti Microphone as the output device. The bars under 'Output' and 'Input' both light up when I play sound or snap my fingers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathijs2185 F pulseaudio /dev/snd/pcmC0D0c: mathijs2185 F...m pulseaudio /dev/snd/pcmC0D0p: mathijs2185 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 11 10:46:20 2020 InstallationDate: Installed on 2020-04-27 (45 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [XPS 15 7590, Realtek ALC3266, Black Headphone Out, Left] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 0T8KGX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd05/11/2020:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0T8KGX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1883160/+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 1904470] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435500/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435498/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435501/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435502/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435499/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1904470] Re: 100Hz monitor fails to wake after lock
apport information ** Tags added: apport-collected ** Description changed: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.12 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-14 (3 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.4.0-53-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1904470/+attachment/5435497/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1904470 Title: 100Hz monitor fails to wake after lock Status in gnome-shell package in Ubuntu: Incomplete Bug description: When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again. This issue does not happen on 60Hz. This issue is present on both 20.04.1 LTS and 20.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-14 (3 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1904470/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
** No longer affects: build-essential (Ubuntu) ** No longer affects: build-essential (Ubuntu Focal) ** No longer affects: glib2.0 (Ubuntu) ** No longer affects: iputils (Ubuntu) ** No longer affects: kbd (Ubuntu) ** No longer affects: linux-meta (Ubuntu) ** No longer affects: linux-meta (Ubuntu Bionic) ** No longer affects: linux-meta (Ubuntu Focal) ** No longer affects: ntpsec (Ubuntu) ** No longer affects: qemu (Ubuntu) ** No longer affects: qemu (Ubuntu Focal) ** No longer affects: util-linux (Ubuntu) ** No longer affects: util-linux (Ubuntu Focal) ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Focal: Fix Released Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/) ...F upstream (F 17% S 0% B 0% => P 82%/) .F..F.F.FFF...F. systemd-fsckd (F 32% S 0% B 0% => P 67%/) FFF..FF..F.FF..F root-unittests (F 10% S 0% B 0% => P 90%/) FFF...F. arm64 tests-in-lxd (F 40% S 0% B 2% => P 57%/) F.B...FFF.FF..F..F.FFF.F logind (F 2% S 0% B 2% => P 95%/) ..B...F. upstream (F 22% S 0% B 2% => P 75%/)
[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1754671 *** https://bugs.launchpad.net/bugs/1754671 ** This bug is no longer a duplicate of bug 1688018 DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 ** This bug has been marked a duplicate of bug 1754671 Full-tunnel VPN DNS leakage regression -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
*** This bug is a duplicate of bug 1754671 *** https://bugs.launchpad.net/bugs/1754671 ** This bug has been marked a duplicate of bug 1754671 Full-tunnel VPN DNS leakage regression -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1672491] Re: New NetworkManager breaks VPN DNS.
*** This bug is a duplicate of bug 1754671 *** https://bugs.launchpad.net/bugs/1754671 ** This bug is no longer a duplicate of bug 1688018 DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 ** This bug has been marked a duplicate of bug 1754671 Full-tunnel VPN DNS leakage regression -- 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/1672491 Title: New NetworkManager breaks VPN DNS. Status in network-manager package in Ubuntu: Confirmed Bug description: Alright, this is going to be a frustrating bug for everyone involved I expect, but here goes. On Ubuntu 16.04, using a non-released VPN client (making this _much_ harder for anyone to reproduce), upgrading the network-manager packages from 1.2.2-0ubuntu0.16.04.3 to 1.2.6-0ubuntu0.16.04.1 quite handily broke DNS over the VPN. And it broke it really oddly. dnsmasq binds to socket 12 for the new interface, just fine. strace shows that it does the sendto for the DNS request, and that the poll calls are working, just fine. tcpdump shows the response messages, they are coming back from the correct host and port, going to my IP and the port that dnsmasq is sending from. There are no iptables rules involved, nothing is set to deny. dnsmasq is never getting the response packet. The request thus times out. Doing a host or dig directly to the DNS server works just fine. And this is completely reproducible, and goes away the moment I downgrade back to 1.2.2-0ubuntu0.16.04.3. Was there some change to how network-manager handles VPN interfaces/tap0 in the new version? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1672491/+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 1796648] Re: network-manager-openvpn leaks DNS information on Ubuntu 18.04
*** This bug is a duplicate of bug 1754671 *** https://bugs.launchpad.net/bugs/1754671 ** Bug watch removed: GNOME Bug Tracker #746422 https://gitlab.gnome.org/746422 -- 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/1796648 Title: network-manager-openvpn leaks DNS information on Ubuntu 18.04 Status in network-manager package in Ubuntu: Confirmed Bug description: By default when adding a VPN configuration on Ubuntu 18.04 the DNS configuration supplied by DHCP is not used, resulting in DNS leakage. How to reproduce: * Add VPN configuration, for example, import a ovpn file * activate * Check for DNS leakage at for example https://www.dnsleaktest.com/ This has been reported at various locations: https://github.com/systemd/systemd/issues/7182 https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1690860 https://github.com/eduvpn/python-eduvpn-client/issues/160 The issue has been solved since network-manage-open version 1.12.0: https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/issues/10 This version or a more recent version is part of Ubuntu 18.10 which doesn't have this issue. A workaround is to run: $ systemd-resolve -i tun2 --set-domain=~. where tun2 is your VPN interface. We think this is a security issue and at least a backport of network- manage-open > 1.12.0 should be uploaded to the archive. greetings, - Gijs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 11:19:00 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-06-06 (123 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.178.1 dev enp6s0 proto dhcp metric 100 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown 192.168.178.0/24 dev enp6s0 proto kernel scope link src 192.168.178.61 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 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/1796648/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
I executed: apport-collect 1903986 Step 1: Directory /var/crash is empty. Step 2: I get https://errors.ubuntu.com/user/3b81bfacd6a0c6d0f5d20395f7f51923611af976e65590519b1a3d70e9a0f5ef1454621e36d78b8c546167c5a8c9e9a3b2e7828938bb23cd0f8b737a46a7c591 but this may be some other problem, because yesterday I have had no issue with gnome-shell crash. Step 3: I don't really know what to do here... This should probably be done right after crash appears, isn't it? -- 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/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435474/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435473/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435470/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435471/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435472/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903986/+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 1903986] Re: Ubuntu 20.04 freezes with remmina in full-screen
apport information ** Tags added: apport-collected ** Description changed: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.12 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-23 (392 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: focal + Uname: Linux 5.4.0-54-generic x86_64 + UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark + _MarkForUpload: True + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1903986/+attachment/5435469/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903986 Title: Ubuntu 20.04 freezes with remmina in full-screen Status in gnome-shell package in Ubuntu: Incomplete Bug description: On Ubuntu 20.04 using Remmina accessing remote Windows session to my work and everything was working fine for 5 hours and then suddenly Reminna freezes. Mouse pointer still working fine, but Remmina not responding and also keyboard not responding (maybe because all of the keys are controller by Remmina). This problem is now third time the problem appeared: - bug 1902051 - bug 1903710 with no response. :( Work-around: hard press power button to power off laptop and power on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: remmina 1.4.2+dfsg-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 12:38:25 2020 InstallationDate: Installed on 2019-10-23 (386 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: remmina UpgradeStatus: Upgraded to focal on 2020-08-14 (89 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-04-29T17:08:03.553351 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-23 (392 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-08-14 (95 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True
[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Seems to be Wayland related, from other sources. (I did not test it in X, though.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
there are various forum and askubuntu threads about this issue already as well: https://forum.snapcraft.io/t/ui-glitch-after-recent-update/15133 https://forum.snapcraft.io/t/some-snaps-app-have-weird-looking-window- control-and-fonts/17859 https://askubuntu.com/q/1206868/66509 https://discourse.ubuntu.com/t/odd-close-button-with-snaps/19392 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1904545] Re: ZFS rollback does not do anything
*** This bug is a duplicate of bug 1894329 *** https://bugs.launchpad.net/bugs/1894329 ** This bug has been marked a duplicate of bug 1894329 ZFS revert from grub menu not working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1904545 Title: ZFS rollback does not do anything Status in zsys package in Ubuntu: New Bug description: On Ubuntu 20.04.1 LTS as well as Ubuntu 20.10 rolling back a zfs snapshot does nothing. Tested rolling back autozsys as well as a manual snapshot. The rollback command does not return any error but does not rollback a snapshot. May be related to Bug #1904469 as a secondary symptom of the same issue but then again maybe not. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1904545/+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
