[Desktop-packages] [Bug 1870519] Re: Ubuntu 20.04 Dock - Autohide not working
Still the same, not working for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1870519 Title: Ubuntu 20.04 Dock - Autohide not working Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Hello, Ubuntu 20.04 beta (Apr 2nd 2020) 1. Set in dconf editor under /org/gnome/shell/extensions/dash-to-dock/ autohide:true docker-fixed:false 2. Maximize some desktop window and the dock disappears. Now, move mouse to the dock area but the dock will never appear. (on 18.04 this works properly - using the same dconf properties in both 20.04 and 18.04) It should auto appear when you move the mouse where the dock was hidden. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-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-ubuntu-dock/+bug/1870519/+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 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time
Hello ! Please find journal.txt attached. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+attachment/5390033/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1886162 Title: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Side scrollbar setting feature works from time to time . If you set it on and close the window it saves the setting and side scrollbar works . If you set it on and move to another menu item i.e. "Sound" or "search" it doesn't save the setting and switch it back to off. S.T.R. 1. Open "Settings"; 2. Move to "Mouse and scroll pad" item; 3. Set Side scrollbar to on; 4. Move to "Sound" item; 5. Move to "Mouse and scroll pad" item. A.R. Side scrollbar is on. E.R. Side scrollbar is off. Severity: low Environment: Ubuntu 20.04 LTS 64 bit Russian language Gnome 3.36.2 Check screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+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
Re: [Desktop-packages] [Bug 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time
Hello! Attached journal.txt to my bug report. Regards, Yurii -- С уважением, Панков Юрий 6 июл. 2020 г., 05:25 От 1886...@bugs.launchpad.net: > Please run this command: > > journalctl -b0 > journal.txt > > and attach the resulting text file. > > ** Tags added: focal > > ** Changed in: gnome-control-center (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1886162 > > Title: > Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from > time to time > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > Side scrollbar setting feature works from time to time . If you set it > on and close the window it saves the setting and side scrollbar works > . If you set it on and move to another menu item i.e. "Sound" or > "search" it doesn't save the setting and switch it back to off. > > S.T.R. > 1. Open "Settings"; > 2. Move to "Mouse and scroll pad" item; > 3. Set Side scrollbar to on; > 4. Move to "Sound" item; > 5. Move to "Mouse and scroll pad" item. > > A.R. Side scrollbar is on. > E.R. Side scrollbar is off. > > Severity: low > > Environment: > Ubuntu 20.04 LTS 64 bit Russian language > Gnome 3.36.2 > > Check screenshot attached. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1886162 Title: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Side scrollbar setting feature works from time to time . If you set it on and close the window it saves the setting and side scrollbar works . If you set it on and move to another menu item i.e. "Sound" or "search" it doesn't save the setting and switch it back to off. S.T.R. 1. Open "Settings"; 2. Move to "Mouse and scroll pad" item; 3. Set Side scrollbar to on; 4. Move to "Sound" item; 5. Move to "Mouse and scroll pad" item. A.R. Side scrollbar is on. E.R. Side scrollbar is off. Severity: low Environment: Ubuntu 20.04 LTS 64 bit Russian language Gnome 3.36.2 Check screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+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 1876887] Re: taking screenshots fails with gnome-shell error after upgrade to 20.04
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876887 Title: taking screenshots fails with gnome-shell error after upgrade to 20.04 Status in gnome-shell package in Ubuntu: Expired Bug description: After upgrading from ubuntu desktop 19.10 to 20.04, taking screenshots using the 'PrntScrn' keyboard-button fails with the following gnome- shell error logged in journalctl: Mai 05 11:27:17 work-pc2 gnome-shell[1683]: JS ERROR: Error: Argument 'filename' (type filename) may not be null _resolveRelativeFilename/path<@resource:///org/gnome/shell/ui/screenshot.js:73:26 _resolveRelativeFilename@resource:///org/gnome/shell/ui/screenshot.js:73:11 _createStream@resource:///org/gnome/shell/ui/screenshot.js:102:9 ScreenshotAsync@resource:///org/gnome/shell/ui/screenshot.js:220:35 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34 $ dpkg -l |grep gnome-shell ii gnome-shell3.36.1-5ubuntu1 ii gnome-shell-common 3.36.1-5ubuntu1 ii gnome-shell-extension-appindicator 33-1 ii gnome-shell-extension-desktop-icons20.04.0-1 ii gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 GsettingsChanges: InstallationDate: Installed on 2020-01-17 (108 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876887/+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 1876802] Re: Gnome (on Xorg) crashes when disconnecting external monitor
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876802 Title: Gnome (on Xorg) crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Expired Bug description: Working on a dell xps13 running Ubuntu 20.04, having a second display connected to my laptop. When disconnecting the 2nd display, first the application windows move the built-in laptop display, but after one or two seconds the screen went gray, telling me that an error has occured and that you need to log in again. I went through the journalctl, and noticed lots of messages as below: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Not sure if this is the actual cause though. After some googling I found bug report #1857660 in which it was suggested to uninstall a few gnome extensions. One of the mentioned extensions was indeed installed, but I removed (in the end) all of them, rebooted but still problem occurs. And is reproducable in a very simple way: - Reboot & Login (with 2nd monitor attached) - Open an app (not sure this is really needed to reproduce though) - Disconnect the 2nd display and wait a second. - Boom! Useful to mention that the problem does not occur on Wayland, even with the extensions installed (but with Wayland I can't share my full screen, which I need for Slack :-( ). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-07-30 (644 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876802/+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 1876910] Re: video stutter
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1876910 Title: video stutter Status in mutter package in Ubuntu: Expired Bug description: System works fine util Suspend. After wake up from Suspend video on display stutters. Video (e.g. in browser) freezes approximately once every second, and freeze lasts for about 100 millisecond. If you drag an icon or a window over the desktop, the icon will stutter, but the cursor will not stutter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 5 13:49:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:095d] InstallationDate: Installed on 2020-04-27 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer TravelMate P236-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P236-M dmi.board.vendor: Acer dmi.board.version: V1.17 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd08/10/2015:svnAcer:pnTravelMateP236-M:pvrV1.17:rvnAcer:rnTravelMateP236-M:rvrV1.17:cvnAcer:ct10:cvrV1.17: dmi.product.family: BDW dmi.product.name: TravelMate P236-M dmi.product.sku: TravelMate P236-M_095D_1.17 dmi.product.version: V1.17 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/mutter/+bug/1876910/+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 1876915] Re: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1876915 Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 Status in cups package in Ubuntu: Expired Bug description: Im not sure what caused this problem ProblemType: Package DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Sat May 2 11:27:39 2020 DpkgHistoryLog: Start-Date: 2020-05-02 11:27:19 Commandline: /usr/bin/unattended-upgrade Upgrade: libcups2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcups2:i386 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-server-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-bsd:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-core-drivers:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-daemon:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcupsimage2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-client:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-ipp-utils:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1) ErrorMessage: installed cups-daemon package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-03-30 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: ASUSTeK COMPUTER INC. Q500A Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: cups Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to eoan on 2020-04-02 (32 days ago) dmi.bios.date: 08/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q500A.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q500A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ500A.205:bd08/17/2012:svnASUSTeKCOMPUTERINC.:pnQ500A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ500A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Q dmi.product.name: Q500A dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1876915/+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 1876946] Re: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876946 Title: gnome-shell freezing with "Attempting to run a JS callback during garbage collection." messages Status in gnome-shell package in Ubuntu: Expired Bug description: This happened soon after logging in. The entire desktop (mouse cursor included) would freeze for maybe 30 seconds at a time. The activities screen seemed to trigger it. The dock appeared empty. After a few minutes of this I rebooted and things seem to be alright now. Relevant log messages start on May 5 at 11:10 AM US/Eastern time. Similar messages appear on March 31st. I don't recall whether I experienced similar freezing behavior at that time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 5 11:22:41 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (322 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-21 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876946/+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 1876923] Re: Xorg freeze on shutdown
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1876923 Title: Xorg freeze on shutdown Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: The system was suspended, it recovered perfectly. When I did a shutdown, the system hung with a message about waiting for Xorg. After several minutes, I pressed the power button once and the system responded with another message about sending sigkill to Xorg. Still didn't shutdown and went into the 'waiting for Xorg' again. I held the power button and turned the system off. Not sure if I can reproduce this, or what logs would help with the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 5 07:22:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb] InstallationDate: Installed on 2020-03-12 (53 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) MachineType: LENOVO 81T2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-440/+bug/1876923/+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 1876923] Re: Xorg freeze on shutdown
[Expired for nvidia-graphics-drivers-440 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Incomplete => Expired -- 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/1876923 Title: Xorg freeze on shutdown Status in nvidia-graphics-drivers-440 package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: The system was suspended, it recovered perfectly. When I did a shutdown, the system hung with a message about waiting for Xorg. After several minutes, I pressed the power button once and the system responded with another message about sending sigkill to Xorg. Still didn't shutdown and went into the 'waiting for Xorg' again. I held the power button and turned the system off. Not sure if I can reproduce this, or what logs would help with the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue May 5 07:22:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed nvidia, 440.64, 5.4.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:3ffb] InstallationDate: Installed on 2020-03-12 (53 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) MachineType: LENOVO 81T2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-440/+bug/1876923/+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 1886345] Re: Display gets corrupted and text gets replaced by odd characters
Please run these commands: lspci -k > lspcik.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1886345/+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 1724876] Re: libreoffice soffice.bin using 100% cpu
** Changed in: df-libreoffice Status: Incomplete => Unknown -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1724876/+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 1886331] Re: Xorg freeze
The attached file 'dmesg.0' shows the amdgpu kernel driver crashed on startup. So I assume that file is meant to show a case where the problem happened. ** Tags added: amdgpu ** Summary changed: - Xorg freeze + Cannot boot sometimes - black screen with a mouse pointer. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Cannot boot sometimes - black screen with a mouse pointer. + [amdgpu] Cannot boot sometimes - black screen with a mouse pointer. -- 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/1886331 Title: [amdgpu] Cannot boot sometimes - black screen with a mouse pointer. Status in linux package in Ubuntu: New Bug description: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw1xxx dmi.product.sku: 6QF12EA#AB7 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1886331/+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 1724876]
Dear Gabriel Staples, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1724876/+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 1886330] Re: pulseaudio not working in Virtualbox
The attached info shows PulseAudio was running when you reported the bug: !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes Are you sure the problem is PulseAudio not running (the process should be named 'pulseaudio')? If so then please check for any crash files in /var/crash If you don't find any relevant crash files then please wait until the problem happens again and then run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1886330 Title: pulseaudio not working in Virtualbox Status in pulseaudio package in Ubuntu: Incomplete Bug description: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886330/+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 1886322] Re: Unable to move files in bulk on desktop using rectangle
Can someone please report the issue to the developers? https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues -- 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/1886322 Title: Unable to move files in bulk on desktop using rectangle Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: Hi, This bug started to happen like 1-2 months ago, and as I remember I didn't do any customizations like installing any external plugins and etc, but I have some stuff already like custom icons, shell, theme... but it worked normaly before. What is happening is that when I select more than 1 file on desktop, no matter which file it is (folder, .txt, image.. anything), and when I try to move around desktop from one place to another, it will move only 1 file and not the rest. So, unable to move selected files on desktop (drag and drop using cursor's rectangle). Its simple issue, no need for video or screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:18:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322/+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 1886269] Re: ps/2 mouse not working
I can't see any evidence of a PS/2 mouse being detected in your logs. Only a Bluetooth mouse. If this is a software bug then it would probably be a kernel bug. ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: New Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) dmi.bios.date: 01/08/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG41RQ dmi.board.vendor: Intel Corporation dmi.board.version: AAE54511-203 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jul 3 08:17:23 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+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 1768543] Re: Window previews are not horizontally centered in their context menus
** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/823 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1768543 Title: Window previews are not horizontally centered in their context menus Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Ubuntu 18.04 Gnome Shell with Communitheme, also checked with default theme. Steps to reproduce: 1. Open 2 windows of the same application (Terminal in my case) 2. Left click on the icon in the dock and notice how the previews of app's windows and the close button are positioned 3. Click somewhere to close the previews 4. Right click on the icon in the dock 5. Select "All windows" and notice the slight difference in the positions of previews and close button Screenshots attached To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1768543/+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 1886246] Re: Xorg freeze
That sounds like two different issues so we will make this bug just about the mouse problem. Please open a new bug for the other issue if you like. It seems like there's a hardware/kernel problem with that mouse due to these occasional messages: [ 11273.560] (II) event11 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. [ 12901.284] (II) event6 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. [ 15824.486] (II) event6 - YSPRINGTECH USB OPTICAL MOUSE: SYN_DROPPED event - some input events have been lost. So please try a different USB mouse and/or a different USB port. ** Summary changed: - Xorg freeze + Sometimes on my lock screen, my mouse stops for a moment ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Description changed: - Sometimes on my lock screen, my mouse stops for a moment, and also many - times certain application freezes and then I have to force quit them. - Also, it is not going too fast, it takes much time to boot up. + Sometimes on my lock screen, my mouse stops for a moment Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 10:22:09 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] + Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240 / R3 Series] [1002:9838] (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8240 / R3 Series] [1025:104b] InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Aspire ES1-520 ProcEnviron: - LANGUAGE=en_IN:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + 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-26-generic root=UUID=01e0d428-3558-4f95-a0f0-994b27c807c3 ro quiet splash i8042.nopnp vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Bellemere_BE dmi.board.vendor: Acer dmi.board.version: V1.06 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd08/11/2015:svnAcer:pnAspireES1-520:pvrV1.06:rvnAcer:rnBellemere_BE:rvrV1.06:cvnAcer:ct9:cvrChassisVersion: dmi.product.family: KB dmi.product.name: Aspire ES1-520 dmi.product.sku: Aspire ES1-520_104B_V1.06 dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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 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 -- 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/1886246 Title: Sometimes on my lock screen, my mouse stops for a moment Status in linux package in Ubuntu: Incomplete Bug description: Sometimes on my lock screen, my mouse stops for a moment Please send me the solution I had recently sifted form windows to ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
[Desktop-packages] [Bug 1886268] Re: Window preview isn't centred, it is left aligned and looks wrong
*** This bug is a duplicate of bug 1768543 *** https://bugs.launchpad.net/bugs/1768543 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 1768543, 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 1768543 Window previews are not horizontally centered in their context menus -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1886268 Title: Window preview isn't centred, it is left aligned and looks wrong Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: There is an issue on Ubuntu 20.04 / 20.04.1 where the ubuntu dock extension for gnome is misaligning the preview window - it should be centred based on what I've seen online. This was a fresh install of Ubuntu 20.04 close to or just after release. People are discussing the issue on Stack Exchange here: https://askubuntu.com/q/1183065/10857 with the following answer fixing the issue for most people: https://askubuntu.com/a/1232740/10857. The problem with that fix is that people shouldn't have to do that - it should already be baked in, so I'm making it aware here so someone can apply this fix if possible since you'll know better if this will break other things or not. 1) $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 2) $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 68ubuntu1~20.04.1 Candidate: 68ubuntu1~20.04.1 Version table: *** 68ubuntu1~20.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 67ubuntu20.04.5 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages 3) Expended the window to be centred in the preview. 4) Preview is left-aligned and looks out of place. See screenshot originally posted in Stack Exchange: https://i.stack.imgur.com/dlDhJ.png (I've also uploaded a screenshot from my own system below). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 14:43:28 2020 InstallationDate: Installed on 2020-05-22 (43 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1886268/+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 1886259] Re: Nvidia driver is not in the correct directory
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (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/1886259 Title: Nvidia driver is not in the correct directory Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Ubuntu 20.04 The packages installed by the metapackage nvidia-driver-440 do not put the nvidia x server module in the right place. The server cannot find it. My file /var/log/Xorg.0.log was collected by apport. nvidia-driver-440_440.100-0ubuntu0.20.04.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Jul 4 04:46:32 2020 DistUpgraded: 2020-06-01 17:37:38,642 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0532] InstallationDate: Installed on 2016-12-01 (1310 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6230 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=69311ad3-1ba4-46b2-80b4-5e8986e36f36 ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (32 days ago) dmi.bios.date: 02/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0YW5N5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd02/06/2013:svnDellInc.:pnLatitudeE6230:pvr01:rvnDellInc.:rn0YW5N5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6230 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1886259/+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 1886245] Re: BCM20702A bluetooth freezing after boot
This looks like a hardware problem or a kernel bug so reassigning... ** Summary changed: - bluetooth freezing after boot + BCM20702A bluetooth freezing after boot ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - BCM20702A bluetooth freezing after boot + BCM20702A bluetooth freezing for 4-9 seconds ** Summary changed: - BCM20702A bluetooth freezing for 4-9 seconds + BCM20702A bluetooth mouse freezing for 4-9 seconds -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886245 Title: BCM20702A bluetooth mouse freezing for 4-9 seconds Status in linux package in Ubuntu: Confirmed Bug description: Boot system, the Bluetooth mouse will stop for about 4-9 seconds, then it will work as normal. I am using a plugable USB Bluetooth adapter for Bluetooth connections. I am using blueman to connect. Mouse used is a Kensington Exper Mouse Wireless Trackball Issue does not occur with bluetooth speakers, or headphones. Computer- Dell Precision 5520. Logs show these errors as below bt_uhid_send: Invalid argument (22) Bluetooth: hci0: advertising data len corrected Description: Ubuntu 20.04 LTS Release: 20.04 blueman: Installed: 2.1.2-1 Candidate: 2.1.2-1 Version table: *** 2.1.2-1 500 500 http://au.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 13:24:01 2020 InstallationDate: Installed on 2020-06-03 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 002: ID 0a5c:21e8 Broadcom Corp. BCM20702A0 Bluetooth 4.0 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezfsem@/vmlinuz-5.4.0-40-generic root=ZFS=rpool/ROOT/ubuntu_ezfsem ro quiet splash pcie_aspm=off vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.2 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.2:bd05/22/2020:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 5C:F3:70:7E:32:2F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:193521 acl:13666 sco:0 events:137 errors:0 TX bytes:5858 acl:61 sco:0 commands:82 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886245/+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 1716301] Re: wifi driver: mt7601u not work on 16.04
** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch-data in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110 [ 4757.730870] usbcore: registered new interface driver mt7601u // end $> sudo ifconfig -a // do not list any new interface 2)
[Desktop-packages] [Bug 1886176] Re: gnome-shell crashes on screen-lock, disable and re-enable extensions fixes until session restart
*** This bug is a duplicate of bug 184 *** https://bugs.launchpad.net/bugs/184 This is probably a duplicate of bug 184. A fix for that is now available. To get it please: sudo apt update sudo apt full-upgrade Reboot. ** This bug has been marked a duplicate of bug 184 gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] -- 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/1886176 Title: gnome-shell crashes on screen-lock, disable and re-enable extensions fixes until session restart Status in gnome-shell package in Ubuntu: New Bug description: After logging in I can't screen-lock until I disable then re-enable extensions. I have tried disable extensions one by one and it doesn't matter which extensions are enable, any will break on first attempt to lock after fresh login. systemd sees the SEGV, logs attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 10:31:02 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-06 (178 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-25 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886176/+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 1886204] Re: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card
** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (Ubuntu) ** Tags added: radeon -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1886204 Title: Flickering and sudden resolution changes on 20.04/18.04 and old Radeon HD 6570 card Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: Initially, Ubuntu started with far lower resolution than my monitor. I've tried xrandr --newmode command*, it temporarily helps to get back to my original 1600X900 resolution. But now screen sometimes go back to that lower resolution (and randpomly comes back to normal after some time), and xrandr doesn't help. Plus, my screen keeps flickering, sometimes quite frequently. Combined with low resolution, it has become almost unbearable at this point. Things work alright with windows 10 (dual boot). Further details: 1. Sometimes, but not always, simply going to Display Setting by GUI or typing xrandr in command line fixes it. 2. I sometimes see "drm:radeon_vga_detect [radeon]] ERROR VGA-1: probed a monitor but no|invalid EDID" while shutting down or in /var/log/syslog. Also quite frequently "ERROR:edid_parser.cc(102)] Too short EDID data: manufacturer id" in the log. 3. Using read-edid package, I noticed that while on low res, it can't detect EDID on any bus. However if I keep running this command, at some point it successfully reads & parses EDID. Then, if I go to Display Setting, or after some time automatically- the resolution comes back to normal. 4. Reinstalled ubuntu 20.04, removed that cron job. Didn't change the situation. 5. I've tried Wayland, awesome window manager, lightdm display manager. I'd rather not change the GNOME environment. 6. Tried Ubuntu 18.04.4 (current OS), now its always low resolution. Config: CPU: Ryzen 3700x, MB: Asus Tuf x570 Gaming plus, Monitor: Samsung SyncMaster E2020 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.7.1-050701-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 3 20:53:51 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] [1002:6759] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Turks PRO [Radeon HD 6570/7570/8550] [174b:e193] InstallationDate: Installed on 2020-07-02 (0 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.7.1-050701-generic root=UUID=e26c767f-e791-4209-905a-0e9eaa3bc363 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1405 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1405:bd11/19/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1886204/+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 1885610] Re: enlarged components on lock/login screen
Please open Gnome Tweaks, click on Appearance, and then take a screenshot of the window (Alt+PrtScn) and attach it here. -- 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/1885610 Title: enlarged components on lock/login screen Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Source Package: usr/bin/gnome-shell Ubuntu Release: 20.04 LTS Package Version: 3.36.2-1ubuntu1~20.04.1 Expected: Normal sized components on lock/login screen Happened: Enlarged components on lock/login screen This behavior is unaffected by resolution size from different monitors ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Flat-Remix-Miami-Dark-GNOME:GNOME Date: Mon Jun 29 13:01:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-02 (331 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-06-27 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1885610/+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 1886162] Re: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time
Please run this command: journalctl -b0 > journal.txt and attach the resulting text file. ** Tags added: focal ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1886162 Title: Gnome-Settings-Mouse and scrollpad : side scrollbar setting works from time to time Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Side scrollbar setting feature works from time to time . If you set it on and close the window it saves the setting and side scrollbar works . If you set it on and move to another menu item i.e. "Sound" or "search" it doesn't save the setting and switch it back to off. S.T.R. 1. Open "Settings"; 2. Move to "Mouse and scroll pad" item; 3. Set Side scrollbar to on; 4. Move to "Sound" item; 5. Move to "Mouse and scroll pad" item. A.R. Side scrollbar is on. E.R. Side scrollbar is off. Severity: low Environment: Ubuntu 20.04 LTS 64 bit Russian language Gnome 3.36.2 Check screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886162/+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 1880739] Re: Night Light not working
** Summary changed: - Night Light not working in mutter 3.36.2-1ubuntu1~20.04.1 + Night Light not working -- 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/1880739 Title: Night Light not working Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Till yesterday, it was working fine. But today after reboot, night light failed to start. I tried turning Night Light off/on but nothing seemed to work. Unfortunately, I don't know what the previous version of mutter was installed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-04 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880739/+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 1884049] Re: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable
*** This bug is a duplicate of bug 1880405 *** https://bugs.launchpad.net/bugs/1880405 To get all of it: journalctl -b0 > journal.txt Or to just watch for the latest messages: journalctl -f -- 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/1884049 Title: gnome-shell is taking more and more CPU over time, UI becomes slowly unusable Status in gnome-shell package in Ubuntu: New Bug description: I'm a relatively heavy desktop user, having multiple browsers running at any given time, lots of terminal windows, etc.However, my browsers don't use a lot of CPU as most of the tabs are suspended at any given moment. On a regular basis, over time, my desktop becomes less and less usable. It starts with becoming noticeably slower, laggy, and eventually absolutely requiring a reboot since it becomes totally unusable. At the same time my my system load is low, and remains low, while gnome-shell appears only to take more and more CPU. I often see it using 30, 50, 90, and sometimes 100% CPU, while the rest is idle. It reaches the point where terminals don't easily The only "fix" is rebooting, or restarting X. I must admit that I've been seeing this on my laptop for years now, and there is no improvement in sight even though I upgrade Ubuntu to the next version every time an update is out. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.2-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 11:53:00 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-28 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1884049/+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 1787822] Re: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it
It appears the fix is in Ubuntu 20.04 but not 18.04. So I will mark this to request a fix in 18.04. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released ** Tags added: rls-bb-incoming -- 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/1787822 Title: gnome-shell[2503]: Object Meta.Background (0x561c9af53600), has been already deallocated - impossible to access to it Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/501 --- lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.28.2-0ubuntu0.18.04.1 Candidate: 3.28.2-0ubuntu0.18.04.1 Version table: *** 3.28.2-0ubuntu0.18.04.1 500 Since upgrading from 16.04.5LTS to 18.04.1LTS last Thursday my syslog has been filling with the below: Aug 19 11:34:11 localhost gnome-shell[2503]: Object Meta.Background (0x7febd401a470), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: == Stack trace for context 0x561c9a54e330 == Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #0 0x561c9a9edbd8 i resource:///org/gnome/shell/ui/background.js:718 (0x7febd000f450 @ 22) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #1 0x561c9a9edb50 i resource:///org/gnome/shell/ui/tweener.js:113 (0x7febd02c7e68 @ 37) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #2 0x7fff0e3e36e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:208 (0x7febd02d3b38 @ 54) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #3 0x7fff0e3e3830 b resource:///org/gnome/gjs/modules/tweener/tweener.js:337 (0x7febd02d3bc0 @ 1626) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #4 0x7fff0e3e38e0 b resource:///org/gnome/gjs/modules/tweener/tweener.js:350 (0x7febd02d3c48 @ 100) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #5 0x7fff0e3e3970 b resource:///org/gnome/gjs/modules/tweener/tweener.js:365 (0x7febd02d3cd0 @ 10) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #6 0x7fff0e3e3a60 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7febd02d3230 @ 386) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #7 0x7fff0e3e3b10 b resource:///org/gnome/shell/ui/tweener.js:245 (0x7febd02cf808 @ 159) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #8 0x7fff0e3e3be0 b resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7febd02b5de0 @ 71) Aug 19 11:34:11 localhost org.gnome.Shell.desktop[2503]: #9 0x7fff0e3e3c80 b resource:///org/gnome/shell/ui/tweener.js:220 (0x7febd02cf780 @ 15) Following suggestions in previous bug reports about this I went through and removed all of my shell extensions: chris@localhost:~/.local/share/gnome-shell/extensions$ ls -l total 0 chris@localhost:~/.local/share/gnome-shell/extensions$ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-10-24 (1395 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (3 days ago) UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1787822/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second
** Summary changed: - Resizing any window will randomly result in glitchy appearance for a fraction of a second + Resizing any window will randomly result in graphics corruption for a fraction of a second -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872802/+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 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1884428 Title: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory) Status in gnome-calculator package in Ubuntu: New Status in snapd package in Ubuntu: New Bug description: new bug ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-59-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 18:21:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-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.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1884428/+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 1874874] Re: Focal detects wrong driver version 440 for NVIDIA GTX 550
nvidia-driver-440 contains some invalid modaliases that cause to be detected as a valid driver for the wrong card. ** Package changed: ubuntu-drivers-common (Ubuntu) => nvidia-graphics- drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1874874 Title: Focal detects wrong driver version 440 for NVIDIA GTX 550 Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: My desktop PC has an NVIDIA GeForce GTX 550 Ti. Just installed Focal selecting the option to install 3rd-party drivers during setup process, and after the first boot screen resolution is 800x600. I verified the detected version of NVIDIA driver and I realized it was 440, although correct version is 390. Finally I manually installed proper version (390) and now the graphics are working OK. This is the output for the command "$ lspci -nn": 01:00.0 VGA compatible controller: NVIDIA Corporation GF116 [GeForce GTX 550 Ti] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) This is the output for the command "# ubuntu-drivers devices": == /sys/devices/pci:00/:00:02.0/:01:00.0 == modalias : pci:v10DEd1244sv1043sd83BEbc03sc00i00 vendor : NVIDIA Corporation model: GF116 [GeForce GTX 550 Ti] driver : nvidia-driver-435 - distro non-free driver : nvidia-driver-390 - distro non-free driver : nvidia-driver-440 - distro non-free recommended driver : nvidia-340 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin The version 440 is recommended, but it's not correct for this model (390 should be recommended instead) The issue was not present in previous versions (in both 19.10 and 18.04 driver 390 was recommended correctly) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1874874/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers
** Changed in: dnsmasq (Ubuntu) Status: Triaged => New ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => New ** Changed in: network-manager (Ubuntu) Status: Invalid => New ** Changed in: network-manager (Ubuntu Precise) Status: Invalid => New ** Changed in: dnsmasq (Ubuntu) Assignee: nikhil (nikhilnikki) => (unassigned) ** Changed in: dnsmasq (Ubuntu Precise) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: network-manager (Ubuntu Precise) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Changed in: network-manager (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned) ** Summary changed: - dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers + SDFEEWRDSsdfdasfsdf ** Description changed: - A number of reports already filed against network-manager seem to - reflect this problem, but to make things very clear I am opening a new - report. Where appropriate I will mark other reports as duplicates of - this one. - - Consider a pre-Precise system with the following /etc/resolv.conf: - - nameserver 192.168.0.1 - nameserver 8.8.8.8 - - The first address is the address of a nameserver on the LAN that can - resolve both private and public domain names. The second address is the - address of a nameserver on the Internet that can resolve only public - names. - - This setup works fine because the GNU resolver always tries the first- - listed address first. - - Now the administrator upgrades to Precise and instead of writing the - above to resolv.conf, NetworkManager writes - - server=192.168.0.1 - server=8.8.8.8 - - to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to - resolv.conf. Resolution of private domain names is now broken because - dnsmasq treats the two upstream nameservers as equals and uses the - faster one, which could be 8.8.8.8. + dfasfwerwq2323sf ** Tags removed: precise xenial ** Information type changed from Public to Private -- 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/1003842 Title: SDFEEWRDSsdfdasfsdf Status in dnsmasq package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in dnsmasq source package in Precise: New Status in network-manager source package in Precise: New Status in dnsmasq package in Debian: New Bug description: dfasfwerwq2323sf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 360970] Re: Multi-monitor - When using two displays with different vertical resolution, icons get lost on the shorter display
** Attachment removed: "Screenshot of Displays settings"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/360970/+attachment/4646954/+files/Screenshot%20from%202016-04-25%2011-45-53.png
** Attachment removed: "Screenshot of displays showing issue"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/360970/+attachment/4646955/+files/Screenshot%20from%202016-04-25%2011-46-23.png
** Description changed:
- On a Multi-Monitor setup, where the extended desktop is non-rectangular
- in shape (ie. the displays are of a different resolution, and their
- top/bottom/left/right edges are not aligned), desktop icons are placed
- in non-accessible areas when arranged using the menu option 'View-
- Organise Desktop by Name' from the Desktop.
-
- See the attached image. The top three desktop items are not accessible,
- and can only be seen in the Workspace Switcher.
-
- Please also refer to the 'Non-Rectangular Extended Desktops' section of the
Multi-Monitor spec:
-
https://docs.google.com/a/canonical.com/document/d/1aHvJ-iIw-59bXTYBmIhQqEx0za2h9jpFE_RhZ2VOvJc/edit#bookmark=id.yph05n82oeff
-
- --
-
- [Test Case]
- 1. Set up two monitors side by side
- 2. Set left monitor to a smaller vertical resolution than the right monitor
- 3. for i in $(seq 1 50) ; do touch file-${i} ; done
- 4. Right click on desktop to bring up context menu, then 'Organize Desktop by
Name'
- 5. Should be: All icons from file-1 to file-50 (or as many fit on the screen)
should be visible
- Is: Icons for files at the top and/or bottom of the arranged columns are
not visible on any display
- 6. xrandr --output LVDS1 --off
- 7. Verify icons are arranged properly on the external monitor
- 8. Set up monitors one over the other
- 9. Verify icons are displayed in long columns spanning both displays with all
icons shown
+ a
** Changed in: nautilus (Ubuntu)
Status: Triaged => New
** Changed in: ayatana-design
Status: Fix Committed => New
** Summary changed:
- Multi-monitor - When using two displays with different vertical resolution,
icons get lost on the shorter display
+ adfsfafsd
** Tags removed: multimonitor precise quantal rls-x-notfixing trusty udp
vivid
** Project changed: ayatana-design => climage
** Information type changed from Public to Private
--
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/360970
Title:
adfsfafsd
Status in aaa:
New
Status in Nautilus:
Expired
Status in Unity:
Confirmed
Status in nautilus package in Ubuntu:
New
Bug description:
a
To manage notifications about this bug go to:
https://bugs.launchpad.net/climage/+bug/360970/+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 1886354] Re: Software app (gnome-software) Explore always hangs
I tried "sudo apt-get install --reinstall gnome-software" in case something was lost when upgrading to Ubuntu 20.04. Afterwards when I ran gnome-software, it said '"GNOME Software" needs to be restarted to use new plugins' but when I clicked "Restart Now", it hung. This time syslog had these lines: Jul 5 18:01:21 lxjima systemd[1989]: tracker-store.service: Succeeded. Jul 5 18:01:27 lxjima dbus-daemon[2153]: [session uid=2000 pid=2153] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=2000 pid=2140 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Jul 5 18:01:27 lxjima systemd[1989]: Starting Tracker metadata database store and lookup manager... Jul 5 18:01:27 lxjima dbus-daemon[2153]: [session uid=2000 pid=2153] Successfully activated service 'org.freedesktop.Tracker1' Jul 5 18:01:27 lxjima systemd[1989]: Started Tracker metadata database store and lookup manager. Jul 5 18:01:38 lxjima gnome-software-[217747]: Failed to quit service: Failed to see org.gnome.Software vanish: Waited for 3ms Jul 5 18:01:58 lxjima tracker-store[217754]: OK Jul 5 18:01:58 lxjima systemd[1989]: tracker-store.service: Succeeded. (but it's still hung) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs Status in gnome-software package in Ubuntu: New Bug description: The Explore tab of the "Software" app seems to be completely non- functional. It shows an initial screen with "Editors Picks", etc. but if you do any search or click one of the Categories, a blank screen appears with a forever-spinning indicator. The following error is written to syslog: ... dbus-daemon... Successfully activated service 'org.gnome.seahorse.Application' gnome-shell[]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1376 was not provided by any .service files gnome-shell[]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 4 but got 0 (complete syslog from during the run is attached as syslog.txt) STEPS TO REPRODUCE: 1. Run gnome-software (or run "Software" through the app-finder mechanism) 2. Click the "Explore" (leftmost) tab at the top 3. Scroll down and click "Audio & Video" under Categories RESULTS: White screen with forever-spinning indicator ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 17:40:51 2020 InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+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 1886354] Re: Software app (gnome-software) Explore always hangs
** Attachment added: "syslog.txt -- logged during gnome-software" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+attachment/5390007/+files/syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs Status in gnome-software package in Ubuntu: New Bug description: The Explore tab of the "Software" app seems to be completely non- functional. It shows an initial screen with "Editors Picks", etc. but if you do any search or click one of the Categories, a blank screen appears with a forever-spinning indicator. The following error is written to syslog: ... dbus-daemon... Successfully activated service 'org.gnome.seahorse.Application' gnome-shell[]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1376 was not provided by any .service files gnome-shell[]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 4 but got 0 (complete syslog from during the run is attached as syslog.txt) STEPS TO REPRODUCE: 1. Run gnome-software (or run "Software" through the app-finder mechanism) 2. Click the "Explore" (leftmost) tab at the top 3. Scroll down and click "Audio & Video" under Categories RESULTS: White screen with forever-spinning indicator ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 17:40:51 2020 InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+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 1886354] [NEW] Software app (gnome-software) Explore always hangs
Public bug reported: The Explore tab of the "Software" app seems to be completely non- functional. It shows an initial screen with "Editors Picks", etc. but if you do any search or click one of the Categories, a blank screen appears with a forever-spinning indicator. The following error is written to syslog: ... dbus-daemon... Successfully activated service 'org.gnome.seahorse.Application' gnome-shell[]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1376 was not provided by any .service files gnome-shell[]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 4 but got 0 (complete syslog from during the run is attached as syslog.txt) STEPS TO REPRODUCE: 1. Run gnome-software (or run "Software" through the app-finder mechanism) 2. Click the "Explore" (leftmost) tab at the top 3. Scroll down and click "Audio & Video" under Categories RESULTS: White screen with forever-spinning indicator ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 17:40:51 2020 InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-16 (50 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886354 Title: Software app (gnome-software) Explore always hangs Status in gnome-software package in Ubuntu: New Bug description: The Explore tab of the "Software" app seems to be completely non- functional. It shows an initial screen with "Editors Picks", etc. but if you do any search or click one of the Categories, a blank screen appears with a forever-spinning indicator. The following error is written to syslog: ... dbus-daemon... Successfully activated service 'org.gnome.seahorse.Application' gnome-shell[]: Received error from D-Bus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name :1.1376 was not provided by any .service files gnome-shell[]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 4 but got 0 (complete syslog from during the run is attached as syslog.txt) STEPS TO REPRODUCE: 1. Run gnome-software (or run "Software" through the app-finder mechanism) 2. Click the "Explore" (leftmost) tab at the top 3. Scroll down and click "Audio & Video" under Categories RESULTS: White screen with forever-spinning indicator ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 17:40:51 2020 InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-05-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886354/+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 1886351] [NEW] [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while
Public bug reported: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe1410 F pulseaudio /dev/snd/pcmC0D0c: joe1410 F...m pulseaudio /dev/snd/pcmC0D0p: joe1410 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 19:23:02 2020 InstallationDate: Installed on 2020-06-02 (33 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_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: Jul 05 17:44:12 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.26' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:17 joe dbus-daemon[729]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=125 pid=925 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Jul 05 17:44:56 joe systemd[900]: pulseaudio.service: Succeeded. Jul 05 17:45:05 joe systemd[900]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.60:bd06/26/2012:svnTOSHIBA:pnSatelliteL745:pvrPSK0YU-01V00E:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L745 dmi.product.sku: PSK0YU-01V00E dmi.product.version: PSK0YU-01V00E dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886351 Title: [Satellite L745, Conexant CX20585, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I recently installed Ubuntu 20.04 on my Toshiba Satellite-L740 laptop. I seem to lose audio periodically. At first I thought I hit something on the keyboard accidentally, but can now confirm it is a random occurrence with no input from me. I have tried toggling the mute/volume of the system but cannot recover the audio. When the audio is lost there is still audio activity shown on the VU meter from the source shown under the output device in sound settings. I also plugged in headphones and am able to hear audio in the headset. When unplugging headset the sound does not return to the speakers. There was no issue with audio on the laptop prior to installing Ubuntu 20.04 (previously Windows 10). It seems to come back on it's own sometimes but then gets lost again. A reboot of the machine sometimes recovers the audio but sometimes not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joe
[Desktop-packages] [Bug 1801161] Re: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug has been marked a duplicate of bug 1782984 Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- 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/1801161 Title: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in libreoffice package in Ubuntu: Confirmed Bug description: Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was: Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that. Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-calc 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 13:39:03 2018 InstallationDate: Installed on 2018-10-29 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Summary changed: - PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 + Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04
** Changed in: libx11 (Ubuntu) Importance: Undecided => High ** Bug watch removed: github.com/rust-windowing/glutin/issues #1034 https://github.com/rust-windowing/glutin/issues/1034 ** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #108 https://gitlab.freedesktop.org/mesa/mesa/issues/108 ** Bug watch removed: gitlab.gnome.org/GNOME/gtk/-/issues #2767 https://gitlab.gnome.org/GNOME/gtk/-/issues/2767 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
*** This bug is a duplicate of bug 1782984 *** https://bugs.launchpad.net/bugs/1782984 ** This bug has been marked a duplicate of bug 1782984 PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 ** Bug watch removed: Claws Mail bugzilla #4203 http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 ** Bug watch removed: redmine.audacious-media-player.org/issues #798 https://redmine.audacious-media-player.org/issues/798 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Status in libx11 package in Ubuntu: New Bug description: GTK2 applications randomly crash or freeze with error like: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. where is the name of the executable, e.g. audacious, soffice.bin, etc. RELATED BUGS LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 Audacious: https://redmine.audacious-media-player.org/issues/798 FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 ClawsMail: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 OTHER APPLICATIONS SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1886345] [NEW] Display gets corrupted and text gets replaced by odd characters
Public bug reported: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1886345 Title: Display gets corrupted and text gets replaced by odd characters Status in gnome-shell package in Ubuntu: New Bug description: This is a fresh install of 2020.04. Issue is that the display routinely gets corrupted and flickers with blocks of previously open windows. If left without a restart, the system menu text will get replaced by odd characters and system dialog boxes will not display, buttons for the dialog boxes will briefly appear with no text when cursor is over them. Very occasionally, the system will stop responding to the mouse and keyboard after clicking an icon on the dash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:24:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 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/1886345/+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 1782984] Re: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libx11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: PCManFM freezes with Assertion `!xcb_xlib_threads_sequence_lost' failed when clicking on a file or folder in 18.04 Status in libx11 package in Ubuntu: Confirmed Status in pcmanfm package in Ubuntu: Triaged Bug description: STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a SpaceFM file manager that is available in GTK2 and GTK3. The GTK2 version displays the behavior. The GTK3 version does not. Same with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1782984/+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 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
FTR, uploaded 2.6.0-3 to Debian/unstable with the patch mentionned by @digidietze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 usb-modeswitch: Instalados: 2.4.0+repack0-1ubuntu1 Candidato: 2.4.0+repack0-1ubuntu1 Tabla de versión: *** 2.4.0+repack0-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status This error appears just after login. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: usb-modeswitch 2.4.0+repack0-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 28 09:40:09 2017 ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-6 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: usb-modeswitch StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () __libc_start_main (main=0x555ed4e5f970, argc=3, argv=0x7ffd50b28338, init=, fini=, rtld_fini=, stack_end=0x7ffd50b28328) at ../csu/libc-start.c:291 ?? () Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+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 1886336] [NEW] Network Manager permissions issue
Public bug reported:
Description:Ubuntu 20.04 LTS
Release:20.04
network-manager:
Installed: 1.22.10-1ubuntu2.1
Candidate: 1.22.10-1ubuntu2.1
Version table:
*** 1.22.10-1ubuntu2.1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
1.22.10-1ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
Having recently updated from 19.19 to 20.04, I am now unable to add/edit
any connections. When I try, a dialogue box pops up saying;
"Failed to activate {SSID}
Not authorized to control networking."
I have spent some time trawling the web but no obvious solution was
found, but one post mentioned "nmcli g permissions" which I tried as
user and using sudo.
User output;
PERMISSION VALUE
org.freedesktop.NetworkManager.enable-disable-network no
org.freedesktop.NetworkManager.enable-disable-wifi no
org.freedesktop.NetworkManager.enable-disable-wwan no
org.freedesktop.NetworkManager.enable-disable-wimax no
org.freedesktop.NetworkManager.sleep-wake no
org.freedesktop.NetworkManager.network-control auth
org.freedesktop.NetworkManager.wifi.share.protecte d no
org.freedesktop.NetworkManager.wifi.share.open no
org.freedesktop.NetworkManager.settings.modify.sys tem no
org.freedesktop.NetworkManager.settings.modify.own auth
org.freedesktop.NetworkManager.settings.modify.hos tname auth
org.freedesktop.NetworkManager.settings.modify.glo bal-dns auth
org.freedesktop.NetworkManager.reload auth
org.freedesktop.NetworkManager.checkpoint-rollback auth
org.freedesktop.NetworkManager.enable-disable-statistics no
org.freedesktop.NetworkManager.enable-disable-connectivity-check no
org.freedesktop.NetworkManager.wifi.scan unknown
Sudo output;
org.freedesktop.NetworkManager.enable-disable-network yes
org.freedesktop.NetworkManager.enable-disable-wifi yes
org.freedesktop.NetworkManager.enable-disable-wwan yes
org.freedesktop.NetworkManager.enable-disable-wimax yes
org.freedesktop.NetworkManager.sleep-wake yes
org.freedesktop.NetworkManager.network-control yes
org.freedesktop.NetworkManager.wifi.share.protecte d yes
org.freedesktop.NetworkManager.wifi.share.open yes
org.freedesktop.NetworkManager.settings.modify.sys tem yes
org.freedesktop.NetworkManager.settings.modify.own yes
org.freedesktop.NetworkManager.settings.modify.hos tname yes
org.freedesktop.NetworkManager.settings.modify.glo bal-dns yes
org.freedesktop.NetworkManager.reload yes
org.freedesktop.NetworkManager.checkpoint-rollback yes
org.freedesktop.NetworkManager.enable-disable-statistics yes
org.freedesktop.NetworkManager.enable-disable-connectivity-check yes
org.freedesktop.NetworkManager.wifi.scan unknown
Now it seems to me that I should have more permissions as a user.
I have checked what the User output is when you boot into the live ISO
and it has all the same permissions as the Sudo output shown above. So
my guess would be that this is what myproblem is.
How can I fix these permission issues as a workaround while you
investigate this bug.
Thanks.
Jim!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu2.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Jul 5 19:07:19 2020
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2016-10-13 (1361 days ago)
InstallationMedia: It
IpRoute:
default via 192.168.0.2 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.176 metric 600
ProcEnviron:
LANGUAGE=en_GB
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2020-03-14 (113 days ago)
modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
[connection]
wifi.powersave = 2
mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
2020-01-01T15:53:38.227396
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI
WWAN-HW WWAN
running 1.22.10 connected started full enabled enabled
enabled enabled disabled
** Affects: network-manager (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 network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1886336
Title:
Network Manager permissions issue
Status in network-manager package in Ubuntu:
New
Bug description:
Description:Ubuntu 20.04 LTS
Release:20.04
network-manager:
Installed: 1.22.10-1ubuntu2.1
Candidate: 1.22.10-1ubuntu2.1
Version table:
*** 1.22.10-1ubuntu2.1 500
500
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop)
** Summary changed: - Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop) ** No longer affects: mesa-utils (Ubuntu) ** Summary changed: - Second Monitor on HDMI blank screen with Nvidia+Intel & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) ** Summary changed: - Second Monitor on HDMI blank screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) + Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1886323] Re: Engish print dialog in German Thunderbird
Sorry for the typo, I meant the printing dialog window of course. -- 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/1886323 Title: Engish print dialog in German Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I changed the langueage of my thunderbird client from English to German. Most parts of Thunderbird are now in German, but the pring dialog settings is still in English. I use Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.8.0+build2-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BuildID: 20200504155042 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 14:52:31 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-05-17 (49 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.8.0/20200504155042 (In use) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1886323/+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 1886333] Re: Nautilus goes berserk when trying to switch to list view in Trash
Oh, here's another quirk: When I click the Trash icon in Nautilus, Nautilus's Launcher icon immediately disappears, even though its window doesn't. It happened me a few times and each time I thought I had closed the window and forgotten, but then I realised, by minimizing all other windows one by one, that several Nautilus windows were still there. Pathetic. And this isn't just a bug in Nautilus (I'm sure the main triggering reason is a bug in nautilus), it's also a bug in whoever is responsible for managing windows (Xorg? Compiz? I have no idea), because it should never allow to hide a launcher icon for a window that remains open. That's an inconsistent situation that should just be forbidden at the deepest level. The whole thing is such a fucking mess. -- 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/1886333 Title: Nautilus goes berserk when trying to switch to list view in Trash Status in nautilus package in Ubuntu: New Bug description: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow. But if, for whatever valid reason, it did require a perceivable amount of time (which btw is an assumtion you should always make when designing the UI, because even a few milliseconds can be perceivable enough that visual feedback needs to be given and interaction can happen meanwhile), you should see a spinning icon somewhere giving you visual feedback that something is being processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long because Nautilus sucks and is slow and inefficient, but gives no visual feedback that it's processing something. But it doesn't end here: 4. Close Nautilus and open it again 5. Switch to list mode BEFORE you open trash (succesfully switches) 6. Open Trash => Now the Trash appears empty, even though it's not. Again, no idea whether it's loading and taking long: there's no indication of it. 7. Try to switch back to icon mode: => goes back to the folder you were browsing before, and does switch to icons mode. It's all a fucking mess - something is way slower than it should - the UI seems to be designed around the (never correct and in this case false) assumption that everything happens instantly, so there's no feedback when you need to wait because something is being loaded, and when that happens and you keep doing stuff, the behavior becomes inconsistent and everything goes completely berserk. This is fucking pathetic. And don't start with "You are using an old version of Ubuntu bla bla bla". I am using an old version because of an unrelated disgraceful regression in Nautilus itself which renders it completely unusable from Ubuntu 17.04 onward ana that to this day hasn't been fixed, of which luckily enough I became aware before I upgraded, so I stuck with 16.04. Furthermore, 16.04 is LTS and hasn't reached EOL yet, so bugs that render the system completely unusable like this one have to be fixed and the fix has to be released to 16.04. Anyway I don't give a fuck. I'm sick of Ubuntu and I'm switching to OpenSuse soon. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 18:42:26 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1161x849+533+136'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1886333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1886333] [NEW] Nautilus goes berserk when trying to switch to list view in Trash
Public bug reported: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow. But if, for whatever valid reason, it did require a perceivable amount of time (which btw is an assumtion you should always make when designing the UI, because even a few milliseconds can be perceivable enough that visual feedback needs to be given and interaction can happen meanwhile), you should see a spinning icon somewhere giving you visual feedback that something is being processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long because Nautilus sucks and is slow and inefficient, but gives no visual feedback that it's processing something. But it doesn't end here: 4. Close Nautilus and open it again 5. Switch to list mode BEFORE you open trash (succesfully switches) 6. Open Trash => Now the Trash appears empty, even though it's not. Again, no idea whether it's loading and taking long: there's no indication of it. 7. Try to switch back to icon mode: => goes back to the folder you were browsing before, and does switch to icons mode. It's all a fucking mess - something is way slower than it should - the UI seems to be designed around the (never correct and in this case false) assumption that everything happens instantly, so there's no feedback when you need to wait because something is being loaded, and when that happens and you keep doing stuff, the behavior becomes inconsistent and everything goes completely berserk. This is fucking pathetic. And don't start with "You are using an old version of Ubuntu bla bla bla". I am using an old version because of an unrelated disgraceful regression in Nautilus itself which renders it completely unusable from Ubuntu 17.04 onward ana that to this day hasn't been fixed, of which luckily enough I became aware before I upgraded, so I stuck with 16.04. Furthermore, 16.04 is LTS and hasn't reached EOL yet, so bugs that render the system completely unusable like this one have to be fixed and the fix has to be released to 16.04. Anyway I don't give a fuck. I'm sick of Ubuntu and I'm switching to OpenSuse soon. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 18:42:26 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1161x849+533+136'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial ** Description changed: Steps to reproduce: 1. open Nautilus 2. Select icons view 3. open Trash 4. try to switch to list view by clicking on the button on the top right Expected: should immediately switch to list mode. There's no acceptable valid reason for this to be slow, since it is possible to make it efficient enough to make it quick. If, for whatever valid reason, it did - require a perceivable amount of time, you should see a spinning icon - somewhere giving you visual feedback that something is being processed - (and you should be able to instantly go back to icons mode) + require a perceivable amount of time (which btw is an assumtion you + should always make when designing the UI, because even a few + milliseconds can be perceivable enough that visual feedback needs to be + given and interaction can happen meanwhile), you should see a spinning + icon somewhere giving you visual feedback that something is being + processed (and you should be able to instantly go back to icons mode) Observed: it remains in icons mode as if you hadn't clicked anything (despite the fact that the list mode button becomes apparently selected). I have no idea whether it simply ignores you and doesn't switch to list mode without any error message, or if it's actually processing and taking long
[Desktop-packages] [Bug 1886329] Re: The thing that opens by double-clicking on a .deb file never works
** Summary changed: - The crap that opens by double-clicking on a .deb file never works + The thing that opens by double-clicking on a .deb file never works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886329 Title: The thing that opens by double-clicking on a .deb file never works Status in gnome-software package in Ubuntu: New Bug description: I downloaded a .deb file. It was Virtual Box, but that is not relevant, nor is whether there was something wrong with that .deb file or whether my system was properly set up to be ready to install that package or not. I double-clicked on the .deb file from within a folder in Nautilus, and a program opened that if I'm not mistaken is called Ubuntu Software Center, or something like that. That showed a list with only one item that corresponded to the file I had opened: Virtual Box Whatever, with a title and a description of the package, and there was an "Install" button. I clicked the Install button. Expected: either install the package succesfully, or give me an error message telling me exactly why you can't install it. These are the two only possible expected outcomes; no other outcome is acceptable. Observed: First, when I clicked on Install, something showed up for a very brief time; maybe a progress bar or something. Then that went away, and the Install button was visible again. This already makes no sense. I clicked install, so either you are able to install or you are not. If you are not, you should be showing me an error message, and the Install button should no longer be called "Install" but either not be there or be called "try again" (unless if you first show me an error message and I dismiss it, then we may be back to square one). If you are able to install, then you should be installing it, and if you are, I should be seeing an indication of the status and progress of the installation. So either the installation silently failed and no error message was shown, which is not acceptable, or the installation was ongoing somewhere in the background, or being prepared for, and there was no indication of it. Then I clicked "Install" again. This time, an icon appeared in the Launcher with something that looked like an empty or almost empty progress bar (i.e. a progress bar at its very beginning). When a new icon shows up in the Launcher, a new window should ALWAYS be open. The very thing an icon in the Launcher represents is a window. But no. No window or popup showed up when the Launcher icon showed up, and clicking on it did nothing. By right-clicking on it there was no "quit" option either. So the launcher icon was probably some process that wasn't responding. First: if you launched a process that is not responding, something is broken. Secondly, you should detect it, show an error message, and allow me to take action. You don't just leave me with a stuck hung process and a Launcher icon that doesn't even allow me to figure out what the hung process is and to abort it. This is not the first time this happens to me. It has happened almost every time I've ever tried to install a .deb file by double-clicking on it (which is not something I do often). It doesn't matter whether the .deb file I'm trying to install is broken, or cannot be installed for any valid reason: if that is the case you tell me what that fucking reason it and show me an error message, with all the details and the options. NOTE: after all this, I restarted my system, and then I went to the folder containing the .deb file and ran: sudo apt install ./that_file.deb and that installed Virtual Box succesfully and seamlessly. All I was expecting the Ubuntu Software Center (or whatever that thing is called) to do by double clicking on the .deb file was the same thing I did by running that command from the terminal. The only reason I didn't do it from the terminal was to not have to google what the command was. That's why you are allowed to double-click on things, so the system takes care to do whatever it needs to be done for you. It's pathetic that by double clicking on a .deb file the system isn't able to install a package that I can seamlessly install with a one- line command that required no interaction (besides one single prompt "are you sure Y/N") and had no error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.13 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 17:26:39 2020 InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring
[Desktop-packages] [Bug 1886331] [NEW] Xorg freeze
Public bug reported: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.34:bd07/31/2019:svnHP:pnHPPavilionLaptop15-cw1xxx:pvr:rvnHP:rn8615:rvr46.23:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cw1xxx dmi.product.sku: 6QF12EA#AB7 dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 freeze ubuntu ** Attachment added: "dmesg.0" https://bugs.launchpad.net/bugs/1886331/+attachment/5389899/+files/dmesg.0 -- 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/1886331 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Cannot boot sometimes - black screen with a mouse pointer. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 18:47:44 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: rtl8821ce, 5.5.2.1, 5.4.0-39-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-39-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Pavilion Laptop 15-cw1xxx [103c:8615] InstallationDate: Installed on 2020-06-05 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP Pavilion Laptop 15-cw1xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a88d53cb-0507-4895-a6b9-15550b8ec4e3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: AMI dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8615 dmi.board.vendor: HP dmi.board.version: 46.23 dmi.chassis.type: 10 dmi.chassis.vendor: HP
[Desktop-packages] [Bug 1886329] [NEW] The crap that opens by double-clicking on a .deb file never works
Public bug reported: I downloaded a .deb file. It was Virtual Box, but that is not relevant, nor is whether there was something wrong with that .deb file or whether my system was properly set up to be ready to install that package or not. I double-clicked on the .deb file from within a folder in Nautilus, and a program opened that if I'm not mistaken is called Ubuntu Software Center, or something like that. That showed a list with only one item that corresponded to the file I had opened: Virtual Box Whatever, with a title and a description of the package, and there was an "Install" button. I clicked the Install button. Expected: either install the package succesfully, or give me an error message telling me exactly why you can't install it. These are the two only possible expected outcomes; no other outcome is acceptable. Observed: First, when I clicked on Install, something showed up for a very brief time; maybe a progress bar or something. Then that went away, and the Install button was visible again. This already makes no sense. I clicked install, so either you are able to install or you are not. If you are not, you should be showing me an error message, and the Install button should no longer be called "Install" but either not be there or be called "try again" (unless if you first show me an error message and I dismiss it, then we may be back to square one). If you are able to install, then you should be installing it, and if you are, I should be seeing an indication of the status and progress of the installation. So either the installation silently failed and no error message was shown, which is not acceptable, or the installation was ongoing somewhere in the background, or being prepared for, and there was no indication of it. Then I clicked "Install" again. This time, an icon appeared in the Launcher with something that looked like an empty or almost empty progress bar (i.e. a progress bar at its very beginning). When a new icon shows up in the Launcher, a new window should ALWAYS be open. The very thing an icon in the Launcher represents is a window. But no. No window or popup showed up when the Launcher icon showed up, and clicking on it did nothing. By right-clicking on it there was no "quit" option either. So the launcher icon was probably some process that wasn't responding. First: if you launched a process that is not responding, something is broken. Secondly, you should detect it, show an error message, and allow me to take action. You don't just leave me with a stuck hung process and a Launcher icon that doesn't even allow me to figure out what the hung process is and to abort it. This is not the first time this happens to me. It has happened almost every time I've ever tried to install a .deb file by double-clicking on it (which is not something I do often). It doesn't matter whether the .deb file I'm trying to install is broken, or cannot be installed for any valid reason: if that is the case you tell me what that fucking reason it and show me an error message, with all the details and the options. NOTE: after all this, I restarted my system, and then I went to the folder containing the .deb file and ran: sudo apt install ./that_file.deb and that installed Virtual Box succesfully and seamlessly. All I was expecting the Ubuntu Software Center (or whatever that thing is called) to do by double clicking on the .deb file was the same thing I did by running that command from the terminal. The only reason I didn't do it from the terminal was to not have to google what the command was. That's why you are allowed to double-click on things, so the system takes care to do whatever it needs to be done for you. It's pathetic that by double clicking on a .deb file the system isn't able to install a package that I can seamlessly install with a one-line command that required no interaction (besides one single prompt "are you sure Y/N") and had no error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-software 3.20.5-0ubuntu0.16.04.13 ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 Uname: Linux 4.4.0-184-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 5 17:26:39 2020 InstallationDate: Installed on 2013-10-11 (2458 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886329 Title: The crap that opens by double-clicking on a .deb file never works Status in gnome-software package in Ubuntu: New Bug description: I
[Desktop-packages] [Bug 1886330] [NEW] pulseaudio not working in Virtualbox
Public bug reported: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot_2020-07-05_11-52-59.png" https://bugs.launchpad.net/bugs/1886330/+attachment/5389892/+files/Screenshot_2020-07-05_11-52-59.png -- 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/1886330 Title: pulseaudio not working in Virtualbox Status in pulseaudio package in Ubuntu: New Bug description: I run my "work" VMs and in Xubuntu pulse audio often does not start. In this dump I tried to start music through Firefox and through my media player quodlibet and none of the audio starts. See attachment with the pulseaudio volume control and quodlibet stuck on time 0:00 like Firefox. I do not have the problem with plain Ubuntu, Ubuntu Mate nor with Ubuntu Studio. The problem is annoying, because I use Xubuntu for office and communication like Email and the WhatsApp/Firefox/ICE combination and with this bug WhatsApp is useless. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bertadmin 1490 F pulseaudio /dev/snd/pcmC0D0c: bertadmin 1490 F...m pulseaudio /dev/snd/pcmC0D0p: bertadmin 1490 F...m pulseaudio /dev/snd/timer: bertadmin 1490 f pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Jul 5 11:33:48 2020 InstallationDate: Installed on 2018-03-11 (847 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310) SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-03-04 (122 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1886330/+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 1876219] Re: iris driver for old cpu
@star-gmx : The above did work for me (but I only tried setting the variable before the command such as "VARIABLE=value command"), setting this variable MESA_LOADER_DRIVER_OVERRIDE=i965 for anything that uses the MESA driver, stops segmentation faults from happening. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1886326] [NEW] gnome-terminal does not retain maximised size when external monitor goes into power save
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 with standard Ubuntu Gnome desktop. ii gnome-terminal 3.36.2-1ubuntu1~20.04 amd64GNOME terminal emulator application ii gnome-terminal-data 3.36.2-1ubuntu1~20.04 all Data files for the GNOME terminal emulator ii libvte-2.91-0:amd64 0.60.3-0ubuntu1~20.04 amd64Terminal emulator widget for GTK+ 3.0 - runtime files ii libvte-2.91-common 0.60.3-0ubuntu1~20.04 amd64Terminal emulator widget for GTK+ 3.0 - common files Steps to reproduce: 1. Have laptop with 1920x1080 display, but closed so the display is not being used. 2. Have external 1920x1200 monitor connected via HDMI. 3. Open gnome-terminal and maximise it. 4. Press Windows+L to lock screen. 5. Leave computer locked for long enough for the monitor to go into power save. 6. Unlock. 7. Notice that gnome-terminal window no longer covers the whole screen - a 120 pixel bar of the desktop is visible at the bottom of the screen. 8. Double click on the gnome-terminal title bar in an attempt to maximise the window and discover that the window gets smaller (because it thought it was already maximised.) 9. Double click on the gnome-terminal title bar again and the window is then maximised correctly. Expected result: The gnome-terminal window remains maximised covering the whole screen at step 7. (However, if I were to unplug the external monitor and start using the laptop display I would expect the window to remain maximised but resized to cover the smaller display.) I suspect that this problem can be reproduced with any two differing display sizes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:47:50 2020 InstallationDate: Installed on 2020-04-18 (78 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Summary changed: - gnome-terminal does not re-maximise when display size changes + gnome-terminal does not retain maximised size when external monitor goes into power save -- 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/1886326 Title: gnome-terminal does not retain maximised size when external monitor goes into power save Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 with standard Ubuntu Gnome desktop. ii gnome-terminal 3.36.2-1ubuntu1~20.04 amd64GNOME terminal emulator application ii gnome-terminal-data 3.36.2-1ubuntu1~20.04 all Data files for the GNOME terminal emulator ii libvte-2.91-0:amd64 0.60.3-0ubuntu1~20.04 amd64Terminal emulator widget for GTK+ 3.0 - runtime files ii libvte-2.91-common 0.60.3-0ubuntu1~20.04 amd64Terminal emulator widget for GTK+ 3.0 - common files Steps to reproduce: 1. Have laptop with 1920x1080 display, but closed so the display is not being used. 2. Have external 1920x1200 monitor connected via HDMI. 3. Open gnome-terminal and maximise it. 4. Press Windows+L to lock screen. 5. Leave computer locked for long enough for the monitor to go into power save. 6. Unlock. 7. Notice that gnome-terminal window no longer covers the whole screen - a 120 pixel bar of the desktop is visible at the bottom of the screen. 8. Double click on the gnome-terminal title bar in an attempt to maximise the window and discover that the window gets smaller (because it thought it was already maximised.) 9. Double click on the gnome-terminal title bar again and the window is then maximised correctly. Expected result: The gnome-terminal window remains maximised covering the whole screen at step 7. (However, if I were to unplug the external monitor and start using the laptop display I would expect the window to remain maximised but resized to cover the smaller display.) I suspect that this problem can be reproduced with any two differing display sizes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 15:47:50 2020 InstallationDate: Installed on 2020-04-18 (78 days ago) InstallationMedia: Ubuntu 20.04 LTS
[Desktop-packages] [Bug 1870519] Re: Ubuntu 20.04 Dock - Autohide not working
gsettings set org.gnome.shell.extensions.dash-to-dock intellihide false //autohide ubuntu gnome dock without mouse over -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1870519 Title: Ubuntu 20.04 Dock - Autohide not working Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Hello, Ubuntu 20.04 beta (Apr 2nd 2020) 1. Set in dconf editor under /org/gnome/shell/extensions/dash-to-dock/ autohide:true docker-fixed:false 2. Maximize some desktop window and the dock disappears. Now, move mouse to the dock area but the dock will never appear. (on 18.04 this works properly - using the same dconf properties in both 20.04 and 18.04) It should auto appear when you move the mouse where the dock was hidden. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-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-ubuntu-dock/+bug/1870519/+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 1870519] Re: Ubuntu 20.04 Dock - Autohide not working
run that in terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1870519 Title: Ubuntu 20.04 Dock - Autohide not working Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Hello, Ubuntu 20.04 beta (Apr 2nd 2020) 1. Set in dconf editor under /org/gnome/shell/extensions/dash-to-dock/ autohide:true docker-fixed:false 2. Maximize some desktop window and the dock disappears. Now, move mouse to the dock area but the dock will never appear. (on 18.04 this works properly - using the same dconf properties in both 20.04 and 18.04) It should auto appear when you move the mouse where the dock was hidden. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-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-ubuntu-dock/+bug/1870519/+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 1884393] Re: With Auto-hide dock enabled, icons get hidden behind dock & dock does not hide untill there's an app near it
gsettings set org.gnome.shell.extensions.dash-to-dock intellihide false -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1884393 Title: With Auto-hide dock enabled, icons get hidden behind dock & dock does not hide untill there's an app near it Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Bug description: Gnome Settings>Appearance> auto hide dock //enable it automatically you might see icons getting hidden behind dock (keep windows away from dock). Not only desktop getting hidden under dock looks unaesthetic, But don't you think dock should remain hidden till the user points mouse at it? Other wise we won't be able to use left side of the desktop to keep icons. Dock never hides till an app is near it, so desktop icons may get under it. So that we can use the entire left side of desktop to keep icons, with the auto hide dock option enabled, don't you think dock should remain hidden until user points mouse near it? //probably a logical error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 21 02:14:32 2020 DistUpgraded: 2020-05-10 12:37:12,893 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0794] InstallationDate: Installed on 2019-12-13 (190 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Beta amd64 (20191210) MachineType: Dell Inc. Vostro 15-3568 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-37-generic root=UUID=d2615e91-f6ee-49c3-8ba6-e3f3be730703 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-10 (41 days ago) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.4.0 dmi.board.name: 0880CR dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.asset.tag: NN_PC_NB0 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.4.0:bd05/10/2019:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn0880CR:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 15-3568 dmi.product.sku: 0794 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1884393/+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 1886322] Re: Unable to move files in bulk on desktop using rectangle
I can confirm this issue. Using ctrl-click to select multiple icons also results in only one being moved. The moved icon retains its selection and the other icons are de- selected. ** Package changed: ubuntu => gnome-shell-extension-desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- 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/1886322 Title: Unable to move files in bulk on desktop using rectangle Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: Hi, This bug started to happen like 1-2 months ago, and as I remember I didn't do any customizations like installing any external plugins and etc, but I have some stuff already like custom icons, shell, theme... but it worked normaly before. What is happening is that when I select more than 1 file on desktop, no matter which file it is (folder, .txt, image.. anything), and when I try to move around desktop from one place to another, it will move only 1 file and not the rest. So, unable to move selected files on desktop (drag and drop using cursor's rectangle). Its simple issue, no need for video or screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:18:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1886322/+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 1886322] [NEW] Unable to move files in bulk on desktop using rectangle
You have been subscribed to a public bug: Hi, This bug started to happen like 1-2 months ago, and as I remember I didn't do any customizations like installing any external plugins and etc, but I have some stuff already like custom icons, shell, theme... but it worked normaly before. What is happening is that when I select more than 1 file on desktop, no matter which file it is (folder, .txt, image.. anything), and when I try to move around desktop from one place to another, it will move only 1 file and not the rest. So, unable to move selected files on desktop (drag and drop using cursor's rectangle). Its simple issue, no need for video or screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 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' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 14:18:03 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB GDDR5 DVI-I/DVI-D/HDMI/DP [174b:e221] InstallationDate: Installed on 2020-03-24 (103 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: MSI MS-7693 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=20c309bc-2b22-43b0-938e-0761aa26cd13 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G46 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd10/31/2012:svnMSI:pnMS-7693:pvr2.0:rvnMSI:rn970A-G46(MS-7693):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- Unable to move files in bulk on desktop using rectangle https://bugs.launchpad.net/bugs/1886322 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons 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 1880191] Re: usb_modeswitch 2.5.2 segfault
I've made an attempt to fix the problem upstream, largely along the lines of Sebastien's patch. I intend to release 2.6.1 soon. If anybody wants to test, the files are here: https://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=19605#p19605 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1880191 Title: usb_modeswitch 2.5.2 segfault Status in usb-modeswitch package in Ubuntu: Incomplete Bug description: The version that is shipped with Ubuntu 20.04 x64 segfaults: Starting program: /usr/sbin/usb_modeswitch -W -v 05c6 -p 1000 -K [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Take all parameters from the command line * usb_modeswitch: handle USB devices with multiple modes * Version 2.5.2 (C) Josua Dietze 2017 * Based on libusb1/libusbx ! PLEASE REPORT NEW CONFIGURATIONS ! DefaultVendor= 0x05c6 DefaultProduct= 0x1000 StandardEject=1 [New Thread 0x77d58700 (LWP 16370)] Look for default devices ... found USB ID 05ac:8406 found USB ID 1d6b:0003 found USB ID 05ac:0291 found USB ID 05ac:828f found USB ID 0a5c:4500 found USB ID 05c6:1000 vendor ID matched product ID matched found USB ID 0781:5567 found USB ID 1d6b:0002 Found devices in default mode (1) Access device 015 on bus 001 Get the current device configuration ... Current configuration number is 1 Use interface number 0 with class 8 Use endpoints 0x01 (out) and 0x81 (in) USB description data (for identification) Error: could not get description string "serial number" - Manufacturer: Qualcomm, Incorporated Product: Qualcomm CDMA Technologies MSM Serial No.: read error - Sending standard EJECT sequence Looking for active drivers ... libusb: error [_open_sysfs_attr] open /sys/bus/usb/devices/1-2/bConfigurationValue failed ret=-1 errno=2 Thread 1 "usb_modeswitch" received signal SIGSEGV, Segmentation fault. 0x9771 in ?? () (gdb) bt #0 0x9771 in ?? () #1 0x7109 in ?? () #2 0x77dd10b3 in __libc_start_main (main=0x6820, argc=7, argv=0x7fffe098, init=, fini=, rtld_fini=, stack_end=0x7fffe088) at ../csu/libc-start.c:308 #3 0x7bde in ?? () I tried to compile latest available version: usb- modeswitch-2.6.0.tar.bz2 (md5: be73dcc84025794081a1d4d4e5a75e4c) and it does not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1880191/+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 1676763] Re: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr()
I've made an attempt to fix the problem of interfaces missing in the original Tcl wrapper. I intend to release 2.6.1 soon. If anybody wants to test, the files are here: https://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?p=19605#p19605 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1676763 Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() Status in usb-modeswitch package in Ubuntu: Fix Released Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 usb-modeswitch: Instalados: 2.4.0+repack0-1ubuntu1 Candidato: 2.4.0+repack0-1ubuntu1 Tabla de versión: *** 2.4.0+repack0-1ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status This error appears just after login. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: usb-modeswitch 2.4.0+repack0-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 28 09:40:09 2017 ExecutablePath: /usr/sbin/usb_modeswitch_dispatcher InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: /usr/sbin/usb_modeswitch_dispatcher --switch-systemd 1-6 ProcEnviron: LANG=es_ES.UTF-8 PATH=(custom, no user) Signal: 11 SourcePackage: usb-modeswitch StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () __libc_start_main (main=0x555ed4e5f970, argc=3, argv=0x7ffd50b28338, init=, fini=, rtld_fini=, stack_end=0x7ffd50b28328) at ../csu/libc-start.c:291 ?? () Title: usb_modeswitch_dispatcher crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1676763/+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 1883705] Re: SRU the current 2.5.25 stable update
With -proposed enabled I updated libgphoto2 to version 2.5.25-0ubuntu0.1. When I connected my Panasonic digital camera I received a notification that a 16GB device was available. As per test case I was able to browse the contents of the camera's internal memory card and import 156 photos into Shotwell. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgphoto2 in Ubuntu. https://bugs.launchpad.net/bugs/1883705 Title: SRU the current 2.5.25 stable update Status in libgphoto2 package in Ubuntu: Fix Released Status in libgphoto2 source package in Focal: Fix Committed Status in libgphoto2 package in Debian: Fix Released Bug description: * Impact That's a stable update including bugfixes and support for newer cameras The list of changes is available there: https://sourceforge.net/projects/gphoto/files/libgphoto/2.5.25/ * Test case Connect a camera and check that the desktop correctly see it and prompt for an action. Check that the content can be browsed from nautilus and the photos imported from shotwell (unmount the device from nautilus first if needed) * Regression potential Nothing specific to check, the fixes are mostly for hardware that was not working and the change devices specific To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1883705/+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 1861882] Re: Shift key cancels accented IME input with fcitx
Nice finding! Thanks for the quick hack! Another way (takes a bit more time to get used to) is to press Ctrl key before pressing Space. This effectively finalizes and commits the word, and can be used to stop adding accent marks within the same word. It can also be applied to Windows version: pressing A, then Ctrl, then S produces "as". -- 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/1861882 Title: Shift key cancels accented IME input with fcitx Status in chromium-browser package in Ubuntu: Confirmed Bug description: Prerequisites: * Ubuntu Bionic or Zorin OS 15 * chromium-browser=79.0.3945.79-0ubuntu0.18.04.1 amd64 (UPDATE: chromium-browser=80.0.3987.87-0ubuntu0.18.04.1 amd64, chromium-browser=81.0.4044.138-0ubuntu0.18.04.1 amd64, and chromium-browser=83.0.4103.61-0ubuntu0.18.04.1 amd64 also reproduce this issue) * fcitx=1:4.2.9.6-1 * fcitx-unikey=0.2.4-1.1 Steps: * Launch fcitx and chromium-browser. * Focus input to a text box (e.g. omnibox, F12 console). * Trigger fcitx IME with UniKey. * Type a character sequence that produces a Vietnamese character (e.g. "aws" (without quotes), with Telex input method, will produce "ắ"). Do not press Ctrl or Spacebar, which will commit the word. * Press either Shift key. Expected result: * Nothing happens, or the typed character should not change, at the very least. Actual result: * Typed word reverts back to "aws". The underline on the word still retains, meaning that the word is not yet committed. This issue is a real nuisance when typing a Vietnamese word followed by a Shift-punctuation (e.g. a question mark right after the word). Remarks: * This issue does not happen on any other programs, only happens on Chromium and Google Chrome, versions 79 to 83 (and possibly next versions). * Using fcitx-mozc, after typing a Japanese word, the Shift key does not change the character. * This issue, more or less, is similar to bug #1859294, although not a strict duplicate. * This issue has been reported in Chromium Bugs, at: https://bugs.chromium.org/p/chromium/issues/detail?id=1086946 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1861882/+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 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Daniel, the shell itself is still usable in my scenario. You can open the calendar, options menu on the top right and even new windows from the panel. But the windows itself and desktop (including right click menu) are frozen. I just tested it with the latest gnome 3.36.3 updates and it still happens, still easily reproducible with many right clicks on the desktop. -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+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 1886323] [NEW] Engish print dialog in German Thunderbird
Public bug reported: I changed the langueage of my thunderbird client from English to German. Most parts of Thunderbird are now in German, but the pring dialog settings is still in English. I use Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.8.0+build2-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BuildID: 20200504155042 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 14:52:31 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-05-17 (49 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.8.0/20200504155042 (In use) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (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 thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1886323 Title: Engish print dialog in German Thunderbird Status in thunderbird package in Ubuntu: New Bug description: I changed the langueage of my thunderbird client from English to German. Most parts of Thunderbird are now in German, but the pring dialog settings is still in English. I use Kubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.8.0+build2-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BuildID: 20200504155042 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Jul 5 14:52:31 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-05-17 (49 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.8.0/20200504155042 (In use) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1886323/+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 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
On the upstream report for this bug in GNOME Mutter (https://gitlab.gnome.org/GNOME/mutter/issues/1268), Robert Mader just wrote > We landed a fix for this specific issue in 3.36.4 which is going to get released over the next few days. Please report back if you still see the bug after your distribution has picked up the update. Great to hear. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+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 1886319] [NEW] License information for apps is incorrect
Public bug reported: Eg. it tells me that Brasero is Proprietary when in fact it is GPL2. It also says Brasero has never been updated, which is also clearly incorrect. I've seen these issues with others apps too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software (not installed) Uname: Linux 5.7.0-050700rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 12:34:18 2020 InstallationDate: Installed on 2020-04-26 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of Brasero in GNOME Software app incorrectly saying it is Proprietary" https://bugs.launchpad.net/bugs/1886319/+attachment/5389823/+files/brasero_proprietary.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1886319 Title: License information for apps is incorrect Status in gnome-software package in Ubuntu: New Bug description: Eg. it tells me that Brasero is Proprietary when in fact it is GPL2. It also says Brasero has never been updated, which is also clearly incorrect. I've seen these issues with others apps too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software (not installed) Uname: Linux 5.7.0-050700rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 12:34:18 2020 InstallationDate: Installed on 2020-04-26 (69 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1886319/+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 1886314] [NEW] preinstall `earlyoom` by default
Public bug reported: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- 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/1886314 Title: preinstall `earlyoom` by default Status in ubuntu-meta package in Ubuntu: New Bug description: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1886314/+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 1746738] Re: резервное копирование не удалось
** Package changed: memtest86+ (Ubuntu) => ubuntu ** Package changed: ubuntu => deja-dup (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1746738 Title: резервное копирование не удалось Status in deja-dup package in Ubuntu: New Bug description: Создать резервную копию. Пишет: резервное копирование не удалось (неизвестная ошибка). "The above configuration updates the package list, downloads, and installs available upgrades every day. The local download archive is cleaned every week. On servers upgraded to newer versions of Ubuntu, depending on your responses, the file listed above may not be there. In this case, creating a new file of this name should also work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1746738/+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 1746738] [NEW] резервное копирование не удалось
You have been subscribed to a public bug: Создать резервную копию. Пишет: резервное копирование не удалось (неизвестная ошибка). "The above configuration updates the package list, downloads, and installs available upgrades every day. The local download archive is cleaned every week. On servers upgraded to newer versions of Ubuntu, depending on your responses, the file listed above may not be there. In this case, creating a new file of this name should also work. ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New -- резервное копирование не удалось https://bugs.launchpad.net/bugs/1746738 You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup 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 1258919] Re: 067b:2305 printing issue with parallel-to-usb adapter
I am using PL2305 to print to an old Fujitsu line printer and was missing the last few lines of the printout every time. The workaround suggested above worked for me, too :) I changed: lpadmin -p fujitsu -v usb://Unknown/Printer -E to lpadmin -p fujitsu -E -v parallel:/dev/usb/lp0 -- 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/1258919 Title: 067b:2305 printing issue with parallel-to-usb adapter Status in cups package in Ubuntu: Confirmed Bug description: I have an old HP Deskjet 710C parallel printer. I really don't print a lot, so it ages well. I just replaced my former desktop with a new barebone without parallel port - no space to embed a PCI IEEE 1284 adapter. So I just bought a cable which is a parallel-to-usb adapter : it is a Sweex adapter, the kernel recognizes it as : Prolific Technology, Inc. PL2305 Parallel Port I configured cups to use this new adapter, with the same old pnm2ppa driver. When I try to print a test page from cups (or other printings) it goes well, until close to the end, when the printing suddenly stops, without the sheet being released : I have to power off the printer, which as a side effect triggers the sheet ejection before power off. I read various articles and forums on this topic before posting. Playing with usblp, kernel blacklists and /dev/usb/lp0 does not solve anything. I wanted to be sure that it was not the Prolific controller which was flawed. So I connected it to a windows 7 virtual machine into Virtualbox; Windows installed various drivers, and eventually various printings ran seamlessly - without my issue on GNU/Linux. So my conclusion is that the controller is ok. I also just tested mainline kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.13-rc3-trusty/linux- image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_amd64.deb . No improvement, my test page stops being printed at the same spot close to the end. So I can assume that there is a bug in the controller's driver. Best regards R. Grasso WORKAROUND: Setup Lprng locally from lpr - not configurable from KDE/Systemsettings - then from my main computer with CUPS 1.6.1, I configured a remote printer: lpd://10.0.0.1/lp ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image (not installed) ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Dec 8 13:53:43 2013 HibernationDevice: RESUME=UUID=a16e3a2c-0f38-4e72-9c51-145a864b60a1 InstallationDate: Installed on 2013-11-06 (32 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Shuttle Inc. DS47D MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=8c51cecc-9054-4edc-8b06-afb7bb4ebd2e ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-14-generic N/A linux-backports-modules-3.11.0-14-generic N/A linux-firmware 1.116 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS47D dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03:bd08/09/2013:svnShuttleInc.:pnDS47D:pvrV1.0:rvnShuttleInc.:rnFS47D:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: DS47D dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1258919/+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 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
The same thing happens with nvidia-driver-410.104 while using VLC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
The same thing happens with nvidia-driver-410 while using VLC -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876219] Re: iris driver for old cpu
@akechishiro: Did the above mentioned workaround works for you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1876219 Title: iris driver for old cpu Status in mesa package in Ubuntu: Confirmed Bug description: I am not completely sure where I should file the bug. I am using Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the default graphics driver, which results in crashes in multiple apps including guvcview and calibre. Setting MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but is it true that iris does not support older generations of Intel CPUs? If it is the case would it be possible to revert to i965 in those circumstances? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Adam - thanks for the clarification. I'm afraid for some of us ordinary users the subtleties of 'fix released' but not released in ubuntu to the outside world evaded me. Sorry. I sincerely hope the fix works! -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+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 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
same problem on Ubuntu 18.04, when running mate-polkit command in terminal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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
