[Desktop-packages] [Bug 1917987] Re: Unable to drag URL from firefox and drop it to ~/Desktop or any other folder
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1917987 Title: Unable to drag URL from firefox and drop it to ~/Desktop or any other folder Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Open Firefox, enable Bookmarks Toolbar 3. Bookmark some page in it to bookmarks toolbar 4. Open Nautilus 5. Drag some bookmark from Bookmarks Toolbar and drop it to Nautilus window Expected results: * Nautilus accepted this drop, created desktop-file with URL, will allow to open the web-page on launch Actual results: * Nautilus shows the error window with text > Drag and drop is not supported. > An invalid drag type was used. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME-Flashback:GNOME Date: Sat Mar 6 11:57:50 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(800, 505)' SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-01-25 (39 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1917987/+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 1928428] [NEW] yara std theme background is transparent in GnuCash dropdown list for entry behind mouse pointer
Public bug reported: 1) Ubuntu version: Ubuntu 20.04.2 LTS 2) Package version: yaru-theme-gtk version 20.04.10.1 When using the latest GnuCash Flathub 4.5 (but I believe all GnuCash versions 3.0 and later have the same problem) and the Yaru Standard application theme, when moving the mouse pointer thru a dropdown list, the background of the line behind the current mouse pointer is transparent, so you can see the foreground text of the item in the list, and in the background, whatever is under the dropdown list. This makes it very hard to read. See https://lists.gnucash.org/pipermail/gnucash-user/attachments/20210513/ae179ec6/attachment.png for an example display of this problem. The Yaru Light and Dark themes and also Adwaita (default), do NOT have this problem. 3) Expected result: the background color of the dropdown list should be white, like other lines. Refer https://bugs.gnucash.org/show_bug.cgi?id=797493 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnucash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1928428 Title: yara std theme background is transparent in GnuCash dropdown list for entry behind mouse pointer Status in yaru-theme package in Ubuntu: New Bug description: 1) Ubuntu version: Ubuntu 20.04.2 LTS 2) Package version: yaru-theme-gtk version 20.04.10.1 When using the latest GnuCash Flathub 4.5 (but I believe all GnuCash versions 3.0 and later have the same problem) and the Yaru Standard application theme, when moving the mouse pointer thru a dropdown list, the background of the line behind the current mouse pointer is transparent, so you can see the foreground text of the item in the list, and in the background, whatever is under the dropdown list. This makes it very hard to read. See https://lists.gnucash.org/pipermail/gnucash-user/attachments/20210513/ae179ec6/attachment.png for an example display of this problem. The Yaru Light and Dark themes and also Adwaita (default), do NOT have this problem. 3) Expected result: the background color of the dropdown list should be white, like other lines. Refer https://bugs.gnucash.org/show_bug.cgi?id=797493 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1928428/+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 1928348] Re: Activation of network connection fails
girish@girish-System-Product-Name:~$ sudo su [sudo] password for girish: root@girish-System-Product-Name:/home/girish# NetworkManager root@girish-System-Product-Name:/home/girish# locate -b "\NetworkManager" /etc/NetworkManager /usr/lib/NetworkManager /usr/lib/x86_64-linux-gnu/NetworkManager /usr/sbin/NetworkManager /var/lib/NetworkManager root@girish-System-Product-Name:/home/girish# man NetworkManager root@girish-System-Product-Name:/home/girish# NetworkManager -V 1.30.0 root@girish-System-Product-Name:/home/girish# NetworkManager root@girish-System-Product-Name:/home/girish# which NetworkManager /usr/sbin/NetworkManager Strange behavior. Today morning when I switched on the PC, after around 10 seconds, network connected and worked fine automatically, I didn't changed anything, otherwise yesterday I got "Activation of Network connection failed" popped up and after that popup, it got connected automatically. So, in all I can say that this is somewhere bug in either kernel, userspace or NetworkManager program. Something need to be fix for sure. -- 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/1928348 Title: Activation of network connection fails Status in network-manager package in Ubuntu: New Bug description: girish@girish-System-Product-Name:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 girish@girish-System-Product-Name:~$ I just upgraded my home testing and learning PC from 20.10 to 21.04 yesterday. Before upgrade, my network connection which is a USB wifi adapter which connects to my android device's hotspot; working fine, but after upgrade I noticed that to activate the network connection, I have to follow these steps : 1.Turn off Wifi settings 2.Turn off hotspot 3.Turn off mobie data connection 4.Turn on mobie data connection 5.Turn on hotspot 6.Turn on Wifi in settings Now, it works. I don't know the complete steps to file a bug, this is my first chance so please bear with me and ask, if i need to provide more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1928348/+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 1919031] Re: gnome-shell-extension-appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1.
[Expired for gnome-shell-extension-appindicator (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1919031 Title: gnome-shell-extension-appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1. Status in gnome-shell-extension-appindicator package in Ubuntu: Expired Bug description: It is a bug It seems to happens when gnome-shell-extension-appindicator is updated from 33-1 to 33.1-0ubuntu0.20.04.1. Please file a bug report from the Ubuntu terminal: ubuntu-bug gnome-shell-extension-appindicator or add yourself as "This bug affects you" to an existing bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 13 16:36:57 2021 InstallationDate: Installed on 2020-11-09 (123 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator 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-appindicator/+bug/1919031/+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 1891956] Re: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-m
[Expired for libreoffice (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Expired -- 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/1891956 Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 Status in libreoffice package in Ubuntu: Expired Bug description: not sure what exactly happened, I uninstalled it and it never totally went. So, when I tried reinstalling it, I was told it was broken ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-44.48-generic 5.4.55 Uname: Linux 5.4.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Aug 17 18:32:07 2020 ErrorMessage: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 InstallationDate: Installed on 2020-08-12 (5 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.3 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.5-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite '/usr/bin/soffice', which is also in package openoffice-debian-menus 4.0-9702 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1891956/+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 1828671] Re: Xephyr Input is broken
Sebastien Bacher , pls also tell what's the alternate software/method to do multiseat. After Xephyr, their seems no hope. I run a computer lab for poor people, but without multiseat it's not possible. What's the alternate. -- 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/1828671 Title: Xephyr Input is broken Status in xorg-server package in Ubuntu: New Bug description: I'm using Xephyr for a multiseat system (4 GPUs -> up to 12 screens; using VirtualGL for 3D acceleration.) The eventual command line that LightDM ends up running is: Xephyr -fullscreen :0 -seat seat5 -auth /var/run/lightdm/root/:0 -nolisten tcp In 18.04 and earlier this works great. Important note: There is a strong chance my system had the version of Xephyr from the Multiseat PPA with Evdev support patches (https://launchpad.net/~ubuntu- multiseat/+archive/ubuntu/xephyr/+packages). In 19.04 I get: root@redstone-server:~# DISPLAY=:200.1 Xephyr -fullscreen -seat seat6 :20 Pointer option key (_source) of value (server/udev) not assigned! Pointer option key (major) of value (13) not assigned! Pointer option key (minor) of value (80) not assigned! Pointer option key (config_info) of value (udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5.5/2-1.5.5.3/2-1.5.5.3.1/2-1.5.5.3.1:1.0/0003:045E:0083.001D/input/input58/event16) not assigned! Pointer option key (GrabDevice) of value (on) not assigned! couldn't find driver for pointer device "Microsoft Basic Optical Mouse" (/dev/input/event16) Pointer option key (_source) of value (server/udev) not assigned! Pointer option key (major) of value (13) not assigned! Pointer option key (minor) of value (32) not assigned! Pointer option key (config_info) of value (udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5.5/2-1.5.5.3/2-1.5.5.3.1/2-1.5.5.3.1:1.0/0003:045E:0083.001D/input/input58/mouse0) not assigned! Pointer option key (GrabDevice) of value (on) not assigned! couldn't find driver for pointer device "Microsoft Basic Optical Mouse" (/dev/input/mouse0) Kbd option key (_source) of value (server/udev) not assigned! Kbd option key (major) of value (13) not assigned! Kbd option key (minor) of value (93) not assigned! Kbd option key (config_info) of value (udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5.5/2-1.5.5.3/2-1.5.5.3.2/2-1.5.5.3.2:1.0/0003:045E:0752.001E/input/input59/event29) not assigned! Kbd option key (GrabDevice) of value (on) not assigned! couldn't find driver for keyboard device "Microsoft Wired Keyboard 400" (/dev/input/event29) The display is correct, but no user input (mouse or keyboard) works. It looks like Xephyr can't find any input drivers. I also tried specifying drivers (eg Evdev, libinput, keyboard, mouse, ...) Nothing worked. Extracting the version of Xephyr from https://launchpad.net/~ubuntu- multiseat/+archive/ubuntu/xephyr/+packages runs correctly. Required details: lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 apt-cache policy xserver-xephyr xserver-xephyr: Installed: 2:1.20.4-1ubuntu3 Candidate: 2:1.20.4-1ubuntu3 Version table: *** 2:1.20.4-1ubuntu3 500 500 http://ca.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1828671/+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 1928378] Re: Desktop hanging and shoutting down
Thanks for the bug report. Next time the freeze happens, after rebooting please run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt and then attach the resulting text files here. Please also check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1928378 Title: Desktop hanging and shoutting down Status in Ubuntu: Incomplete Bug description: freezing Desktop pc and shutting down after several minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 01:02:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 09da:2268 A4Tech Co., Ltd. USB Keyboard Bus 001 Device 003: ID 09da:3519 A4Tech Co., Ltd. A4Tech OpticalMouse Bus 001 Device 016: ID 22d9:2771 MediaTek CPH1723 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=0e1a6726-8543-47b1-9c6c-49d2e3f29ee7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2PH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd11/03/2015:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2PH-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1928378/+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 1928358] Re: gnome-shell spamming the log
*** This bug is a duplicate of bug 1880405 ***
https://bugs.launchpad.net/bugs/1880405
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 1880405, 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 1880405
Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no
properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
--
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/1928358
Title:
gnome-shell spamming the log
Status in gnome-shell package in Ubuntu:
New
Bug description:
I don't know what happened, but I just sat down at my machine to find
it sluggish. Digging further, I find that gnome-shell is spamming the
system log with these messages:
May 13 12:06:42 cerberus gnome-shell[3120]: JS ERROR: TypeError: null has no
properties
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
actionMoveWorkspace@resource:///org/gnome/shell/ui/windowManager.js:2170:23
_showWorkspaceSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2144:18
Restarting the shell with:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting…")'
restored it to sanity.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 13 12:07:00 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-29 (348 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-11-04 (190 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928358/+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 1928312] Re: ghost compose window with wayland
Thanks for the bug report. Since so many bugs are caused by extensions, please try removing these as a first step: 'disconnect-w...@kgshank.net', 'topIcons@adel.gadl...@gmail.com', 'mediapla...@patapon.info', 'add-username-toppa...@brendaw.com' Then log in again and verify the bug still happens. If it does then please also try disabling 'Ubuntu Dock' in the Extensions app. ** 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/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 Pac
[Desktop-packages] [Bug 1928206] Re: File extension included in renaming selection
** Summary changed: - File rename selection and single click do not work uniformly across the Files application + File extension included in renaming selection -- 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/1928206 Title: File extension included in renaming selection Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: This is on Ubuntu 20.10 Groovy Gorilla. Problem1: If I open Files (the Nautilus equivalent) and select a file and press F2 or right click and select "rename", I'm given the option of renaming the file. If the filename is someFile.txt, the "someFile" portion is highlighted automatically, so when I start renaming it, the ".txt" portion remains unaffected. This is the normal and expected behaviour. However, when I do the same thing directly on the Desktop for any file on the Desktop, the entire "someName.txt" gets highlighted, and the full name isn't even shown at first glance. The attachments show details. Problem2: In Files preferences > Behaviour > Open Action, if I select "Single click to open items", it works fine everywhere except for files on the Desktop, where I have to double click a file to open it. So the bug here is that there seems to be some inconsistency in the behaviour of files on the Desktop vs. the files that are opened in the Files window. If any of the Desktop files are opened in Files, it works fine. The problem happens only when performing these actions directly on files that are on the Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928206/+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 1928388] Re: Select Area on desktop highlights wrong area.
*** This bug is a duplicate of bug 1925095 *** https://bugs.launchpad.net/bugs/1925095 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 1925095, 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. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-desktop- icons-ng (Ubuntu) ** This bug has been marked a duplicate of bug 1925095 GNOME Desktop selection is misaligned with the mouse on 21.04-dev -- 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/1928388 Title: Select Area on desktop highlights wrong area. Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: When I use my mouse to select an area on the desktop by holding down the left mouse bottom, the area being highlighted is off from where my mouse actually is. This issue appeared right after upgrading to 21.04 Release of ubuntu being used: Ubuntu 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 13 22:41:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.11.0-17-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-17-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5600 [8086:1612] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 5600 [1558:6556] Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6556] InstallationDate: Installed on 2020-12-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: XMG P65xSG-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=0bb35a23-8355-4f0e-8e1a-5d4a92903184 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.011 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xSG-A dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd09/15/2015:br5.11:svnXMG:pnP65xSG-A:pvrNotApplicable:rvnNotebook:rnP65xSG-A:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65xSG-A dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: XMG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go
[Desktop-packages] [Bug 1928407] [NEW] Screen not locked when coming out of suspend/hibernate
Public bug reported: when using my hp if my screen is a sleep and i wake it up it dosen't ask me for my password it should ask me i'm using Ubuntu 21 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:41:23 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1928407 Title: Screen not locked when coming out of suspend/hibernate Status in gnome-screensaver package in Ubuntu: New Bug description: when using my hp if my screen is a sleep and i wake it up it dosen't ask me for my password it should ask me i'm using Ubuntu 21 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:41:23 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screensaver Symptom: security Title: Screen not locked when coming out of suspend/hibernate UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1928407/+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 1928406] [NEW] [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume
Public bug reported: speaker audio is low compared to windows 10 the sound needs to be better optimized im using ubuntu 21 it should sound the same as in windows 10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: familypc 1345 F pulseaudio /dev/snd/controlC1: familypc 1345 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:31:32 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1928406 Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: speaker audio is low compared to windows 10 the sound needs to be better optimized im using ubuntu 21 it should sound the same as in windows 10 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: familypc 1345 F pulseaudio /dev/snd/controlC1: familypc 1345 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 13 21:31:32 2021 InstallationDate: Installed on 2021-05-14 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [HP 15 TS Notebook PC, Realtek ALC3227, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2014 dmi.bios.release: 15.22 dmi.bios.vendor: Insyde dmi.bios.version: F.16 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2211 dmi.board.vendor: Hewlett-Packard dmi.board.version: 86.26 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 86.26 dmi.modalias: dmi:bvnInsyde:bvrF.16:bd04/24/2014:br15.22:efr86.26:svnHewlett-Packard:pnHP15TSNotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2211:rvr86.26:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 15 TS Notebook PC dmi.product.sku: G9D75UA#ABA dmi.product.version: 097412405F0620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/
[Desktop-packages] [Bug 1894373] Re: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem
https://github.com/torvalds/linux/commit/8eedd3a70a70f51fa963f3ad7fa97afd0c75bd44 #diff-4dffb9d83f72678edb79fe170c75652f4cd5575be7d46cf406c72d8d205a43d6 -- 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/1894373 Title: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Everything works well, except the Headphone jack. The Headphones are detected, they are not mutted in alsamixer and pavucontrol detects them and detects sound is going to the headphones. However there is no sound. With speakers everything is allright ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 4502 F pulseaudio /dev/snd/pcmC0D0p: daniel 4502 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 5 14:22:55 2020 InstallationDate: Installed on 2018-02-19 (928 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio Interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Only some of outputs are working Title: [UX430UA, Realtek ALC295, Black Headphone Out, Left] Playback problem UpgradeStatus: Upgraded to bionic on 2018-09-21 (714 days ago) dmi.bios.date: 12/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA 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.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-09-05T13:28:26.876229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1894373/+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 1928388] Re: Select Area on desktop highlights wrong area.
** Package changed: ubuntu => xorg (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/1928388 Title: Select Area on desktop highlights wrong area. Status in xorg package in Ubuntu: New Bug description: When I use my mouse to select an area on the desktop by holding down the left mouse bottom, the area being highlighted is off from where my mouse actually is. This issue appeared right after upgrading to 21.04 Release of ubuntu being used: Ubuntu 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 13 22:41:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.11.0-17-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-17-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5600 [8086:1612] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 5600 [1558:6556] Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6556] InstallationDate: Installed on 2020-12-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: XMG P65xSG-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=0bb35a23-8355-4f0e-8e1a-5d4a92903184 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.011 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xSG-A dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd09/15/2015:br5.11:svnXMG:pnP65xSG-A:pvrNotApplicable:rvnNotebook:rnP65xSG-A:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65xSG-A dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: XMG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1928388/+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 1928388] [NEW] Select Area on desktop highlights wrong area.
You have been subscribed to a public bug: When I use my mouse to select an area on the desktop by holding down the left mouse bottom, the area being highlighted is off from where my mouse actually is. This issue appeared right after upgrading to 21.04 Release of ubuntu being used: Ubuntu 21.04 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .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 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 13 22:41:28 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.11.0-17-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-17-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5600 [8086:1612] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 5600 [1558:6556] Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:6556] InstallationDate: Installed on 2020-12-23 (141 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: XMG P65xSG-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=0bb35a23-8355-4f0e-8e1a-5d4a92903184 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2015 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.011 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65xSG-A dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.011:bd09/15/2015:br5.11:svnXMG:pnP65xSG-A:pvrNotApplicable:rvnNotebook:rnP65xSG-A:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65xSG-A dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: XMG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- Select Area on desktop highlights wrong area. https://bugs.launchpad.net/bugs/1928388 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1926256] Re: Pasted text in the terminal is always highlighted and selected
This is not an issue with the terminals, this is a new feature of bash-5.1. Search for the word "highlight" at https://lists.gnu.org/archive/html/info-gnu/2020-12/msg3.html . --- This could not theoretically be a bug in gnome-terminal/vte. Terminals don't directly paint a letter as a consequence of the user pressing that letter, or pasting something. I'm certain you can think of plenty of cases where pressing a certain letter does not cause that letter to be painted on the canvas, but some other action (larger repaints), or perhaps nothing at all. When you press a letter, or paste some text, it is forwarded towards the kernel over the tty line, but is not displayed. The kernel then might handle it itself, or forward further towards some application (e.g. bash in this case). Then that application may or may not decide to paint something. Whatever it decides to paint may or may not be the same as the typed letter or pasted text. But even if it's the same, the terminal has no way of making this connection. "The user pressed the letter X, I've forwarded it, 100 milliseconds later I received a letter X to be painted, it must be the «same» X" -- it cannot work like this. What happens in this particular case is that you paste "foo", and in response bash instructs the terminal to print "foo" in inverse colors. The terminal does what it must do: obeys this instuction (without having the slightest idea that it's related to the paste). --- Two more things to mention to complete the picture: There is a so-called "bracketed paste mode", where special markers are inserted at the beginning and end of pasted data. This is how applications (bash in this case) can distinguish it from data typed by the user, without relying on timing heuristics. Also, some terminals have a legacy "local echo" mode where pressed keys immediately appear on the screen. I'm fairly certain it's not used anywhere nowadays. Most terminals don't support it, and VTE removed it in version 0.60, see https://gitlab.gnome.org/GNOME/vte/-/issues/69 . ** Bug watch added: gitlab.gnome.org/GNOME/vte/-/issues #69 https://gitlab.gnome.org/GNOME/vte/-/issues/69 -- 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/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This is the only way i managed to speed up my "Trackpoint" on HP ZBOOK 15u G6 to a acceptable level. user1@lab1-w:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Mouseid=11 [slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Touchpad id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=10 [slave keyboard (3)] ↳ ALP0017:00 044E:121C UNKNOWN id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ HP WMI hotkeysid=18 [slave keyboard (3)] user1@lab1-w:~$ xinput --list-props 15 Device 'PS/2 Generic Mouse': Device Enabled (180): 1 Coordinate Transformation Matrix (182): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 0.20 libinput Natural Scrolling Enabled (317): 1 libinput Natural Scrolling Enabled Default (318): 0 libinput Scroll Methods Available (319):0, 0, 1 libinput Scroll Method Enabled (320): 0, 0, 1 libinput Scroll Method Enabled Default (321): 0, 0, 1 libinput Button Scrolling Button (322): 2 libinput Button Scrolling Button Default (323): 2 libinput Middle Emulation Enabled (346):0 libinput Middle Emulation Enabled Default (347):0 libinput Accel Speed (324): 1.00 libinput Accel Speed Default (325): 0.00 libinput Accel Profiles Available (326):1, 1 libinput Accel Profile Enabled (327): 1, 0 libinput Accel Profile Enabled Default (328): 1, 0 libinput Left Handed Enabled (329): 0 libinput Left Handed Enabled Default (330): 0 libinput Send Events Modes Available (302): 1, 0 libinput Send Events Mode Enabled (303):0, 0 libinput Send Events Mode Enabled Default (304):0, 0 Device Node (305): "/dev/input/event8" Device Product ID (306):2, 1 libinput Drag Lock Buttons (331): libinput Horizontal Scroll Enabled (332): 1 user1@lab1-w:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Mouseid=11 [slave pointer (2)] ⎜ ↳ ALP0017:00 044E:121C Touchpad id=12 [slave pointer (2)] ⎜ ↳ PS/2 Generic Mouseid=15 [slave pointer (2)] ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=16 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ HP HD Camera: HP HD Cameraid=10 [slave keyboard (3)] ↳ ALP0017:00 044E:121C UNKNOWN id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ HP WMI hotkeysid=18 [slave keyboard (3)] user1@lab1-w:~$ xinput --list-props 15 Device 'PS/2 Generic Mouse': Device Enabled (180): 1 Coordinate Transformation Matrix (182): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 0.20 libinput Natural Scrolling Enabled (317): 1 libinput Natural Scrolling Enabled Default (318): 0 libinput Scroll Methods Available (319):0, 0, 1 libinput Scroll Method Enabled (320): 0, 0, 1 libinput Scroll Method Enabled Default (321): 0, 0, 1 libinput Button Scrolling Button (322): 2 libinput Button
[Desktop-packages] [Bug 1928348] Re: Activation of network connection fails
** Package changed: ubuntu => network-manager (Ubuntu) -- 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/1928348 Title: Activation of network connection fails Status in network-manager package in Ubuntu: New Bug description: girish@girish-System-Product-Name:~$ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 girish@girish-System-Product-Name:~$ I just upgraded my home testing and learning PC from 20.10 to 21.04 yesterday. Before upgrade, my network connection which is a USB wifi adapter which connects to my android device's hotspot; working fine, but after upgrade I noticed that to activate the network connection, I have to follow these steps : 1.Turn off Wifi settings 2.Turn off hotspot 3.Turn off mobie data connection 4.Turn on mobie data connection 5.Turn on hotspot 6.Turn on Wifi in settings Now, it works. I don't know the complete steps to file a bug, this is my first chance so please bear with me and ask, if i need to provide more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1928348/+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 1928348] [NEW] Activation of network connection fails
You have been subscribed to a public bug: girish@girish-System-Product-Name:~$ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 girish@girish-System-Product-Name:~$ I just upgraded my home testing and learning PC from 20.10 to 21.04 yesterday. Before upgrade, my network connection which is a USB wifi adapter which connects to my android device's hotspot; working fine, but after upgrade I noticed that to activate the network connection, I have to follow these steps : 1.Turn off Wifi settings 2.Turn off hotspot 3.Turn off mobie data connection 4.Turn on mobie data connection 5.Turn on hotspot 6.Turn on Wifi in settings Now, it works. I don't know the complete steps to file a bug, this is my first chance so please bear with me and ask, if i need to provide more details. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Activation of network connection fails https://bugs.launchpad.net/bugs/1928348 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1923845] Re: Please compress packages with zstd by default
Sorry, those comments were for LP: #1926437, which is at least related.
:-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ext/repo_deb.c
lintian - needs fix malformed-deb-archive
lutris - needs fix, lutris/util/extract.py
obs-build - needs fix Build/Deb.pm
osc - needs fix osc/util/debquery.py control.tar.zst only
python-apt - needs fix
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
radare2 - needs fix
reprepro- needs fix, debfile.c
vim-scripts - needs fix debPlugin/autoload/deb.vim
winetricks - needs fix when Debian switches src/winetricks
zeroinstall-injector - needs fix src/zeroinstall/archive.ml
acr - skip, does not _have to_ be fixed, just creates packages,
see dist/deb_hand.mak
alien - skip, uses dpkg-deb to extract .deb
ansible - not affected, just test data in dbdata.tar.xz
anthy - not affected, just changelog entry
apt - seems fixed already
ceph- not affected in Ubuntu's version
circlator - not affected, just test data
cowdancer - not affected, just documentation
eccodes - skip, just orig-data.tar.xz
eckit - skip, just ...orig-data.tar.xz
firefox - skip, profdata.tar.xz
firefox-esr - skip, profdata.tar.xz
galculator - skip, just changelog
grads - skip, ...orig-data.tar.xz
gvmd- skip, just creates xz compressed .deb
insighttoolkit4 - skip, ...orig-data.tar.xz
jdeb- skip, just creates compressed .deb packages
jmol- skip, just local data archive
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.0.0ubuntu0.20.04.5 on Focal.
root@f-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:56:02--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.61MB/sin 1.2s
2021-05-13 19:56:03 (4.61 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@f-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@f-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=---
ii python-apt-common 2.0.0ubuntu0.20.04.5 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.0.0ubuntu0.20.04.5 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsol
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.1.3ubuntu1.4 on Groovy.
root@gg-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:51:34--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.70MB/sin 1.1s
2021-05-13 19:51:36 (4.70 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@gg-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@gg-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name VersionArchitecture Description
+++-=-==--
ii python-apt-common 2.1.3ubuntu1.4 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.1.3ubuntu1.4 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
libsolv - needs fix, ex
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 2.2.0~ubuntu0.21.04.1 on Hirsute.
root@hh-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:42:59--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.78MB/sin 1.1s
2021-05-13 19:43:00 (4.78 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@hh-lp1926437:~# python3 -c 'import apt_inst; import apt_pkg;
apt_pkg.init_config();
print(apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall())'
True
root@hh-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=-=--
ii python-apt-common 2.2.0~ubuntu0.21.04.1 all Python interface to
libapt-pkg (locales)
ii python3-apt 2.2.0~ubuntu0.21.04.1 amd64Python 3 interface to
libapt-pkg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope - needs fix, diffoscope/comparators/deb.py
dpkg- needs fix, change default
dpkg-sig- needs fix, dpkg-sig
dpmb- needs fix, maybe later, for Debian
elfutils- may need fix, uses dpkg-deb if it is available, does not
handle .gz either
file- needs fix, magic/Magdir/archive
[Desktop-packages] [Bug 1923845] Re: Please compress packages with zstd by default
Verified 1.6.5ubuntu0.6 on Bionic.
root@bb-lp1926437:~# wget
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
--2021-05-13 19:29:17--
https://people.canonical.com/~rbalint/zstd-debs/glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb
Resolving people.canonical.com (people.canonical.com)... 91.189.89.62
Connecting to people.canonical.com (people.canonical.com)|91.189.89.62|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 5618446 (5.4M) [application/x-debian-package]
Saving to: ‘glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb’
glibc-doc-reference_2.33-0ubuntu2~zstd1_all
100%[=>]
5.36M 4.80MB/sin 1.1s
2021-05-13 19:29:18 (4.80 MB/s) - ‘glibc-doc-
reference_2.33-0ubuntu2~zstd1_all.deb’ saved [5618446/5618446]
root@bb-lp1926437:~# python3
Python 3.6.9 (default, Jan 26 2021, 15:33:00)
[GCC 8.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apt_inst
>>> import apt_pkg
>>> apt_pkg.init_config()
>>> apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
True
>>>
root@bb-lp1926437:~# dpkg -l python3-apt python-apt-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture
Description
+++-=-===-===-
ii python-apt-common 1.6.5ubuntu0.6 all
Python interface to libapt-pkg (locales)
ii python3-apt 1.6.5ubuntu0.6 amd64
Python 3 interface to libapt-pkg
root@bb-lp1926437:~#
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1923845
Title:
Please compress packages with zstd by default
Status in appstream-glib package in Ubuntu:
New
Status in apt package in Ubuntu:
New
Status in aptly package in Ubuntu:
New
Status in boinc package in Ubuntu:
New
Status in busybox package in Ubuntu:
New
Status in cdebootstrap package in Ubuntu:
New
Status in cdist package in Ubuntu:
New
Status in debdelta package in Ubuntu:
New
Status in debian-el package in Ubuntu:
New
Status in debootstrap package in Ubuntu:
Fix Released
Status in debsig-verify package in Ubuntu:
New
Status in debsigs package in Ubuntu:
New
Status in diffoscope package in Ubuntu:
New
Status in dpkg package in Ubuntu:
New
Status in dpkg-sig package in Ubuntu:
New
Status in file package in Ubuntu:
New
Status in libsolv package in Ubuntu:
New
Status in lintian package in Ubuntu:
New
Status in lutris package in Ubuntu:
New
Status in obs-build package in Ubuntu:
New
Status in osc package in Ubuntu:
New
Status in radare2 package in Ubuntu:
New
Status in reprepro package in Ubuntu:
New
Status in vim-scripts package in Ubuntu:
New
Status in zeroinstall-injector package in Ubuntu:
New
Bug description:
https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
on Hirsute having both data and control members of the .deb being
compressed with zstd. It can be handy for testing various tools.
[dpkg]
Decompression support in dpkg landed first in Bionic and is being SRUd to
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the
zstd-compressed binary packages.
From dpkg's perspective the upgrade path is cleared.
The original plan was compressing only the internal data.tar .deb
member, but dpkg uses uniform compression by default since dpkg 1.19.0
thus I'm collecting all the changes to support control.tar.zst, too,
in this bug.
Reviewed packages from:
https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1
appstream-glib - needs fix: libappstream-builder/asb-package-deb.c
aptly - needs fix: deb/deb.go
boinc - needs fix: debian/fetch_example_applications.sh
busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
cdebootstrap- needs fix: src/package.c
cdist - may need fix, can use dpkg-deb:
cdist/preos/debootstrap/files/devuan-debootstrap/functions
debdelta- needs fix: debdelta debpatch.sh
debian-el - needs fix: deb-view.el
debian-handbook - needs fix, maybe later, for Debian
debootstrap - needs fix,
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
debsigs - needs fix, debsigs
debsig-verify - needs fix, src/debsig-verify.c
diffoscope -
[Desktop-packages] [Bug 1928378] [NEW] Desktop hanging and shoutting down
Public bug reported: freezing Desktop pc and shutting down after several minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 01:02:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 09da:2268 A4Tech Co., Ltd. USB Keyboard Bus 001 Device 003: ID 09da:3519 A4Tech Co., Ltd. A4Tech OpticalMouse Bus 001 Device 016: ID 22d9:2771 MediaTek CPH1723 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=0e1a6726-8543-47b1-9c6c-49d2e3f29ee7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2PH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd11/03/2015:br5.6:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2PH-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1928378 Title: Desktop hanging and shoutting down Status in xorg package in Ubuntu: New Bug description: freezing Desktop pc and shutting down after several minutes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 14 01:02:54 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 510 [8086:1902] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd HD Graphics 510 [1458:d000] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 09da:2268 A4Tech Co., Ltd. USB Keyboard Bus 001 Device 003: ID 09da:3519 A4Tech Co., Ltd. A4Tech OpticalMouse Bus 001 Device 016: ID 22d9:2771 MediaTek CPH1723 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-43-generic root=UUID=0e1a6726-8543-47b1-9c6c-49d2e3f29ee7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2PH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type:
[Desktop-packages] [Bug 1925795] Re: SRU the current 0.20.4 stable update
The pinenty test was successful after a retry -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsecret in Ubuntu. https://bugs.launchpad.net/bugs/1925795 Title: SRU the current 0.20.4 stable update Status in libsecret package in Ubuntu: Fix Released Status in libsecret source package in Focal: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some bugfixes and translation updates https://gitlab.gnome.org/GNOME/libsecret/-/blob/master/NEWS There are non trivial changes to the meson build system included in the update but we still build using autotools so that's not impacting us * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Libsecret is providing an API to access gnome-keyring secrets, try a few applications using it and make sure credentials are correctly available. To list a few possible candidate softwares - evince (try to open a a password protected pdf, it should store and remember the password) - evolution - epiphany-browser - vinagre - balsa - deja-dup * Regression potential Nothing specific to try in those changes, just ensure the library still access the passwords as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsecret/+bug/1925795/+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 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter
While I waited for reply, I found an appropriate solution. The cause of the problem was that in the system with lightdm and unity-greeter installed as a desktop manager and a greeter respectively timeout intervals are given _twice_ as numeric values: (1) Time before suspend in lightdm. (2) Time before suspend in unity-greeter. To change the first set of parameters (for lightdm) I needed to specify the values for the user lightdm by means of dconf editor: sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 I also changed the type of action after the suspend time elapses to 'nothing' sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' sudo -u lightdm dbus-launch gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' To change the second set of parameters (for unity-greeter) I needed to perform a similar action: sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 And sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing' sudo -u lightdm dbus-launch gsettings set com.canonical.unity.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' Test showed that no further suspend event was observed. There was no bug, rather simple misunderstanding of that lightdm and unity-greeter store parameters in different places. With kind regards, Ruben Alexandrovich Iskandaryan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of system
[Desktop-packages] [Bug 1388491]
I've submitted a patch: https://gerrit.libreoffice.org/c/core/+/115535 Waiting for review -- 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/1388491 Title: [upstream] calc: "Cut" and "Paste special" -> "Transpose" affects other cells Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: Confirmed Bug description: Step to reproduce: 1. Open the attached ods file. 2. Select I12 to L16 and cut this region (Ctrl+X). (This bug doesn't occur with copy) 3. Select I5 and open Paste Special dialog (Shift+Ctrl+V). 4. Enable "Transpose" option and Click "OK" Then, values of some cells in C9 to E10, which are not related to blank cells are changed: C9: =C3/SUM(C$3:C$6) -> K7/SUM(C$3:C$6) D9: =D3/SUM(D$3:D$6) -> L7/SUM(D$3:D6) E9: =E3/SUM(E$3:E$6) -> M7/SUM(E$3:E$6) C10: =C4/SUM(C$3:C$6) -> K8/SUM(C$3:C$6) D10: =D4/SUM(D$3:D$6) -> L8/SUM(D$3:D6) E10: =E4/SUM(E$3:E$6) -> M8/SUM(E$3:E$6) My environment is Ubuntu 14.04 LibreOffice 4.2.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1388491/+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 1772465]
*** Bug 132889 has been marked as a duplicate of this bug. *** -- 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/1772465 Title: [upstream] Pressing undo in Writer removes text but not formatting Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: To reproduce this bug, follow these steps: 1) Create two paragraphs of text, one with font size 14 and the other with size 18. 2) Copy some text from the first paragraph to the end of the second paragraph using Ctrl-C and Ctrl-V. 3) Now press immediately Ctrl-Z for undo. 4) While the cursor is still at the end of the second paragraph, type some new text. As a user, I would expect the new text to have font size 18, since that’s the size of the text just before the cursor. However, as it appears, the new text gets font size 14 because of the text that was copied from the first paragraph. Thus it seems that Ctrl-Z did not undo the whole copy operation but instead just removed the copied text and left its formatting. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 17:25:11 2018 InstallationDate: Installed on 2017-02-13 (462 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to artful on 2017-11-05 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772465/+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 1903632]
Same problem here. In MS Office you can scroll using touchscreen input but here it has no similar option. Please include this important option for touchscreen users. -- 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/1903632 Title: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way. Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue. There are times when a user might want to scroll their screen by touching their screen. But I can't do this anymore. I want to know what went wrong? What can I do? Any info is appreciated. Note: Currently, I can scroll without in issue in Nautilus. But I can't do the same in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select words on screen whenever I touch my screen to scroll. But we all know, SCROLL ≠ SELECT. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 09:25:39 2020 DistUpgraded: 2020-10-28 23:47:17,717 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: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:0641] InstallationDate: Installed on 2020-02-16 (267 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 5548 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago) dmi.bios.date: 05/28/2019 dmi.bios.release: 5.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0FFJC4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10: dmi.product.name: Inspiron 5548 dmi.product.sku: 0641 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/df-libreoffice/+bug/1903632/+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 1928312] Re: ghost compose window with wayland
doesn't look like there is sensitive information in #8, hope I didn't miss anything ;) -- 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/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroups: adm audio cdrom dip libvirt lpadmin nordvpn plugdev sambashare sudo v
[Desktop-packages] [Bug 1928312] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497164/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroups: a
[Desktop-packages] [Bug 1928312] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497168/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroups: adm audio
[Desktop-packages] [Bug 1928312] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroup
[Desktop-packages] [Bug 1928312] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497166/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroups: adm audio c
[Desktop-packages] [Bug 1928312] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497167/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: hirsute wayland-session Uname: Linux 5.11.0-17-lowlatency x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) UserGroups: adm audio
[Desktop-packages] [Bug 1927958] Re: Switching power source retains tab, even if it does not exist
Sounds similar to the upstream report https://gitlab.gnome.org/GNOME /gnome-power-manager/-/issues/11 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-power-manager/-/issues #11 https://gitlab.gnome.org/GNOME/gnome-power-manager/-/issues/11 ** Changed in: gnome-power-manager (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1927958 Title: Switching power source retains tab, even if it does not exist Status in gnome-power-manager package in Ubuntu: Triaged Bug description: When switching from a power source (e.g., "Laptop battery") to another power source (e.g. "AC adapter"), where the latter does not have the tab which was selected in the former, then no information at all is displayed. Ubuntu 21.04, gnome-power-manager 3.32.0-2 Actual behavior === 1. `gnome-power-statistics` starts with "AC adapter" selected left and "Details" tab being shown on the right 2. Click on "Laptop battery" left: Laptop battery "Details" tab is shown on the right 3. Click on "History" or "Statistics" tab: The appropriate information for "Laptop battery" is shown on the right. So far, so good. 4. Click on "AC adapter" left again: Now, *nothing* is shown on the right. This should not happen. Expected behavior = 4. Click on "AC adapter": "Details" tab should be shown. (In general: *Any* tab should be shown, but here, "Details" is the only one available.) This is probably a result from trying to fix https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/766876 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1927958/+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 1928312] Re: ghost compose window with wayland
apport information ** Tags added: apport-collected ** Description changed: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2018-04-27 ( days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: gnome-shell 3.38.4-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 + RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 + Tags: hirsute wayland-session + Uname: Linux 5.11.0-17-lowlatency x86_64 + UpgradeStatus: Upgraded to hirsute on 2021-04-25 (18 days ago) + UserGroups: adm audio cdrom dip libvirt lpadmin nordvpn plugdev sambashare sudo vboxusers video wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1928312/+attachment/5497163/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to
[Desktop-packages] [Bug 1928312] Re: ghost compose window with wayland
Thank you for your bug report, it seems rather a shell issue getting confused about the status of the windows ** Package changed: thunderbird (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928312/+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 1928312] Re: ghost compose window with wayland
Could you do $ apport-collect 1928312 now that it got reassigned that would add the debug informations for right component -- 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/1928312 Title: ghost compose window with wayland Status in gnome-shell package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928312/+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 1875671] Re: wayland: desktop folder missing in sidebar
Reading their comment they suggest that Gtk is doing the right thing but gnome-shell is the one setting the key value on wayland and currently always claiming that desktop isn't handled. The suggestion is that gnome-shell should be updated, or maybe the desktop extension if it's technical doable for it to override the value. Reassigning to gnome- shell as a first step now. Ideally someone would report it upstream on the shell or desktop icons extension to get their opinion ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1875671 Title: wayland: desktop folder missing in sidebar Status in GTK+: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: Using Wayland session nautilus home window does not show Desktop folder in sidebar while is dispayed using X11 session. see attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 Uname: Linux 5.7.0-050700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 17:24:45 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 852)' InstallationDate: Installed on 2020-04-23 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1875671/+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 1928360] [NEW] Switch to Fcitx 5 for Chinese
Public bug reported: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. ** Affects: ubuntukylin Importance: Undecided Status: New ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntukylin Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Ubuntu Kylin: New Status in language-selector package in Ubuntu: New Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1928360/+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 1875671] [NEW] wayland: desktop folder missing in sidebar
You have been subscribed to a public bug: Using Wayland session nautilus home window does not show Desktop folder in sidebar while is dispayed using X11 session. see attachment. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 Uname: Linux 5.7.0-050700rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 17:24:45 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1059, 852)' InstallationDate: Installed on 2020-04-23 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: gtk Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug focal wayland-session -- wayland: desktop folder missing in sidebar https://bugs.launchpad.net/bugs/1875671 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928358] [NEW] gnome-shell spamming the log
Public bug reported:
I don't know what happened, but I just sat down at my machine to find it
sluggish. Digging further, I find that gnome-shell is spamming the
system log with these messages:
May 13 12:06:42 cerberus gnome-shell[3120]: JS ERROR: TypeError: null has no
properties
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
actionMoveWorkspace@resource:///org/gnome/shell/ui/windowManager.js:2170:23
_showWorkspaceSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2144:18
Restarting the shell with:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting…")'
restored it to sanity.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 13 12:07:00 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-29 (348 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-11-04 (190 days ago)
** Affects: gnome-shell (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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1928358
Title:
gnome-shell spamming the log
Status in gnome-shell package in Ubuntu:
New
Bug description:
I don't know what happened, but I just sat down at my machine to find
it sluggish. Digging further, I find that gnome-shell is spamming the
system log with these messages:
May 13 12:06:42 cerberus gnome-shell[3120]: JS ERROR: TypeError: null has no
properties
_onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
actionMoveWorkspace@resource:///org/gnome/shell/ui/windowManager.js:2170:23
_showWorkspaceSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2144:18
Restarting the shell with:
busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting…")'
restored it to sanity.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 13 12:07:00 2021
DisplayManager: gdm3
InstallationDate: Installed on 2020-05-29 (348 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-11-04 (190 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928358/+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 1926771] Re: Hard dependency on desktop-file-utils not declared
This bug was fixed in the package wslu - 3.2.3-0ubuntu2 --- wslu (3.2.3-0ubuntu2) impish; urgency=medium * debian/control: - fix a Depends syntax error in the previous changes -- Sebastien Bacher Thu, 13 May 2021 13:01:07 +0200 ** Changed in: wslu (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Bug description: Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+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 1928305] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497097/+files/LightdmLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups: android audio
[Desktop-packages] [Bug 1928305] LightdmGreeterLog.txt
apport information ** Attachment added: "LightdmGreeterLog.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497096/+files/LightdmGreeterLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups:
[Desktop-packages] [Bug 1928305] LightdmConfig.txt
apport information ** Attachment added: "LightdmConfig.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497094/+files/LightdmConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups: android
[Desktop-packages] [Bug 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter
apport information ** Tags added: apport-collected focal third-party-packages ** Description changed: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery-timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.17 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: GNOME + DistroRelease: Ubuntu 20.04 + Package: lightdm 1.30.0-0ubuntu4~20.04.1 + PackageArchitecture: amd64 + Tags: focal third-party-packages + Uname: Linux 5.4.96-050496-lowlatency x86_64 + UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) + UserGroups: android audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape users vboxusers video + _MarkForUpload: True + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + enabled=0 + mtime.conffile..etc.default.apport: 2014-03-07T13:
[Desktop-packages] [Bug 1928305] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497100/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups: android audi
[Desktop-packages] [Bug 1928305] LightdmUsersConfig.txt
apport information ** Attachment added: "LightdmUsersConfig.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497098/+files/LightdmUsersConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups
[Desktop-packages] [Bug 1928305] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497099/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups
[Desktop-packages] [Bug 1928305] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1928305/+attachment/5497095/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 PackageArchitecture: amd64 Tags: focal third-party-packages Uname: Linux 5.4.96-050496-lowlatency x86_64 UpgradeStatus: Upgraded to focal on 2021-02-10 (92 days ago) UserGroups:
[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1927149] Re: Irrelevant translatable strings
** Bug watch added: github.com/ximion/appstream/issues #315 https://github.com/ximion/appstream/issues/315 ** Also affects: appstream via https://github.com/ximion/appstream/issues/315 Importance: Unknown Status: Unknown -- 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/1927149 Title: Irrelevant translatable strings Status in AppStream: Unknown Status in snap-store-desktop: New Status in gnome-software package in Ubuntu: Fix Committed Bug description: When building gnome-software on Ubuntu, dh_translations generates a translation template (.pot file) to be imported to Rosetta. That template includes 700+ log messages from data/appdata/org.gnome.Software.appdata.xml.in. The messages are not shown to users, and it makes no sense to have those strings translated. It's worth mentioning that the strings are excluded in upstream's translation template. The issue was first reported at the ubuntu-translators mailing list: https://lists.ubuntu.com/archives/ubuntu-translators/2021-May/007757.html I stripped the redundant strings from the template and uploaded it to hirsute manually as a temporary measure. The reason why this happens seems to be that the appstream package is included in Build-Depends. appstream installs the file /usr/share/gettext/its/metainfo.its with rules which make all the log entries be extracted. But the gettext package installs /usr/share/gettext-0.21/its/metainfo.its with more sensible rules which do not make the log entries be extracted. If the former is not present, xgettext falls back to the latter. So a solution to this issue is to drop appstream from Build-Depends. gnome-software seems to build fine without that package (tested in PPA). To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1927149/+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 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
OK, if you think that Wayland is responsible for the but, then: 1: this but must be upstreamed to the developers of the Wayland protocol 2: and this bug is also a bug of the "21.04 release as a whole", since it is a bug that it makes this buggy Wayland as default. I understand that this bug reporting system is package oriented, ... ok, then the base package of "21.04 release as a whole" which defines what packages belong to the release and what are the default settings HAS this bug. -- 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/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+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 1920730] Re: gstoraster: Ghostscript runs to long while converting djvu files to Xerox`s 3210 format
Valentyna, and anyone else affected, could you attach a sample djvu file
and also instructions how you print the djvu file, so that we can
reproduce the problem and perhaps improve the patch somewhat? This is
especially important as we want to carry on the CUPS filters when CUPS
will not use PPD files any more.
As the Ghostscript call you are modifying does not more than counting
the pages (there is another one for the actual rasterization) could you
also try to modify the patch by not calling cupsRasterInterpretPPD() for
extracting the default page size from the PPD and instead, simply insert
arbitrary height and width, like "-dDEVICEWIDTHPOINTS=612
-dDEVICEHEIGHTPOINTS=792"? This would allow you to remove the "if (ppd)"
and so your fix would also work for using the filter without PPD.
Could you try this out? Do you still get fast execution and correct page
counts (= filter outputs all pages)?
** Changed in: cups-filters (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1920730
Title:
gstoraster: Ghostscript runs to long while converting djvu files to
Xerox`s 3210 format
Status in cups-filters package in Ubuntu:
Incomplete
Bug description:
My OS:
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Package version: cups-filters version 1.27.4-1
When I try to print djvu files on my Xerox WorkCentre 3210 gstoraster filter,
which calls ghostscript inside runs to long while converting djvu files to
Xerox`s 3210 format.
E.x.: For 155 pages of djvu files, it runs more then 15 minutes.
I found a solution by adding -dDEVICEWIDTHPOINTS -dDEVICEHEIGHTPOINTS params
to ghostscript command inside gstoraster filter. Now the time of converting the
same file is about 30 seconds.
I`ve made patch which solves this problem.
--- a/filter/gstoraster.c
+++ b/filter/gstoraster.c
@@ -733,8 +733,17 @@
char output[31] = "";
int pagecount;
size_t bytes;
-snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH -sDEVICE=bbox %s
2>&1 | grep -c HiResBoundingBox",
- CUPS_GHOSTSCRIPT, filename);
+// Ghostscript runs to long while converting djvu files to Xerox`s 3210
format
+// Using -dDEVICEWIDTHPOINTS -dDEVICEHEIGHTPOINTS params solves the
problem
+if (ppd) {
+ cupsRasterInterpretPPD(&h,ppd,num_options,options,0);
+ snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH
-dDEVICEWIDTHPOINTS=%d -dDEVICEHEIGHTPOINTS=%d -sDEVICE=bbox %s 2>&1 | grep -c
HiResBoundingBox",
+ CUPS_GHOSTSCRIPT, h.PageSize[0], h.PageSize[1], filename);
+}
+else {
+ snprintf(gscommand, 65536, "%s -q -dNOPAUSE -dBATCH -sDEVICE=bbox %s
2>&1 | grep -c HiResBoundingBox",
+ CUPS_GHOSTSCRIPT, filename);
+}
FILE *pd = popen(gscommand, "r");
if (!pd) {
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920730/+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 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
"Although dragging could be done by relative movements. Setting an absolute position does appear to be impossible in Wayland." If it was really impossibble, then how the Gnome shell or any window manager can position *itself*? We see, that the diverse components of the diverse window managers does not float around in an uncontrolled way, but *somehow* they are able to tell to Wayland where to position that components. The gnome-terminal should be able to do the same, either directly ask Wayland, or indirectly ask the window manager, in return of the --geometry argument. Hence it is confirmed, that the problem in question is 1: either a severe bug of the windows manager itself 2: or a severe bug of the applications receiving the --geometry arguments. I am extremly upset of keeping this bug report on the level of "opinion". There are so uncomfortable problems around the terminal windowing since 21.04, https://bugs.launchpad.net/ubuntu/+bug/1925823 https://bugs.launchpad.net/ubuntu/+bug/1928317 https://bugs.launchpad.net/ubuntu/+bug/1916890 https://bugs.launchpad.net/ubuntu/+bug/1888098 https://bugs.launchpad.net/ubuntu/+bug/1288655 or the too thick capture bar of a terminal wastes the vertical space that I seriousely consieder to change to other distro. My work depends heavily on the comfort of character terminals I became used to in the late 80's, and since 21.04 the level of comfort reached a treshold of pain. And now, I can not achieve that this serious bug is taken seriously. This bug crosses the basics of the windowing standars hold already for decades. Perhaps one of the iconic feature of a windowing system is that an application can position the other windows. This was possibble already in the mid 80's! I simply do not understand what is going here around the Wayland, while on the other hand it seems to be a very promising progress in the technology of the windowing system. But why it is a so big issue to position a window by an other application? -- 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/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+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 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
I have installed the new version and the problem is gone. No issues spotted so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+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 1927305] Re: google acount login not working, get stuck at loading screen
Thank you for your bug report, could start this n a command prompt $ journalctl -f then trigger the issue and copy any output printed? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** 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/1927305 Title: google acount login not working, get stuck at loading screen Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Every time I try to log in to my Google account in settings, after entering the details and clicking allow button settings get stuck and it did not even get closed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 6 10:18:59 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2020-11-16 (170 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-11-21 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1927305/+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 1928206] Re: File rename selection and single click do not work uniformly across the Files application
Thank you for your bug report, the desktop is handled by another component so reassigning. The rename selection had been reported upstream as https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/issues/72 and marked as fixed so maybe something changed. ** Package changed: nautilus (Ubuntu) => gnome-shell-extension-desktop- icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues #72 https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/issues/72 -- 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/1928206 Title: File rename selection and single click do not work uniformly across the Files application Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: This is on Ubuntu 20.10 Groovy Gorilla. Problem1: If I open Files (the Nautilus equivalent) and select a file and press F2 or right click and select "rename", I'm given the option of renaming the file. If the filename is someFile.txt, the "someFile" portion is highlighted automatically, so when I start renaming it, the ".txt" portion remains unaffected. This is the normal and expected behaviour. However, when I do the same thing directly on the Desktop for any file on the Desktop, the entire "someName.txt" gets highlighted, and the full name isn't even shown at first glance. The attachments show details. Problem2: In Files preferences > Behaviour > Open Action, if I select "Single click to open items", it works fine everywhere except for files on the Desktop, where I have to double click a file to open it. So the bug here is that there seems to be some inconsistency in the behaviour of files on the Desktop vs. the files that are opened in the Files window. If any of the Desktop files are opened in Files, it works fine. The problem happens only when performing these actions directly on files that are on the Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1928206/+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 1928263] Re: Files 3.38.2 doesn't show Desktop icon in sidebar
*** This bug is a duplicate of bug 1875671 *** https://bugs.launchpad.net/bugs/1875671 Thank you for your bug report, it was already reported as bug #1875671 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Confirmed ** This bug has been marked a duplicate of bug 1875671 wayland: desktop folder missing in sidebar -- 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/1928263 Title: Files 3.38.2 doesn't show Desktop icon in sidebar Status in nautilus package in Ubuntu: Confirmed Bug description: ## Environment Description: Ubuntu 21.04 Release: 21.04 Package: nautilus 1:3.38.2- ## What you expected to happen Files must show 'Desktop' folder icon in the sidebar pane. ## What happened instead 'Desktop' folder icon doesn't appear in the sidebar. ## Other info My .config/user-dirs.dirs: # This file is written by xdg-user-dirs-update # If you want to change or add directories, just edit the line you're # interested in. All local changes will be retained on the next run. # Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped # homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an # absolute path. No other format is supported. # XDG_DESKTOP_DIR="$HOME/Desktop" XDG_DOWNLOAD_DIR="$HOME/Downloads" XDG_TEMPLATES_DIR="$HOME/Templates" XDG_PUBLICSHARE_DIR="$HOME/Public" XDG_DOCUMENTS_DIR="$HOME/Documents" XDG_MUSIC_DIR="$HOME/Music" XDG_PICTURES_DIR="$HOME/Pictures" XDG_VIDEOS_DIR="$HOME/Videos" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928263/+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 1928305] Re: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1928305 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1928305/+subscriptions -- Ma
[Desktop-packages] [Bug 1882143]
Bjoern Michaelsen committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/b129ce4426d460963ace6c9e69c4b44e2a3615c2 tdf#141307: adapt null-check It will be available in 7.1.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/1882143 Title: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/caec6eae4d3f44d6d42c65c3f1a882a3d15ce34e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1882143/+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 1882143]
Bjoern Michaelsen committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b0ae5fd236663f7e81af06a567ade8a2a745 tdf#141307: adapt null-check It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- 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/1882143 Title: /usr/lib/libreoffice/program/soffice.bin:11:SvtBroadcaster::Add:SvtListener::StartListening:SwAccessibleNoTextFrame::SwAccessibleNoTextFrame:SwAccessibleGraphic::SwAccessibleGraphic:SwAccessibleMap::GetContext Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libreoffice. This problem was most recently seen with package version 1:6.4.3-0ubuntu0.20.04.1, the problem page at https://errors.ubuntu.com/problem/caec6eae4d3f44d6d42c65c3f1a882a3d15ce34e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1882143/+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 1928312] [NEW] ghost compose window with wayland
Public bug reported: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgrading to Ubuntu 21.04 and using wayland by default. It doesn't happen 100% of the time, but often enough for me to be able to collect additional information if necessary. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-lowlatency 5.11.12 Uname: Linux 5.11.0-17-lowlatency x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: martin26115 F pulseaudio /dev/snd/controlC1: martin26115 F pulseaudio /dev/snd/controlC0: martin26115 F pulseaudio BuildID: 20210304234616 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:42:39 2021 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:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-04-27 ( days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.8.1/20210304234616 (In use) Profile0 (Default) - LastVersion=78.8.1/20210304234616 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to hirsute on 2021-04-25 (17 days ago) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.21 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET50WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DF004NGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrJ5ET50WW(1.21):bd11/20/2015:br1.21:efr1.21:svnLENOVO:pn20DF004NGE:pvrThinkPadE550:rvnLENOVO:rn20DF004NGE:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E550 dmi.product.name: 20DF004NGE dmi.product.sku: LENOVO_MT_20DF_BU_Think_FM_ThinkPad E550 dmi.product.version: ThinkPad E550 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1928312 Title: ghost compose window with wayland Status in thunderbird package in Ubuntu: New Bug description: After writing a new email and sending it, gnome still sees the compose window, even though it is really closed. * Ubuntu Dock has an additional dot next to the thunderbird logo * Clicking in the top bar on Thunderbird has the compose window listed under "Open windows" * Using get_windows() in looking glass on the thunderbird app object gets 2 objects of MetaWindowWayland Even after closing the main window of thunderbird, the ghost window is still there (dot next to thunderbird logo in ubuntu dock), which means Ubuntu Dock is not launching thunderbird on single left click any more. Right click on the thunderbird logo in this state just opens an action window which doesn't respond to any clicks. Only logging out and back in seems to restore normal behavior. This is happening since upgradin
[Desktop-packages] [Bug 1925822] Re: [21.04 regression] formatting vfat times out
@Łukasz we started working on merges, that one will probably land in
impish next week at this point and we will include the SRU changes. I
could try to find time today though if that's a prerequire to validate
the SRU
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Title:
[21.04 regression] formatting vfat times out
Status in udisks2 package in Ubuntu:
Fix Committed
Status in udisks2 source package in Hirsute:
Fix Committed
Bug description:
* Impact
Formatting devices to vfat fails in some cases due to an
incompatibility with the new dosfstools version
* Test case
see comment #5
or
- $ sudo modprobe scsi_debug
- check what device is assigned
- $ sudo busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/DEVNAME org.freedesktop.UDisks2.Block
Format 'sa{sv}' vfat 0
(replace DEVNAME by the actual device name, 'sdc' for example)
the formatting should work which you can verify by
- $ blkid -p /dev/DEVNAME
* Regression potential
The changes is specific to vfat handling so that's the feature to
focus on while testing, make sure than creating, deleting, renaming
vfat partitions from gnome-disks is working.
[racb] An upstream "precautionary" partprobe is being added following
the mkfs for vfat, when it didn't do this before. This is a change in
behaviour that might expose a problem elsewhere.
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' vfat 0
(long pause)
Call failed: Error synchronizing after formatting with type `vfat': Timed out
waiting for object
# blkid -p /dev/sda
/dev/sda: PTUUID="3690494f" PTTYPE="dos"
OTOH, formatting as ext4 works fine:
# wipefs -a /dev/sda; wipefs -a /dev/sda
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' ext4 0
(immediately succeeds)
# blkid -p /dev/sda
/dev/sda: UUID="8bea7475-6af5-4835-86d0-0e5b2cb5500e" VERSION="1.0"
BLOCK_SIZE="4096" TYPE="ext4" USAGE="filesystem"
I tested this to a QEMU emulated disk, but it reproduces equally well
against a `modprobe scsi_debug` device.
Package: udisks2 2.9.2-1
DistroRelease: Ubuntu 21.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1925822/+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 1920190] Re: Printing to ipp printer uses multiple GB of ram. pdftoraster and/or filter chain selection at fault?
Tested this command on an another system and still got about 100s runtime. /usr/bin/time -v /usr/lib/cups/filter/pdftoraster 99 manu sometitle 1 'PageSize=A4 output-format=apple-raster Resolution=600dpi' testdoc/test12.pdf > pdftorast.out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1920190 Title: Printing to ipp printer uses multiple GB of ram. pdftoraster and/or filter chain selection at fault? Status in cups-filters package in Ubuntu: Confirmed Bug description: I have an ipp/AirPrint capable printer (Brother MFC L2710DW) which automatically got added by Ubuntu (I'm on XUbuntu). Printing larger documents will easily use multiple gigabytes of ram. If the document is large enough this makes printing impossible or _very_ slow, as the process either gets killed or starts swapping. By watching htop and /proc/$pid/exe I was able to determine that the filter at fault seems to be /usr/lib/cups/filter/pdftoraster. Indeed, manually calling pdftoraster with similar arguments as passed by cups (taken from /proc/$pid/cmdline) I can observe the same memory use behaviour. Memory used seems to be linear in the number of pages and will reach around 7GB for a 48 page test-document. I am not sure if the resolution should be to fix the memory usage of pdftoraster or to make cups select a different filter chain. I describe below how I first tried to debug the issue with the help of the Debian wiki on cupsfilter and wasn't able to get the same behaviour because cupsfilter would select a different filter chain (involving gstoraster instead of pdftoraster). For my current situation it would also be nice to know if there's some way for me to work around the issue until it's fixed by printing via the filter chain selected by cupsfilter. Should adding the printer manually via the xfce interface or the cups webinterface work? Please let me know if you need more information. ## Further info: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy cups-filters cups-filters: Installed: 1.27.4-1 Candidate: 1.27.4-1 Version table: *** 1.27.4-1 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status In the system print settings the printer has the device URI "implicitclass://Brother_MFC_L2710DW_series/". From watching htop I get the impression that somewhere along the way that changes to "ipp://Brother%20MFC-L2710DW%20series._ipp._tcp.local/" (that's the argv[0] of the offending process, the binary for which is /usr/lib/cups/filter/pdftoraster). I am attaching test pdfs which exhibit the described memory use when used with pdftoraster like this: /usr/bin/time -v /usr/lib/cups/filter/pdftoraster 99 manu sometitle 1 'PageSize=A4 output-format=apple-raster Resolution=600dpi' testdoc/test48.pdf > pdftorast.out The memory use and timings I get are in memory_use.txt. Information about the processes involved and their arguments when printing is in watching_printing.txt. ## Trying to debug with cupsfilter: I also tried to reproduce the issue by following the steps on the debian wiki about cupsfilter: https://wiki.debian.org/CUPSFilter Interestingly, I could not get cupsfilter to select the same filter chain. I am not sure which ppd I should be using, though. I tried with /etc/cups/ppd/Brother_MFC_L2710DW_series.ppd and with a ppd generated by driverless cat 'ipp://Brother%20MFC-L2710DW%20series._ipp._tcp.local/' The former only outputs pdf: $ /usr/sbin/cupsfilter -p Brother_MFC_L2710DW_series.ppd -m printer/foo -o number-up=2 testdoc/test96.pdf -e --list-filters pdftopdf The latter uses gstoraster: $ /usr/sbin/cupsfilter -p driverless.ppd -m printer/foo -o number-up=2 testdoc/test96.pdf -e --list-filters pdftopdf gstoraster rastertopwg Running either without the --list-filters option finishes reasonably fast and doesn't use excessive ram. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+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 1922216] Update Released
The verification of the Stable Release Update for evince has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1922216 Title: SRU the current 3.36.10 stable update Status in evince package in Ubuntu: Fix Released Status in evince source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including a theme fix and some translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the viewer to display documents, pdf mostly but also dvi, ps and other supported types. Ensure that annotations and still loaded and that it's possible to add new ones, that searching for text and selecting is also working. * Regression potential The update has fixes around display scaling on x11 so verify that the rendering is still correct there while unscaled and with scaling enabled. There is also a change impacting fonts on dvi document so we should test several of those to ensure there is no unwanted side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922216/+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 1922216] Re: SRU the current 3.36.10 stable update
This bug was fixed in the package evince - 3.36.10-0ubuntu1 --- evince (3.36.10-0ubuntu1) focal; urgency=medium * New stable version (lp: #1922216) -- Sebastien Bacher Thu, 01 Apr 2021 11:35:10 +0200 ** Changed in: evince (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1922216 Title: SRU the current 3.36.10 stable update Status in evince package in Ubuntu: Fix Released Status in evince source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including a theme fix and some translation updates https://gitlab.gnome.org/GNOME/evince/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the viewer to display documents, pdf mostly but also dvi, ps and other supported types. Ensure that annotations and still loaded and that it's possible to add new ones, that searching for text and selecting is also working. * Regression potential The update has fixes around display scaling on x11 so verify that the rendering is still correct there while unscaled and with scaling enabled. There is also a change impacting fonts on dvi document so we should test several of those to ensure there is no unwanted side effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922216/+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 1928305] [NEW] Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter
Public bug reported: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery-timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power gives the output: root@supercat:/home/supercat# sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power No protocol specified org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend' org.gnome.settings-daemon.plugins.power time-critical 300 org.gnome.settings-daemon.plugins.power power-button-action 'suspend' org.gnome.settings-daemon.plugins.power lid-close-suspend-with-external-monitor false org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate' org.gnome.settings-daemon.plugins.power idle-dim true org.gnome.settings-daemon.plugins.power button-power 'suspend' org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend' org.gnome.settings-daemon.plugins.power priority 0 org.gnome.settings-daemon.plugins.power idle-brightness 30 org.gnome.settings-daemon.plugins.power active true org.gnome.settings-daemon.plugins.power critical-battery-action 'hibernate' org.gnome.settings-daemon.plugins.power button-suspend 'suspend' org.gnome.settings-daemon.plugins.power button-sleep 'hibernate' org.gnome.settings-daemon.plugins.power percentage-critical 3 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power ambient-enabled true org.gnome.settings-daemon.plugins.power notify-perhaps-recall true org.gnome.settings-daemon.plugins.power percentage-low 10 org.gnome.settings-daemon.plugins.power percentage-action 2 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power time-low 1200 org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0 org.gnome.settings-daemon.plugins.power time-action 120 org.gnome.settings-daemon.plugins.power use-time-for-policy true 3. I checked the result, the system still suspends (goes into sleep mode) in 20 minutes. I checked the IdleAction parameter in /etc/systemd/logind.conf, because it may affect the suspend mode. It is set to ignore. # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. # # Entries in this file show the compile time defaults. # You can change settings by editing this file. # Defaults can be restored by simply deleting this file. # # See logind.conf(5) for details. [Login] #NAutoVTs=6 #ReserveVT=6 #KillUserProcesses=no #KillOnlyUsers= #KillExcludeUsers=root #InhibitDelayMaxSec=5 #HandlePowerKey=poweroff #HandleSuspendKey=suspend #HandleHibernateKey=hibernate #HandleLidSwitch=suspend #HandleLidSwitchExternalPower=suspend #HandleLidSwitchDocked=ignore #PowerKeyIgnoreInhibited=no #SuspendKeyIgnoreInhibited=no #HibernateKeyIgnoreInhibited=no #LidSwitchIgnoreInhibited=yes #HoldoffTimeoutSec=30s IdleAction=ignore IdleActionSec=30min #RuntimeDirectorySize=10% #RemoveIPC=yes #InhibitorsMax=8192 #SessionsMax=8192 I came to conclusion that lightdm ignores correctly given setting for not suspending the system (org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0). Commentaries on this finding are welcome. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: lightdm sleep suspend -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1928305 Title: Lightdm ignores power saving settings; suspends system in 20 minutes regardless of sleep-inactive-ac-timeout parameter Status in lightdm package in Ubuntu: New Bug description: Dear colleagues, We have discovered an abnormal operation of the lightdm (1.30.0-0ubuntu4~20.04.1) program. 1. When no user is logged in (the initial user selection screen is displayed) the idle system goes into suspend (sleep) mode. The timeout for this event is 20 minutes. 2. I tried to cancel the entering into sleep mode. To do this, I altered the sleep-inactive-ac-timeout and sleep-inactive-battery- timeout parameters to 0. The command sudo -H -u lightdm dbus-launch --exit-with-session gsettings list-recursively org.gnome.settings-daemon.plugins.power
[Desktop-packages] [Bug 1928206] Re: File rename selection and single click do not work uniformly across the Files application
** Tags added: groovy ** Package changed: ubuntu => nautilus (Ubuntu) -- 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/1928206 Title: File rename selection and single click do not work uniformly across the Files application Status in nautilus package in Ubuntu: New Bug description: This is on Ubuntu 20.10 Groovy Gorilla. Problem1: If I open Files (the Nautilus equivalent) and select a file and press F2 or right click and select "rename", I'm given the option of renaming the file. If the filename is someFile.txt, the "someFile" portion is highlighted automatically, so when I start renaming it, the ".txt" portion remains unaffected. This is the normal and expected behaviour. However, when I do the same thing directly on the Desktop for any file on the Desktop, the entire "someName.txt" gets highlighted, and the full name isn't even shown at first glance. The attachments show details. Problem2: In Files preferences > Behaviour > Open Action, if I select "Single click to open items", it works fine everywhere except for files on the Desktop, where I have to double click a file to open it. So the bug here is that there seems to be some inconsistency in the behaviour of files on the Desktop vs. the files that are opened in the Files window. If any of the Desktop files are opened in Files, it works fine. The problem happens only when performing these actions directly on files that are on the Desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1928206/+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 1928206] [NEW] File rename selection and single click do not work uniformly across the Files application
You have been subscribed to a public bug: This is on Ubuntu 20.10 Groovy Gorilla. Problem1: If I open Files (the Nautilus equivalent) and select a file and press F2 or right click and select "rename", I'm given the option of renaming the file. If the filename is someFile.txt, the "someFile" portion is highlighted automatically, so when I start renaming it, the ".txt" portion remains unaffected. This is the normal and expected behaviour. However, when I do the same thing directly on the Desktop for any file on the Desktop, the entire "someName.txt" gets highlighted, and the full name isn't even shown at first glance. The attachments show details. Problem2: In Files preferences > Behaviour > Open Action, if I select "Single click to open items", it works fine everywhere except for files on the Desktop, where I have to double click a file to open it. So the bug here is that there seems to be some inconsistency in the behaviour of files on the Desktop vs. the files that are opened in the Files window. If any of the Desktop files are opened in Files, it works fine. The problem happens only when performing these actions directly on files that are on the Desktop. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment groovy -- File rename selection and single click do not work uniformly across the Files application https://bugs.launchpad.net/bugs/1928206 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus 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 1925822] Re: [21.04 regression] formatting vfat times out
What about impish? I know this fix is upstream and will eventually get
released, but do we know when? I would at least like to know that before
proceeding with the release of this into hirsute-updates.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Title:
[21.04 regression] formatting vfat times out
Status in udisks2 package in Ubuntu:
Fix Committed
Status in udisks2 source package in Hirsute:
Fix Committed
Bug description:
* Impact
Formatting devices to vfat fails in some cases due to an
incompatibility with the new dosfstools version
* Test case
see comment #5
or
- $ sudo modprobe scsi_debug
- check what device is assigned
- $ sudo busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/DEVNAME org.freedesktop.UDisks2.Block
Format 'sa{sv}' vfat 0
(replace DEVNAME by the actual device name, 'sdc' for example)
the formatting should work which you can verify by
- $ blkid -p /dev/DEVNAME
* Regression potential
The changes is specific to vfat handling so that's the feature to
focus on while testing, make sure than creating, deleting, renaming
vfat partitions from gnome-disks is working.
[racb] An upstream "precautionary" partprobe is being added following
the mkfs for vfat, when it didn't do this before. This is a change in
behaviour that might expose a problem elsewhere.
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' vfat 0
(long pause)
Call failed: Error synchronizing after formatting with type `vfat': Timed out
waiting for object
# blkid -p /dev/sda
/dev/sda: PTUUID="3690494f" PTTYPE="dos"
OTOH, formatting as ext4 works fine:
# wipefs -a /dev/sda; wipefs -a /dev/sda
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' ext4 0
(immediately succeeds)
# blkid -p /dev/sda
/dev/sda: UUID="8bea7475-6af5-4835-86d0-0e5b2cb5500e" VERSION="1.0"
BLOCK_SIZE="4096" TYPE="ext4" USAGE="filesystem"
I tested this to a QEMU emulated disk, but it reproduces equally well
against a `modprobe scsi_debug` device.
Package: udisks2 2.9.2-1
DistroRelease: Ubuntu 21.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1925822/+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 1928294] Re: gamma adjustment not working
Oh! I got it, Thanks a lot! -- 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/1928294 Title: gamma adjustment not working Status in xorg-server package in Ubuntu: Invalid Bug description: Used "xgamma -gamma" but it's not changing the gamma value although it's executing successfully. The gamma value is remaining the same as it's been before. The same problem is persisting with "xrandr". ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 13 10:50:09 2021 DistUpgraded: 2021-05-13 01:05:27,602 DEBUG icon theme changed, re-reading DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-17-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a01] InstallationDate: Installed on 2021-01-16 (116 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Dell Inc. Inspiron 5402 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=27db7e67-d3d7-4151-9a09-55ec9d0801fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-12 (0 days ago) dmi.bios.date: 03/30/2021 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 0NTCD9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd03/30/2021:br1.4:svnDellInc.:pnInspiron5402:pvr:rvnDellInc.:rn0NTCD9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5402 dmi.product.sku: 0A01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1928294/+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
