[Desktop-packages] [Bug 1894356] Re: could not acquire name on session bus by simultaneous login by XDMCP and keyboard
** Bug watch added: Debian Bug tracker #969564 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564 ** Also affects: lightdm (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969564 Importance: Unknown Status: Unknown -- 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/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Status in lightdm package in Debian: Unknown Bug description: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+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 1752091] Re: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
In my case, the bug apparead when I mounted an Cryptomator volume and began to navigate on it. Ubuntu 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1752091 Title: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Confirmed Bug description: I have no idea about the package to blame: gvfs/udev/kernel ? This is now logged: gvfsd-metadata[1703]: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Feb 27 14:21:10 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1752091/+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 1894356] [NEW] could not acquire name on session bus by simultaneous login by XDMCP and keyboard
Public bug reported: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 ** Affects: lightdm Importance: Undecided Status: New ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate Importance: Undecided Status: New -- 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/1894356 Title: could not acquire name on session bus by simultaneous login by XDMCP and keyboard Status in Light Display Manager: New Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Bug description: This symptom is observed with Ubuntu Mate 20.04. 1. Create /etc/lightdm/lightdm.conf.d/10-xdmcp.conf as [XDMCPServer] enabled=true and restart lightdm. 2. Login as a normal user from keyboard. 3. Login as the same user as 2 from XDMCP gives "Could not acquire name on session bus" and I cannot login from XDMCP. Without Step 2, XDMCP login succeeds. The same symptom is reported at https://github.com/neutrinolabs/xrdp/issues/1559#issuecomment-623977001 which recommends removal of "dbus-user-session" Ubuntu package. I worked around the above issue by putting "unset DBUS_SESSION_BUS_ADDRESS" in /etc/X11/Xsession.d/ The same issue is also reported at https://bugs.launchpad.net/ubuntu-mate/+bug/1769353 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1894356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746738] Re: резервное копирование не удалось
[Expired for deja-dup (Ubuntu) because there has been no activity for 60 days.] ** Changed in: deja-dup (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1746738 Title: резервное копирование не удалось Status in deja-dup package in Ubuntu: Expired Bug description: Создать резервную копию. Пишет: резервное копирование не удалось (неизвестная ошибка). "The above configuration updates the package list, downloads, and installs available upgrades every day. The local download archive is cleaned every week. On servers upgraded to newer versions of Ubuntu, depending on your responses, the file listed above may not be there. In this case, creating a new file of this name should also work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1746738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) ,
on my windows 10 ,
it report error!
Microsoft Windows [Version 10.0.19042.450]
(c) 2020 Microsoft Corporation. All rights reserved.
C:\WINDOWS\system32>logman create trace -n HID_WPP -o
%SystemRoot%\Tracing\HID_WPP.etl -nb 128 640 -bs 128
Error:
Data Collector already exists.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{E742C27D-29B1-4E4B-94EE-074D3AD72836} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman stop -n HID_WPP
Error:
Data Collector Set is not running.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{47c779cd-4efd-49d7-9b10-9f16e5c25d06} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{896f2806-9d0e-4d5f-aa25-7acdbf4eaf2c} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{07699FF6-D2C0-4323-B927-2C53442ED29B} 0x7FFF 0xFF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman update trace -n HID_WPP -p
{0107cf95-313a-473e-9078-e73cd932f2fe} 0x7FFF 0xF
The command completed successfully.
C:\WINDOWS\system32>logman start -n HID_WPP
Error:
The filename, directory name, or volume label syntax is incorrect.
C:\WINDOWS\system32>logman stop -n HID_WPP
Error:
Data Collector Set is not running.
C:\WINDOWS\system32>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Confirmed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
[Desktop-packages] [Bug 1884860] Re: How to set default applications has changed in Ubuntu 20
The proposal was merged, and will land in groovy once we upgrade to a new upstream release. ** Changed in: gnome-user-docs (Ubuntu) Status: Triaged => In Progress ** Changed in: gnome-user-docs (Ubuntu) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1884860 Title: How to set default applications has changed in Ubuntu 20 Status in gnome-user-docs package in Ubuntu: In Progress Bug description: This page: https://help.ubuntu.com/stable/ubuntu-help/net-default-browser.html.en Says to Open the Activities overview and start typing Details. That option no longer exists. I find it now on the left hand side, under "Default Applications" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1884860/+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 1894347] Re: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
** Description changed: + Try to remove just "ubuntu-wallpapers" in Synaptic. + It will mark for removal "gnome-shell", "ubuntu-desktop", "ubuntu-artwork" and 3 other packages. + It should remove only "ubuntu-wallpapers" and "ubuntu-wallpapers-bionic". + + Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! - Who made this change? Fire him!!! - --- + + + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: - b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" - b'org.gnome.shell' b'command-history' redacted by apport - b'org.gnome.shell' b'favorite-apps' redacted by apport - b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' - b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" + b'org.gnome.shell' b'command-history' redacted by apport + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: Try to remove just "ubuntu-wallpapers" in Synaptic. It will mark for removal "gnome-shell", "ubuntu-desktop", "ubuntu-artwork" and 3 other packages. It should remove only "ubuntu-wallpapers" and "ubuntu-wallpapers-bionic". Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+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 1894347] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1894347/+attachment/5407778/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+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 1894347] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1894347/+attachment/5407779/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+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 1894347] Re: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
apport information ** Tags added: apport-collected bionic third-party-packages ** Description changed: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.17 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 18.04 + EcryptfsInUse: Yes + GsettingsChanges: + b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" + b'org.gnome.shell' b'command-history' redacted by apport + b'org.gnome.shell' b'favorite-apps' redacted by apport + b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' + b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" + InstallationDate: Installed on 2016-06-30 (1527 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Package: ubuntu-wallpapers + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 + Tags: third-party-packages bionic + Uname: Linux 4.15.0-115-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1894347/+attachment/540/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['disable-force-q...@kingodz.gmail.com', 'temperature@xtranophilist', 'freon@UshakovVasilii_Github.yahoo.com', 'systemmoni...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'toolkit-accessibility' b'true' b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2016-06-30 (1527 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: ubuntu-wallpapers PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-115-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+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 1894347] Re: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
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 1894347 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. FYI: There are reasons for the *depends* rules, and the bug report is written like you're just trolling, so currently it's likely to get closed. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-wallpapers (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: Incomplete Status in ubuntu-wallpapers package in Ubuntu: Incomplete Bug description: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+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 1894347] [NEW] Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell
Public bug reported: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-wallpapers (Ubuntu) Importance: Undecided Status: New ** Tags: packaging ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1894347 Title: Can't uninstall ubuntu-wallpapers and ubuntu-wallpapers-bionic without gnome-shell Status in gnome-shell package in Ubuntu: New Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Experiments with "depends" have to stop now! I don't want to remove gnome-shell just because of wallpapers! Who made this change? Fire him!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
And for those who have the Synaptics touchpad, I've found a way to make
the touchpad almost work. You can apply the following patch which will
make kernel use hid-rmi handle the device without blacklisting hid-
mulitouch,
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index a8e3b2796be8..9984e31c8914 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -1102,6 +1102,7 @@
#define I2C_VENDOR_ID_SYNAPTICS 0x06cb
#define I2C_PRODUCT_ID_SYNAPTICS_SYNA2393 0x7a13
+#define I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28 0x7f28
#define USB_VENDOR_ID_SYNAPTICS0x06cb
#define USB_DEVICE_ID_SYNAPTICS_TP 0x0001
diff --git a/drivers/hid/hid-quirks.c b/drivers/hid/hid-quirks.c
index a65aef6a322f..a11366f6ccd8 100644
--- a/drivers/hid/hid-quirks.c
+++ b/drivers/hid/hid-quirks.c
@@ -568,6 +568,7 @@ static const struct hid_device_id hid_have_special_driver[]
= {
{ HID_USB_DEVICE(USB_VENDOR_ID_LENOVO, USB_DEVICE_ID_LENOVO_X1_COVER) },
{ HID_USB_DEVICE(USB_VENDOR_ID_RAZER, USB_DEVICE_ID_RAZER_BLADE_14) },
{ HID_USB_DEVICE(USB_VENDOR_ID_PRIMAX, USB_DEVICE_ID_PRIMAX_REZEL) },
+ { HID_I2C_DEVICE(I2C_VENDOR_ID_SYNAPTICS,
I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28) },
#endif
#if IS_ENABLED(CONFIG_HID_ROCCAT)
{ HID_USB_DEVICE(USB_VENDOR_ID_ROCCAT, USB_DEVICE_ID_ROCCAT_ARVO) },
diff --git a/drivers/hid/hid-rmi.c b/drivers/hid/hid-rmi.c
index 7f41213d5ae3..e74b54f1b0c4 100644
--- a/drivers/hid/hid-rmi.c
+++ b/drivers/hid/hid-rmi.c
@@ -759,6 +759,7 @@ static const struct hid_device_id rmi_id[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_PRIMAX, USB_DEVICE_ID_PRIMAX_REZEL) },
{ HID_USB_DEVICE(USB_VENDOR_ID_SYNAPTICS,
USB_DEVICE_ID_SYNAPTICS_ACER_SWITCH5),
.driver_data = RMI_DEVICE_OUTPUT_SET_REPORT },
+ { HID_I2C_DEVICE(I2C_VENDOR_ID_SYNAPTICS,
I2C_PRODUCT_ID_SYNAPTICS_SYNA7f28) },
{ HID_DEVICE(HID_BUS_ANY, HID_GROUP_RMI, HID_ANY_ID, HID_ANY_ID) },
{ }
};
One left issue is the single clicking is not sensitive enough. I need to
let my finger linger on the touchpad for a while (like 0.5s). I'll send
the patches upstream after fixing this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Confirmed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Stefano Galassi (iltoga) and wangjun (biggerchina) Thank you for providing the info! So this ELAN touchpad's HID reporter descriptors could be read and parsed but it couldn't be started at all since no HID reports are received. Now the only way I can think of to tackle this issue is to install Windows Driver Kit to capture HID reports to see what reports are sent/received from/by the Windows driver while playing with the touchpad under Windows? But my laptop comes with the Synnaptics touchpad, I couldn't do this on my own computer. Is it possible for you to do it for me? Here's the how-to https://techcommunity.microsoft.com/t5/microsoft-usb-blog/how-to-capture-and-read-hid-traces-in-windows-8-1/ba-p/270839. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version:
[Desktop-packages] [Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
The same issue on ASUS GL703GE, headphones doesn't work. It was working some how on Ubuntu 18.04. Now I have installed Ubuntu 20 and this headache back again. Anybody, please help. -- 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/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Built-in speakers work fine. When testing headphones in sound settings, The sound indicator bar in Pulse-Audio moves. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri May 17 12:05:57 2019 InstallationDate: Installed on 2019-05-16 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: root 8064 F pulseaudio galactic 13345 F pulseaudio /dev/snd/pcmC0D0p: galactic 13345 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD 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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
I have AMD graphics, and I'm affected by this too. Ubuntu 20.04.1 LTS AMD Ryzen 5 3500U Radeon Vega 8 -- 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/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Focal: Confirmed Bug description: See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1894338] [NEW] Earphones Volume Control doesn't work
Public bug reported: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) I have two issues with them (possibly should report a new bug for the second one?) 1) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? 2) Every time I boot or reboot my system and leave the earphones on, without unplugging them, i.e. when Ubuntu boots with the headphone plug already occupied, I don't get any sound from my headphones, no matter how much up and down I turn the volume (from my laptop sound controls), i.e. the sound bar moves up and down and I hear no sound. I have to unplug and re-plug my earphones and only then does Ubuntu recognize them and ask me to select "Headset/Headset with mic/Mic". How can I fix it, so that I don't have to replug every time I boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 02P5YY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd02/17/2020:svnDellInc.:pnInspiron7570:pvr:rvnDellInc.:rn02P5YY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7570 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1894338 Title: Earphones Volume Control doesn't work Status in pulseaudio package in Ubuntu: New Bug description: My earphones are the one coming with Samsung Galaxy S8 (here: https://www.samsung.com/us/mobile/mobile-accessories/phones/samsung- earphones-tuned-by-akg--gray-eo-ig955bsegus) and on my Ubuntu 18.04 (dual-boot with Windows 10, Secure Boot enabled) I have two issues with them (possibly should report a new bug for the second one?) 1) Trying to set the volume from my earphones' controls doesn't work, no modification on the volume, the sound bar on Ubuntu doesn't appear in order to indicate volume change. I would like to change the master volume, or whatever my common laptop controls do when I up/down the volume controls on my earphones, like it happens on Windows 10. Why does the erroneous behavior of being unable to set volume from my earphones happen? 2) Every time I boot or reboot my system and leave the earphones on, without unplugging them, i.e. when Ubuntu boots with the headphone plug already occupied, I don't get any sound from my headphones, no matter how much up and down I turn the volume (from my laptop sound controls), i.e. the sound bar moves up and down and I hear no sound. I have to unplug and re-plug my earphones and only then does Ubuntu recognize them and ask me to select "Headset/Headset with mic/Mic". How can I fix it, so that I don't have to replug every time I boot? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.10 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jason 3523 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 23:29:52 2020 InstallationDate: Installed on 2018-09-28 (706 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=el_GR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log
[Desktop-packages] [Bug 1894336] [NEW] package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia
Public bug reported: instalando driver de nvidia-340, la ultima actualización tiene problemas de resolución gráfica ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 4 20:56:57 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-05-12 (115 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1 UpgradeStatus: Upgraded to focal on 2020-05-13 (114 days ago) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1894336 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: instalando driver de nvidia-340, la ultima actualización tiene problemas de resolución gráfica ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 4 20:56:57 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1 InstallationDate: Installed on 2020-05-12 (115 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) 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.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.138-0ubuntu0.20.04.1 UpgradeStatus: Upgraded to focal on 2020-05-13 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1894336/+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 1894327] Re: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr
** Tags removed: need-duplicate-check -- 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/1894327 Title: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr/share/applications/gnome- control-center.desktop', which is the diverted version of '/tmp /fallback-settings.tmp' Status in gnome-control-center package in Ubuntu: New Bug description: Reading database ... 337678 files and directories currently installed.) Preparing to unpack .../gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb ... Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite /usr/share/applications/gnome-control-center.desktop, which is the diverted version of /tmp/fallback-settings.tmp dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 4 18:54:19 2020 DuplicateSignature: package:gnome-control-center:1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YeLaCI/189-gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' ErrorMessage: trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' InstallationDate: Installed on 2020-08-13 (22 days ago) InstallationMedia: Ubuntu Unity 20.10 "Groovy Gorilla" (20200610) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: gnome-control-center Title: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894327/+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 1894327] [NEW] package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/u
Public bug reported: Reading database ... 337678 files and directories currently installed.) Preparing to unpack .../gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb ... Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite /usr/share/applications/gnome-control-center.desktop, which is the diverted version of /tmp/fallback-settings.tmp dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 4 18:54:19 2020 DuplicateSignature: package:gnome-control-center:1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YeLaCI/189-gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' ErrorMessage: trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' InstallationDate: Installed on 2020-08-13 (22 days ago) InstallationMedia: Ubuntu Unity 20.10 "Groovy Gorilla" (20200610) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: gnome-control-center Title: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package groovy package-conflict -- 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/1894327 Title: package gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] failed to install/upgrade: trying to overwrite '/usr/share/applications/gnome- control-center.desktop', which is the diverted version of '/tmp /fallback-settings.tmp' Status in gnome-control-center package in Ubuntu: New Bug description: Reading database ... 337678 files and directories currently installed.) Preparing to unpack .../gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb ... Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite /usr/share/applications/gnome-control-center.desktop, which is the diverted version of /tmp/fallback-settings.tmp dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Sep 4 18:54:19 2020 DuplicateSignature: package:gnome-control-center:1:3.36.2-1ubuntu1 [modified: usr/share/applications/gnome-control-center.desktop] Unpacking gnome-control-center (1:3.37.90-1ubuntu2) over (1:3.36.2-1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-YeLaCI/189-gnome-control-center_1%3a3.37.90-1ubuntu2_amd64.deb (--unpack): trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' ErrorMessage: trying to overwrite '/usr/share/applications/gnome-control-center.desktop', which is the diverted version of '/tmp/fallback-settings.tmp' InstallationDate: Installed on 2020-08-13 (22 days ago)
[Desktop-packages] [Bug 1894224] Re: LO not built consistently with the same optimization flags
Thanks for the patch! I was looking at it and noticed that just a few lines from the bottom there's this: +export DEB_CFLAGS_MAINT_STRIP DEB_CXXFLAGS_MAINT_STRIP +export DEB_CFLAGS_MAINT_PREPEND DEB_CXXFLAGS_MAINT_PREPEND +export DEB_CFLAGS_MAINT_STRIP DEB_CXXFLAGS_MAINT_STRIP Is that second +export DEB_CFLAGS_MAINT_STRIP DEB_CXXFLAGS_MAINT_STRIP necessary for some reason? -- 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/1894224 Title: LO not built consistently with the same optimization flags Status in libreoffice package in Ubuntu: New Bug description: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg- buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.
All GTK programs are broken. Same message: x@warp:~$ export LANG="ru_RU.UTF-8"; leafpad (leafpad:18666): dbind-WARNING **: 23:43:20.266: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Geany, Leafpad, Gedit and Opera save file dialogs don't allow Russian language input. Qt programs works fine. Launching with sudo fix problem: x@warp:~$ sudo leafpad (leafpad:28016): GLib-GIO-CRITICAL **: 00:27:57.489: g_dbus_proxy_new: assertion 'G_IS_DBUS_CONNECTION (connection)' failed Dbus is running. x@warp:~$ echo $DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus x@warp:~$ echo $DBUS_SESSION_BUS_PID (empty string) This happen after upgrade from 16.04.6 to 18.04.5 . Kernel 5.4.0-42-generic. I have old kernels and can test with it. PC on MSI P67S motherboard, no suspends, just XscreenSaver. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1222356 Title: WARNING: Couldn't register with accessibility bus: Did not receive a reply. Status in at-spi2-core package in Ubuntu: Fix Released Status in at-spi2-core package in Debian: Fix Released Bug description: The following warnings/errors appear after calling ubuntu-bug ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport-gtk 2.12.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Sun Sep 8 10:54:01 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-01 (371 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1712698] Re: Uninstalling Dash To Dock does not restore Ubuntu Dock
I don't know why this bug is marked as fixed, because it has just happened to me. Ubuntu 18.04 Gnome 3.28.2 The workaround mentioned, to reset the entire dconf settings, is not a good idea for me, having made a number of personalisations there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1712698 Title: Uninstalling Dash To Dock does not restore Ubuntu Dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: Using 17.10 daily. Installed Dash To Dock to test settings compatibility etc... Finished testing. Uninstalled Dash To Dock. Expected Ubuntu Dock to reappear. It did not, even after a shell restart and log out/in. I was able to get it back by reinstalling and disabling Dash To Dock. Ubuntu Dock folder still exists in the system extension folder, but it's desktop appearance seems now permanently dependent on Dash To Dock's installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712698/+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 1894216] Re: [snap] chromium launch script forces own start-url when it shouldnt (headless mode)
Fixed with https://git.launchpad.net/~chromium-team/chromium- browser/+git/snap-from- source/commit/?id=8327b5df24a2676d71938c066e48b62b35f25c3b. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894216 Title: [snap] chromium launch script forces own start-url when it shouldnt (headless mode) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894216/+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 1894216] Re: [snap] chromium launch script forces own start-url when it shouldnt (headless mode)
Thanks miccs, the above commit is largely inspired by your patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894216 Title: [snap] chromium launch script forces own start-url when it shouldnt (headless mode) Status in chromium-browser package in Ubuntu: Fix Committed Bug description: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894216/+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 1894224] Re: LO not built consistently with the same optimization flags
** Tags added: patch -- 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/1894224 Title: LO not built consistently with the same optimization flags Status in libreoffice package in Ubuntu: New Bug description: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg- buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+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 1894156] Re: Selection of multiple files in icon view
great, closing the bug then, it's an hidden experimental flag which is deprecated and should probably be removed but that's a topic to discussion rather ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Invalid Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] Re: Selection of multiple files in icon view
It worked! Thank you Sebastien! -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 844582] Re: "Invalid argument" when trying to scan
Please start gscan2pdf from the command line with the --log=log option,
try to scan, quit, and post the log file, which gscan2pdf should have
compressed to log.xz for you.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/844582
Title:
"Invalid argument" when trying to scan
Status in gscan2pdf package in Ubuntu:
Invalid
Status in sane-backends package in Ubuntu:
Opinion
Bug description:
I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
it works more or less well with Ubuntu.
I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
another scanner.
All I get is a meaningless "Invalid argument" when I hit the scan
button.
When I start gscan2pdf from the command line I see these lines
appearing when I hit the scan button:
Error running process: Died at (eval 39) line 7.
$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
$device->cancel;
$shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gscan2pdf 0.9.31-2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Sep 8 09:44:25 2011
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gscan2pdf
UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+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 1894156] Re: Selection of multiple files in icon view
the issue is probably due to b'org.gnome.nautilus.preferences' b'use-experimental-views' b'true' could you try to reset that key to the default value (false) and see if that makes a difference? -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] Re: Selection of multiple files in icon view
I added a guest user to make a test and could select multiple files in the "icon view". The problem is only with my user. I don't know how to solve this. Thanks! -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894222] Re: undefined reference when building with -O1 on armhf
Can you please provide your full command used besides the paramaeters in question? It takes some of the guessing out of the task :) -- 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/1894222 Title: undefined reference when building with -O1 on armhf Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O1 everywhere /usr/bin/ld: /home/ubuntu/lo/libreoffice-7.0.1~rc1/workdir/CxxObject/sw/source/ui/config/mailconfigpage.o: in function `com::sun::star::uno::Reference::Reference(com::sun::star::mail::XConnectionListener*)': ././include/com/sun/star/uno/Reference.hxx:154: undefined reference to `non-virtual thunk to cppu::PartialWeakComponentImplHelper::acquire()' collect2: error: ld returned 1 exit status make[2]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/sw/Library_swui.mk:20: /home/ubuntu/lo/libreoffice-7.0.1~rc1/instdir/program/libswuilo.so] Error 1 make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [Makefile:274: build] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1935: debian/stampdir/build-arch] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894222/+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 1893567] Re: Login name ellipsis/dot-dot-dot in GDM
I just noticed that, inside the login screen, making text larger (using the top-right accessibility menu option) and toggling it back to its normal size, makes the ellipsis disappear. Only for that session, of course. -- 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/1893567 Title: Login name ellipsis/dot-dot-dot in GDM Status in gnome-shell package in Ubuntu: New Bug description: Recently, my Ubuntu 20.04.1 login screen started showing my username as a dot-dot-dot, with a vertical scroll, despite being my user name only four letters (i.e.: kopa). It is the only user account in the system too. I've attached a screenshot of the login screen where the issue can be seen. GDM here is version 3.34.1-1ubuntu1. I'm running Xorg (no wayland). No changes to its configuration were made. I can provide whatever extra information that could be useful in diagnosing this problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1893567/+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 1894156] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1894156/+attachment/5407663/+files/ProcEnviron.txt -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] modified.conffile..etc.xdg.autostart.nautilus-autostart.desktop.txt
apport information ** Attachment added: "modified.conffile..etc.xdg.autostart.nautilus-autostart.desktop.txt" https://bugs.launchpad.net/bugs/1894156/+attachment/5407664/+files/modified.conffile..etc.xdg.autostart.nautilus-autostart.desktop.txt -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1894156/+attachment/5407661/+files/GsettingsChanges.txt -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1894156/+attachment/5407662/+files/ProcCpuinfoMinimal.txt -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894156] Re: Selection of multiple files in icon view
apport information ** Tags added: apport-collected focal ** Description changed: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.8 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia + Package: nautilus 1:3.36.3-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers + _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: 2016-10-02T19:15:39.698161 + mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 + usr_lib_nautilus: dropbox 2020.03.04 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1894156/+attachment/5407660/+files/Dependencies.txt -- 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/1894156 Title: Selection of multiple files in icon view Status in nautilus package in Ubuntu: Incomplete Bug description: In "icon view" mode I can't select multiple files with ctrl + click. In "list view" mode it works normally. Ubuntu 20.04.1 LTS Nautilus: 1:3.36.3-0ubuntu1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 NonfreeKernelModules: lkp_Ubuntu_5_4_0_42_46_generic_70 nvidia_modeset nvidia Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers _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: 2016-10-02T19:15:39.698161 mtime.conffile..etc.xdg.autostart.nautilus-autostart.desktop: 2019-07-17T04:12:19.512964 usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1894156/+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 1894222] Re: undefined reference when building with -O1 on armhf
** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Tags added: rls-gg-incoming -- 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/1894222 Title: undefined reference when building with -O1 on armhf Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O1 everywhere /usr/bin/ld: /home/ubuntu/lo/libreoffice-7.0.1~rc1/workdir/CxxObject/sw/source/ui/config/mailconfigpage.o: in function `com::sun::star::uno::Reference::Reference(com::sun::star::mail::XConnectionListener*)': ././include/com/sun/star/uno/Reference.hxx:154: undefined reference to `non-virtual thunk to cppu::PartialWeakComponentImplHelper::acquire()' collect2: error: ld returned 1 exit status make[2]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/sw/Library_swui.mk:20: /home/ubuntu/lo/libreoffice-7.0.1~rc1/instdir/program/libswuilo.so] Error 1 make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [Makefile:274: build] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1935: debian/stampdir/build-arch] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894222/+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 1894223] Re: please have separate targets for the configure and build steps
** Tags added: rls-gg-incoming -- 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/1894223 Title: please have separate targets for the configure and build steps Status in libreoffice package in Ubuntu: New Bug description: the current debian/rules runs the configure step again, if you restart the build for debugging. Please add add separate build targets for the configure and the build step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894223/+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 1894224] Re: LO not built consistently with the same optimization flags
** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Tags added: rls-gg-incoming -- 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/1894224 Title: LO not built consistently with the same optimization flags Status in libreoffice package in Ubuntu: New Bug description: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg- buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+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 1894073] Re: Duplicity fails backups with message "SHA1 hash mismatch for file..." every single time
*** This bug is a duplicate of bug 1360734 *** https://bugs.launchpad.net/bugs/1360734 Hmm, I'm sorry this is happening! I've seen reports of duplicity giving this error before. I'll mark this bug as a duplicate of one of them. Practically, until this gets fixed, I'd say try deleting ~/.cache/deja- dup/ and if that doesn't work, maybe move the file in the error message on the backend into a different folder (or delete it, but moving it will let you still have it if you need it for some reason). ** This bug has been marked a duplicate of bug 1360734 Duplicity fails with "Invalid data - SHA1 hash mismatch for file", does not retry download. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1894073 Title: Duplicity fails backups with message "SHA1 hash mismatch for file..." every single time Status in deja-dup package in Ubuntu: New Bug description: Backup has been going on ok since some days ago. Then the backups started failing with message: Invalid data - SHA1 hash mismatch for file: duplicity-inc.20200828T014540Z.to.20200829T012824Z.vol1.difftar.gz Calculated hash: 06f2c3af5c64b989db2507d842a64e19d1cb7206 Manifest hash: 77788b1c0808968b82904e3b0f688143fbebe1d0 Without any way offered to take an action to proceed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1894073/+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 1894233] Re: LO ftbfs with -O0
** Changed in: libreoffice (Ubuntu) Importance: Undecided => High ** Tags added: rls-gg-incoming -- 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/1894233 Title: LO ftbfs with -O0 Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O0: [...] # build the tests first export gb_SUPPRESS_TESTS=true; \ /usr/bin/make check make[2]: Entering directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' /home/ubuntu/lo/libreoffice-7.0.1~rc1/config_host.mk:102: *** missing separator. Stop. make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/debian/rules:2067: check] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1951: debian/stampdir/build-arch] Error 2 and that file shows: export CPUNAME=ARM export CDEFAULTOPT=-O0 -O0 export HARDEN_CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 export CROSS_COMPILING= export CURL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894233/+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 1891623] Re: Can't build Libreoffice with gcc-10, always ends with a Segmentation Fault in the build or resulting binaries
I am opening a libreoffice task, and closing the gcc-10 task. I didn't see any ICE during my debugging work. Unfortunately the package doesn't build with other optimization options due to packaging and upstream issues. Separate issues are filed as LP: #1894233, LP: #1894224, LP: #1894223, LP: #1894222. ** Summary changed: - Can't build Libreoffice with gcc-10, always ends with a Segmentation Fault in the build or resulting binaries + LO segfaults in one test on armhf when built with GCC 10 ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Groovy) Importance: Undecided => High ** Changed in: gcc-10 (Ubuntu Groovy) Status: Incomplete => Invalid -- 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/1891623 Title: LO segfaults in one test on armhf when built with GCC 10 Status in gcc-10 package in Ubuntu: Invalid Status in libreoffice package in Ubuntu: New Status in gcc-10 source package in Groovy: Invalid Status in libreoffice source package in Groovy: New Bug description: I don't think we've had a successful build of Libreoffce on armhf in Ubuntu since gcc-10, it always eventually segfaults after 24 hours or so /<>/toolkit/source/controls/tkscrollbar.cxx: In member function ‘virtual void toolkit::UnoScrollBarControl::adjustmentValueChanged(const com::sun::star::awt::AdjustmentEvent&)’: /<>/toolkit/source/controls/tkscrollbar.cxx:175:5: internal compiler error: Segmentation fault 175 | } | ^ Please submit a full bug report, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623/+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 1894224] Re: LO not built consistently with the same optimization flags
here is what needs to be changed for armhf and -O0. That patch needs generalization ** Patch added: "opt.diff" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+attachment/5407658/+files/opt.diff -- 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/1894224 Title: LO not built consistently with the same optimization flags Status in libreoffice package in Ubuntu: New Bug description: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg- buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+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 1894216] Re: [snap] chromium launch script forces own start-url when it shouldnt (headless mode)
** Tags removed: patch ** Tags added: snap ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Medium ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894216 Title: [snap] chromium launch script forces own start-url when it shouldnt (headless mode) Status in chromium-browser package in Ubuntu: Confirmed Bug description: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894216/+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 1893579] Re: Ctrl + Alt + T and Fn keys not working
Thanks Sebastien: reverting to gnome-settings-daemon 3.36.1-1ubuntu2 (and rebooting) fixed all the hotkey issues for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1893579/+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 1894234] [NEW] Bluetooth not working with Gnome in Groovy (20.10)
Public bug reported: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! ** Affects: gnome-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth gnome groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1894234 Title: Bluetooth not working with Gnome in Groovy (20.10) Status in gnome-bluetooth package in Ubuntu: New Bug description: Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs report that I have no bluetooth adapter, and I should plug one in. At the same time, I can see the bluetooth adapter with hciconfig, and in fact, I can pair with remote bluetooth devices using a 3rd party bluetooth manager (blueman). Obviously this is not ideal, as it is not fully integrated with gnome, sound devices are not fully available etc.. I'm not sure what else I can provide, but:- # hciconfig -a hci0: Type: Primary Bus: USB BD Address: 24:4B:FE:3A:21:65 ACL MTU: 1021:6 SCO MTU: 255:12 UP RUNNING PSCAN RX bytes:1117 acl:0 sco:0 events:72 errors:0 TX bytes:4973 acl:0 sco:0 commands:72 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'morpheous' Class: 0x1c0104 Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0xb LMP Version: 5.1 (0xa) Subversion: 0x8761 Manufacturer: Realtek Semiconductor Corporation (93) root@morpheous:~# When I got to settings, it tells me I have no bluetooth devices plugged in! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1894234/+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 1894233] [NEW] LO ftbfs with -O0
Public bug reported: seen when building LO with -O0: [...] # build the tests first export gb_SUPPRESS_TESTS=true; \ /usr/bin/make check make[2]: Entering directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' /home/ubuntu/lo/libreoffice-7.0.1~rc1/config_host.mk:102: *** missing separator. Stop. make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/debian/rules:2067: check] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1951: debian/stampdir/build-arch] Error 2 and that file shows: export CPUNAME=ARM export CDEFAULTOPT=-O0 -O0 export HARDEN_CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 export CROSS_COMPILING= export CURL= ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1894233 Title: LO ftbfs with -O0 Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O0: [...] # build the tests first export gb_SUPPRESS_TESTS=true; \ /usr/bin/make check make[2]: Entering directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' /home/ubuntu/lo/libreoffice-7.0.1~rc1/config_host.mk:102: *** missing separator. Stop. make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/debian/rules:2067: check] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1951: debian/stampdir/build-arch] Error 2 and that file shows: export CPUNAME=ARM export CDEFAULTOPT=-O0 -O0 export HARDEN_CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 export CROSS_COMPILING= export CURL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894233/+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 1894225] Re: Blocked UI and 100% cpu in gnome-shell when selecting text
After looking through other processes that use CPU while selecting text, I noticed clipit there as well. Closing clipit seems to improve things a lot. I still see gnome-shell go to 25% CPU but the UI is responsive now. -- 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/1894225 Title: Blocked UI and 100% cpu in gnome-shell when selecting text Status in gnome-shell package in Ubuntu: New Bug description: After upgrading from ubuntu-18.04 to 20.04 I noticed that selecting text via shift-rightarrow in any app (gedit, chrome, firefox) makes X11 stop updating all apps' window contents while gnome-shell jumps to 100% cpu in top. This is on an idle DELL e7440 laptop (i5-4210U with 8 GB of RAM) and a fresh ubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 15:44:00 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-26 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894225/+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 1850995] Re: gnome-shell: freeze and high CPU usage
After looking through other processes that use CPU while selecting text, I noticed clipit there as well. Closing clipit seems to improve things a lot. I still see gnome-shell go to 25% CPU but the UI is responsive now. ** This bug is no longer a duplicate of bug 1850969 x11 session all mouse or keyboard action ignored -- 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/1850995 Title: gnome-shell: freeze and high CPU usage Status in gnome-shell package in Ubuntu: In Progress Bug description: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850995/+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 1893552] Re: Use im-config on Wayland without uninstalling IBus
Verified the test case using im-config 0.44-1ubuntu1.2 from focal- proposed. ** 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 im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893552 Title: Use im-config on Wayland without uninstalling IBus Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: [Impact] In a Wayland session on Ubuntu 20.04 im-config does not work as intended. To be able to use a non-IBus IM framework you basically need to first uninstall ibus (or 'fake uninstall' by renaming /usr/bin /ibus-daemon). This was fixed in im-config 0.45-1, and the proposed upload includes a patch with a cherry picked Debian commit. [Test case] * Install fcitx and fcitx-libpinyin * Open Language Support and switch to fcitx * Reboot and log in to a Wayland session * Open the fcitx preferences and add fcitx-libpinyin * Switch to fcitx-libpinyin and confirm that you can input Chinese [Regression risk] A similar method for making im-config work with Wayland was used in Ubuntu 17.10, which was shipped with Wayland as default. Since the approach has already been used without reported issues, the regression risk now should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893552/+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 1893551] Re: Let im-config back off if IBus on GNOME desktops
Verified the test case using im-config 0.44-1ubuntu1.2 from focal- proposed. ** 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 im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893551 Title: Let im-config back off if IBus on GNOME desktops Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: Note: Quite a few ibus crash bug reports have been marked as duplicates of this bug. If you find that such a bug was not actually addressed through the fix of this bug, please feel free to comment on the bug report and remove the duplicate link. [Impact] GNOME desktops have built-in mechanisms for launching and configuring IBus. However, up to now im-config has overridden GNOME in this respect, resulting in a slightly different command for launching IBus and a few extra environment variables; most importantly GTK_IM_MODULE has been set to "ibus". This was recently changed via im-config 0.45-1 in groovy, where im- config does not do anything in case of IBus on a GNOME desktop. A positive side effect of the change is that the frequency of IBus crashes has been significantly reduced. No deep analysis has been carried out which explains *how* this change prevents IBus crashes. The basis for the conclusion is instead statistics from errors.ubuntu.com. Some relevant links can be found in this discourse topic: https://discourse.ubuntu.com/t/ibus-no-more-gtk-im-module-ibus/17727 [Test case] We have not been able to reproduce the crashes, so a simple test which verifies the fix can't be accomplished. Instead we need to be attentive to possible regressions. * On an Ubuntu desktop, install ibus-libpinyin and ibus-hangul. * Log out and log in again (to an X session). * Enable Intelligent Pinyin and Hangul (from Settings -> Region & Language) * For each of Intelligent Pinyin, Hangul, and the on screen keyboard: - Confirm that inputting works without hassle - Do so on various apps: FF, TB, gedit, LO. [Regression risk] Even if we have done it differently in Ubuntu (and Debian), the GNOME mechanisms we now let replace im-config with respect to IBus is mature code which has been in use for quite some time on other distros. That speaks for a low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893551/+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 1893827] Re: autopkgtest fails in groovy
@seb128 the error seems different and 2.9.0-1ubuntu4 claimed to have fixed the other bug, so my guess was that this one is not the same -- 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/1893827 Title: autopkgtest fails in groovy Status in udisks2 package in Ubuntu: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/arm64/u/udisks2/20200901_174238_f13fc@/log.gz ... == ERROR: test_loop_ro (__main__.Manager) loop device R/O -- Traceback (most recent call last): File "src/tests/integration-test", line 642, in test_loop_ro (path, out_fd_list) = self.manager.call_loop_setup_sync( gi.repository.GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error waiting for loop object after creating '/dev/loop0': Timed out waiting for object (0) -- Ran 31 tests in 371.897s FAILED (errors=1) Testing installed system binaries daemon path: /usr/libexec/udisks2/udisksd Set up test device: r/w: /dev/sda, r/o: /dev/sr0 autopkgtest [17:42:25]: test upstream-system: ---] autopkgtest [17:42:26]: test upstream-system: - - - - - - - - - - results - - - - - - - - - - upstream-system FAIL non-zero exit status 1 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1893827/+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 1894225] [NEW] Blocked UI and 100% cpu in gnome-shell when selecting text
Public bug reported: After upgrading from ubuntu-18.04 to 20.04 I noticed that selecting text via shift-rightarrow in any app (gedit, chrome, firefox) makes X11 stop updating all apps' window contents while gnome-shell jumps to 100% cpu in top. This is on an idle DELL e7440 laptop (i5-4210U with 8 GB of RAM) and a fresh ubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 15:44:00 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-26 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "screen recording of bug reproduction" https://bugs.launchpad.net/bugs/1894225/+attachment/5407630/+files/gnome-shell-cpu-3.ogv -- 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/1894225 Title: Blocked UI and 100% cpu in gnome-shell when selecting text Status in gnome-shell package in Ubuntu: New Bug description: After upgrading from ubuntu-18.04 to 20.04 I noticed that selecting text via shift-rightarrow in any app (gedit, chrome, firefox) makes X11 stop updating all apps' window contents while gnome-shell jumps to 100% cpu in top. This is on an idle DELL e7440 laptop (i5-4210U with 8 GB of RAM) and a fresh ubuntu install. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 15:44:00 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-08-26 (9 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1894225/+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 1894222] Re: undefined reference when building with -O1 on armhf
same with -Os -- 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/1894222 Title: undefined reference when building with -O1 on armhf Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O1 everywhere /usr/bin/ld: /home/ubuntu/lo/libreoffice-7.0.1~rc1/workdir/CxxObject/sw/source/ui/config/mailconfigpage.o: in function `com::sun::star::uno::Reference::Reference(com::sun::star::mail::XConnectionListener*)': ././include/com/sun/star/uno/Reference.hxx:154: undefined reference to `non-virtual thunk to cppu::PartialWeakComponentImplHelper::acquire()' collect2: error: ld returned 1 exit status make[2]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/sw/Library_swui.mk:20: /home/ubuntu/lo/libreoffice-7.0.1~rc1/instdir/program/libswuilo.so] Error 1 make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [Makefile:274: build] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1935: debian/stampdir/build-arch] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894222/+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 1894226] [NEW] No per-pixel scrolling in version 86
Public bug reported: I just refreshed the beta snap, from version 85 to 86.0.4240.22, and now touchpad scrolling is no longer per pixel (Xinput 2 smooth scrolling?) but instead it scrolls a few lines like a mousewheel. I'm using Focal with the default GNOME desktop and X11. I have not tried Chrome or Chromium deb packages. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894226 Title: No per-pixel scrolling in version 86 Status in chromium-browser package in Ubuntu: New Bug description: I just refreshed the beta snap, from version 85 to 86.0.4240.22, and now touchpad scrolling is no longer per pixel (Xinput 2 smooth scrolling?) but instead it scrolls a few lines like a mousewheel. I'm using Focal with the default GNOME desktop and X11. I have not tried Chrome or Chromium deb packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894226/+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 1864244] Re: Text selection in address bar does not work as expected
Thank you for your bug report, it seems to work correctly in the current Ubuntu serie. Could you try if that's still an issue for you? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1864244 Title: Text selection in address bar does not work as expected Status in nautilus package in Ubuntu: Incomplete Bug description: In Nautilus, I can click "Ctrl+L" to open the address bar. At this point, the whole address will be selected, which is desirable. However, if I then press "Right" to place my cursor at the end of the current path, and then try to use "Shift+Ctrl+Left" to select word-by- word (e.g., to select and delete the final folder from the path), the whole path is again selected. It seems that the logic for preselecting the whole path upon opening the address bar seems to trigger in more circumstances than just upon opening, and this makes using Nautilus via keyboard slower and more frictive than necessary. (In general, text entry widgets that override the operating system's existing conventions always really annoy me, on desktop or mobile.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 21 15:44:24 2020 InstallationDate: Installed on 2018-12-17 (431 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LC_CTYPE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2018.11.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1864244/+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 1866250] Re: nautilus crashes under wayland when trying to unmount an external drive
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1866250 Title: nautilus crashes under wayland when trying to unmount an external drive Status in nautilus package in Ubuntu: Invalid Bug description: I can 100% reliably crash nautilus when running under a sway session. The steps to reproduce it are simple: 1. Connect an external drive and mount it by browsing to it in nautilus 2. Open a terminal and cd into the drive mount 3. Press the unmount icon for the drive in nautilus At this point nautilus 100% reliably crashes. It will not crash if the drive is not being used. Looking at the backtrace it seems it is somehow trying to do X calls when running under wayland. Here's the trace: (gdb) bt #0 0x in () #1 0x77eb3393 in g_hash_table_lookup_node (hash_return=, key=0x60, hash_table=0x561e8000) at ../../../glib/ghash.c:473 #2 0x77eb3393 in g_hash_table_lookup (hash_table=0x561e8000, key=key@entry=0x60) at ../../../glib/ghash.c:1509 #3 0x776d35b8 in lookup_cached_xatom (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:76 #4 0x776d35b8 in lookup_cached_xatom (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:67 #5 0x776d35b8 in gdk_x11_atom_to_xatom_for_display (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:109 #6 0x776d35b8 in gdk_x11_atom_to_xatom_for_display (display=0x561b1040 [GdkWaylandDisplay], atom=0x60) at ../../../../../gdk/x11/gdkproperty-x11.c:96 #7 0x77b3fc8d in _gtk_mount_operation_lookup_context_get (display=0x561b1040 [GdkWaylandDisplay]) at ../../../../gtk/gtkmountoperation-x11.c:534 #8 0x779cf800 in update_process_list_store (processes=0x569ce670, list_store=, mount_operation=) at ../../../../gtk/gtkmountoperation.c:1286 #9 0x779cf800 in gtk_mount_operation_show_processes_do_gtk (choices=0x0, processes=0x569ce670, message=0x56930a90 "", op=) at ../../../../gtk/gtkmountoperation.c:1679 #10 0x779cf800 in gtk_mount_operation_show_processes (op=, message=message@entry=0x567dfac0 "Volume is busy\nOne or more applications are keeping the volume busy.", processes=processes@entry=0x569ce670, choices=choices@entry=0x56578420) at ../../../../gtk/gtkmountoperation.c:1704 #11 0x77329b5b in _g_cclosure_marshal_VOID__STRING_BOXED_BOXEDv (closure=0x569572e0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x569e27f0) at ../../../gio/gmarshal-internal.c:2059 #12 0x7725c936 in _g_closure_invoke_va (closure=0x569572e0, return_value=0x0, instance=0x569d32d0, args=0x7fffd1f8, n_params=3, param_types=0x569e27f0) at ../../../gobject/gclosure.c:873 #13 0x7727936c in g_signal_emit_valist (instance=instance@entry=0x569d32d0, signal_id=signal_id@entry=566, detail=detail@entry=0, var_args=var_args@entry=0x7fffd1f8) at ../../../gobject/gsignal.c:3306 #14 0x77279fa9 in g_signal_emit_by_name (instance=0x569d32d0, detailed_signal=0x7fffdae3a1d2 "show-processes") at ../../../gobject/gsignal.c:3493 #15 0x7fffdae33fa8 in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so #16 0x7fffdae385a8 in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so #17 0x7616c81e in ffi_call_unix64 () at ../src/x86/unix64.S:76 #18 0x7616c1ef in ffi_call (cif=cif@entry=0x7fffd660, fn=fn@entry=0x7fffdae38530, rvalue=, avalue=avalue@entry=0x7fffd570) at ../src/x86/ffi64.c:525 Python Exception There is no member named v_pointer.: #22 0x772783ea in #23 0x7fffdae2d7e5 in () at
[Desktop-packages] [Bug 1855507] Re: Add arrow key navigation to Settings app.
The issue partially sound like https://gitlab.gnome.org/GNOME/gnome- control-center/-/issues/970 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #970 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/970 ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/970 Importance: Unknown Status: Unknown -- 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/1855507 Title: Add arrow key navigation to Settings app. Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Press up or down to select menu item on side bar. Press right to show item screen. Press up or down to select items on item screen. Press enter to change item slider setting. Press left arrow to switch back to side bar. 4) Unable to navigate settings app with arrow keys. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1855507/+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 1894224] [NEW] LO not built consistently with the same optimization flags
Public bug reported: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg-buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1894224 Title: LO not built consistently with the same optimization flags Status in libreoffice package in Ubuntu: New Bug description: looking at least at the succeeding armhf build logs, optimization flags are picked up from different places, once injected from dpkg- buidflags, and then hard-coded in solenv/gbuild/platform/LINUX__GCC.mk These really should match. Or maybe disable the settings from solenv at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894224/+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 1847738] Re: Empty item in folder context menu
The issue was reported upstream as https://gitlab.gnome.org/GNOME/nautilus/-/issues/1394 and flagged as a GTK bug ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1394 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1394 ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Triaged -- 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/1847738 Title: Empty item in folder context menu Status in gtk+3.0 package in Ubuntu: Triaged Bug description: Installed 19.10 from a daily image today (also issue on my current laptop which was upgraded from 19.04). Steps to reproduce Open nautilus Right click a file (example.desktop for example) Note the context menu looks okay Right click a folder (such as Downloads) Note the context menu has a blank entry at the bottom, beneath "Properties" Expected No blank line ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 11 11:01:25 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-10-11 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191011) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1847738/+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 1848559] Re: i couldn't access into settings and tweaks, when i clicked to them, it was setup and about 5 seconds later, they're disappeared
Thank you for your bug report. Is that still an issue in newer Ubuntu versions? If so could you do a video showing the problem? ** 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/1848559 Title: i couldn't access into settings and tweaks, when i clicked to them, it was setup and about 5 seconds later, they're disappeared Status in gnome-control-center package in Ubuntu: Incomplete Bug description: because i installed icons from gnome-look, after i choose it, everything like tweaks,settings, folder home,... they couldn't open ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-control-center 1:3.32.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 18 00:51:32 2019 InstallationDate: Installed on 2019-08-19 (59 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848559/+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 1894222] [NEW] undefined reference when building with -O1 on armhf
Public bug reported: seen when building LO with -O1 everywhere /usr/bin/ld: /home/ubuntu/lo/libreoffice-7.0.1~rc1/workdir/CxxObject/sw/source/ui/config/mailconfigpage.o: in function `com::sun::star::uno::Reference::Reference(com::sun::star::mail::XConnectionListener*)': ././include/com/sun/star/uno/Reference.hxx:154: undefined reference to `non-virtual thunk to cppu::PartialWeakComponentImplHelper::acquire()' collect2: error: ld returned 1 exit status make[2]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/sw/Library_swui.mk:20: /home/ubuntu/lo/libreoffice-7.0.1~rc1/instdir/program/libswuilo.so] Error 1 make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [Makefile:274: build] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1935: debian/stampdir/build-arch] Error 2 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1894222 Title: undefined reference when building with -O1 on armhf Status in libreoffice package in Ubuntu: New Bug description: seen when building LO with -O1 everywhere /usr/bin/ld: /home/ubuntu/lo/libreoffice-7.0.1~rc1/workdir/CxxObject/sw/source/ui/config/mailconfigpage.o: in function `com::sun::star::uno::Reference::Reference(com::sun::star::mail::XConnectionListener*)': ././include/com/sun/star/uno/Reference.hxx:154: undefined reference to `non-virtual thunk to cppu::PartialWeakComponentImplHelper::acquire()' collect2: error: ld returned 1 exit status make[2]: *** [/home/ubuntu/lo/libreoffice-7.0.1~rc1/sw/Library_swui.mk:20: /home/ubuntu/lo/libreoffice-7.0.1~rc1/instdir/program/libswuilo.so] Error 1 make[2]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make[1]: *** [Makefile:274: build] Error 2 make[1]: Leaving directory '/home/ubuntu/lo/libreoffice-7.0.1~rc1' make: *** [debian/rules:1935: debian/stampdir/build-arch] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894222/+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 1894223] [NEW] please have separate targets for the configure and build steps
Public bug reported: the current debian/rules runs the configure step again, if you restart the build for debugging. Please add add separate build targets for the configure and the build step. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1894223 Title: please have separate targets for the configure and build steps Status in libreoffice package in Ubuntu: New Bug description: the current debian/rules runs the configure step again, if you restart the build for debugging. Please add add separate build targets for the configure and the build step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1894223/+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 1835654] Re: Extracting a zip archieve creates a new unwanted folder
Thank you for your bug report. The behaviour seems a bit different, for a .xz archive it will create a folder only if there are more than 1 file to extract, is that the case of your example? The issue would be worth reporting upstream on https://gitlab.gnome.org/GNOME/file-roller/-/issues ** Changed in: file-roller (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1835654 Title: Extracting a zip archieve creates a new unwanted folder Status in file-roller package in Ubuntu: Incomplete Bug description: version of the package file-roller: 3.32.1-1 on Ubuntu 19.04 If I right click on the .zip file and choose "extract here" from the context menu, then the archieve content is extracted into a newly created folder, with the same name as the zip file. The expected behavior would be extracting the content into the folder where the archieve is located. Note this does NOT occur for tar.xz archieves, which are correctly extracted into the current folder instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1835654/+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 1838720] Re: Power button action not working
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1838720 Title: Power button action not working Status in gnome-control-center package in Ubuntu: New Bug description: In the Power tab, the option "When the power button is pressed" is set to "Suspend". However, this action is not executed on power button press. It does nothing. This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it works as expected. gnome-control-center 3.32.2 Kernel 5.0.0-23-generic Ubuntu 19.04 Disco See attached logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+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 1839442] Re: desktop icons vanish after drag'n'drop then requires a restart
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1839442 Title: desktop icons vanish after drag'n'drop then requires a restart Status in nautilus package in Ubuntu: Invalid Bug description: All of the desktop icons (and conky, etc) suddenly vanish after I drag and drop something into a desktop folder (typically dragging selected text from chrome browser, which normally creates a text file in the folder). Does not trigger the bug every time, but quite frequently. Once the bug triggers the icon area is useless and requires a system restart to restore the icons and normal functioning. This is a new XPS laptop with Ubuntu 18.04 freshly installed (and little else modified). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 01:24:33 2019 InstallationDate: Installed on 2019-03-15 (145 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1839442/+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 1894216] Re: [snap] chromium launch script forces own start-url when it shouldnt (headless mode)
The attachment "chromium.launcher.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894216 Title: [snap] chromium launch script forces own start-url when it shouldnt (headless mode) Status in chromium-browser package in Ubuntu: New Bug description: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894216/+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 1838008] Re: [snap] cursor theme isn't respected
Probably related: bug #1892085. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1838008 Title: [snap] cursor theme isn't respected Status in chromium-browser package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Fix Committed Bug description: (initially reported at https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/85) When changing the cursor theme with gnome-tweaks, I can observe that some themes aren't respected in the chromium snap. This appears to be specific to chromium, other snaps like evince or gimp use the correct cursors. Yaru and Adwaita are fine, but Redglass or Whiteglass aren't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1838008/+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 1892085] Re: Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab
It does look like a packaging bug, because the cursors are fine in chromium-browser packaged as a deb (I installed the bionic packages in a focal VM), whereas they are not the expected ones with the snap. Probably related: bug #1838008. ** Summary changed: - Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab + [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab ** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1892085 Title: [snap] Wrong cursor theme (Adwaita) for cursors set by CSS, like cursor:wait and cursor:grab Status in chromium-browser package in Ubuntu: Confirmed Bug description: 0. In an Ubuntu 20.04 live session or new installation, install the Chromium snap and Google's Chrome deb packages. 1. In both browsers, try the MDN cursor demos at https://developer.mozilla.org/en-US/docs/Web/CSS/cursor for cursor: wait and cursor: grab. (Click the "cursor: wait;" or "cursor: grab;" button, then move the mouse over the blue box on the right to see the cursor set by that CSS option.) Or any view any page that sets these cursors with CSS such as - cursor: grab - Accuweather/mapbox radar maps, e.g. https://www.accuweather.com/en/us/minneapolis/55455/minute-weather-forecast/348794 - Google Sheets, e.g. hovering over a highlighted cell's border - cursor: wait - NYT video pages while the video loads, e.g. https://www.nytimes.com/video/us/politics/10007231439/who-is-kamala-harris.html 2. Observe that in Chromium, the CSS-set wait spinner and grab hand cursors are using the Adwaita theme, instead of the Ubuntu-default Yaru theme. The correct Yaru theme cursors are used in Chrome and other apps. (Note that for the cursor:grab examples, the Adwaita grab cursor [black hand] is shown when *hovering*, but the correct Yaru cursor [white hand] is shown once you click down, since this is no longer set by cursor:grab.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892085/+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 1834508] Re: I tried to drag an image from chrome browser to files app where it already exists. Instead of asking to replace the image, the app crashed
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1834508 Title: I tried to drag an image from chrome browser to files app where it already exists. Instead of asking to replace the image, the app crashed Status in nautilus package in Ubuntu: Invalid Bug description: 1. The release of Ubuntu is Ubuntu 18.04.2 LTS 2. The package version is 1:3.26.4-0 3. I expected to ask if I want to replace the image or not. 4. What happened is that the app crashed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 4.15.0-52.56-generic 4.15.18 Uname: Linux 4.15.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 27 18:13:59 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-06-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-06-27 (0 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1834508/+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 1822439] Re: gnome-control-center bluetooth panel broken with i3
Thank you for your bug report, gnome-control-center isn't meant to be used outside of GNOME but you could still try to report the issue to the upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1822439 Title: gnome-control-center bluetooth panel broken with i3 Status in gnome-control-center package in Ubuntu: Confirmed Bug description: piro@makkuro:~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center doesn't display bluetooth adapter when run under i3: the panel only shows the text: ``` No Bluetooth Found Plug in a dongle to use Bluetooth. ``` Adapters are correctly displayed if the same user connects with gnome. Other panels work correctly in i3. Running the panel from command line, when the tab is selected, the following log is displayed: ``` piro@makkuro:~$ XDG_CURRENT_DESKTOP=ubuntu:GNOME gnome-control-center (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_unref: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed (gnome-control-center:9355): GLib-CRITICAL **: 19:44:43.226: g_variant_unref: assertion 'value != NULL' failed ``` other tabs don't display any message at critical level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1822439/+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 1892783] Re: [SRU] libreoffice 6.4.6 for focal
Hello Heather, or anyone else affected, Accepted libreoffice into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- 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/1892783 Title: [SRU] libreoffice 6.4.6 for focal Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Focal: Fix Committed Bug description: [Impact] * LibreOffice 6.4.6 is in its sixth bugfix release of the 6.4 line. Version 6.4.5 is currently in focal. For a list of fixed bugs compared to 6.4.5 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.4.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.4.5/RC2#List_of_fixed_bugs (that's a total of 106 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 106 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1892783/+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 1894216] [NEW] [snap] chromium launch script forces own start-url when it shouldnt (headless mode)
Public bug reported: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Patch added: "chromium.launcher.patch" https://bugs.launchpad.net/bugs/1894216/+attachment/5407619/+files/chromium.launcher.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894216 Title: [snap] chromium launch script forces own start-url when it shouldnt (headless mode) Status in chromium-browser package in Ubuntu: New Bug description: it is copied from : https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1893020 - the problem is "/snap/chromium/current/bin/chromium.launcher" script, to be precise these 2 lines below: exec "$SNAP/usr/lib/chromium-browser/chrome" --no-default-browser-check --no-first-run --password-store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" and "$SNAP/usr/lib/chromium-browser/chrome" --user-data-dir=$TEMP_PROFILE --no-default-browser-check --no-first-run --password- store=$PASSWORD_STORE $FLASH_OPTIONS $CHROMIUM_FLAGS "$@" "$FIRSTRUN_PAGE" when --headless options is used "$FIRSTRUN_PAGE" parameter shall never be passed here as user specify his own page here and because of that chromium gives: "[0826/093125.490825:ERROR:headless_shell.cc(174)] Open multiple tabs is only supported when remote debugging is enabled." ive patched this script in my snap directory (which is tricky) like this: copied whole folder "/snap/chromium/1284/bin" to other dir on the disk, patched script, then did "sudo mount --bind -o nodev,ro /media/data/chromsc /snap/chromium/1284/bin" and voila this works so the solution would be to check if user is passing --headless parameter and if he passes his own site - if so then dont pass "$FIRSTRUN_PAGE" parameter --- additional info regarding solution: one doesnt need to check if user adds own site because --headless mode can start without website provided, so its enough just to check if user provided --headless parameter. ive added a patch - which is tested - works perfectly fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894216/+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 1766974] Re: (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- 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/1766974 Title: (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: There are very many bugs reported recently against xorg with a commmon theme the following are just 2 examples from the various xorg logs (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied (EE) intel(0): [drm] failed to set drm interface version: Permission denied [13]. --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2018-08-16 10:03:18,003 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (757 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet nomodeset ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Renderer: Software Tags: bionic ubuntu Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (66 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Oct 22 07:25:26 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1766974/+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 1893562] Re: Second equal USB card reader not detected
Yes, in my case the serial numbers are also identical. I skimmed through the bug you link to and it seems the fix requires a non-trivial change to udev, which explains why this hasn't been fixed. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1893562 Title: Second equal USB card reader not detected Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04.5 LTS, gnome-disks 3.28.3. Two exactly equal USB card readers ( 05e3:0749 genesys logic ) are inserted, each containing a formatted SD card, each with a single partition. Both disk partitions are correctly assigned devices on insertion. Only whichever adapter is inserted first automounts (as checked by mount) and only that adapter is listed in Gnome Disks. Both partitions names are listed in the gnome Places menu. After mounting the second partition via the Places menu, still only the first adapter is listed in Gnome Disks. The error occurs with NTFS, FAT or ext4 SD card partitions. This should be pretty easy to track down, but I can run more tests if required. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1893562/+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 1893551] Re: Let im-config back off if IBus on GNOME desktops
Hello Gunnar, or anyone else affected, Accepted im-config into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/im- config/0.44-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: im-config (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893551 Title: Let im-config back off if IBus on GNOME desktops Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: Note: Quite a few ibus crash bug reports have been marked as duplicates of this bug. If you find that such a bug was not actually addressed through the fix of this bug, please feel free to comment on the bug report and remove the duplicate link. [Impact] GNOME desktops have built-in mechanisms for launching and configuring IBus. However, up to now im-config has overridden GNOME in this respect, resulting in a slightly different command for launching IBus and a few extra environment variables; most importantly GTK_IM_MODULE has been set to "ibus". This was recently changed via im-config 0.45-1 in groovy, where im- config does not do anything in case of IBus on a GNOME desktop. A positive side effect of the change is that the frequency of IBus crashes has been significantly reduced. No deep analysis has been carried out which explains *how* this change prevents IBus crashes. The basis for the conclusion is instead statistics from errors.ubuntu.com. Some relevant links can be found in this discourse topic: https://discourse.ubuntu.com/t/ibus-no-more-gtk-im-module-ibus/17727 [Test case] We have not been able to reproduce the crashes, so a simple test which verifies the fix can't be accomplished. Instead we need to be attentive to possible regressions. * On an Ubuntu desktop, install ibus-libpinyin and ibus-hangul. * Log out and log in again (to an X session). * Enable Intelligent Pinyin and Hangul (from Settings -> Region & Language) * For each of Intelligent Pinyin, Hangul, and the on screen keyboard: - Confirm that inputting works without hassle - Do so on various apps: FF, TB, gedit, LO. [Regression risk] Even if we have done it differently in Ubuntu (and Debian), the GNOME mechanisms we now let replace im-config with respect to IBus is mature code which has been in use for quite some time on other distros. That speaks for a low regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893551/+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 1893552] Re: Use im-config on Wayland without uninstalling IBus
Hello Gunnar, or anyone else affected, Accepted im-config into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/im- config/0.44-1ubuntu1.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: im-config (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1893552 Title: Use im-config on Wayland without uninstalling IBus Status in im-config package in Ubuntu: Fix Released Status in im-config source package in Focal: Fix Committed Bug description: [Impact] In a Wayland session on Ubuntu 20.04 im-config does not work as intended. To be able to use a non-IBus IM framework you basically need to first uninstall ibus (or 'fake uninstall' by renaming /usr/bin /ibus-daemon). This was fixed in im-config 0.45-1, and the proposed upload includes a patch with a cherry picked Debian commit. [Test case] * Install fcitx and fcitx-libpinyin * Open Language Support and switch to fcitx * Reboot and log in to a Wayland session * Open the fcitx preferences and add fcitx-libpinyin * Switch to fcitx-libpinyin and confirm that you can input Chinese [Regression risk] A similar method for making im-config work with Wayland was used in Ubuntu 17.10, which was shipped with Wayland as default. Since the approach has already been used without reported issues, the regression risk now should be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1893552/+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 1893562] Re: Second equal USB card reader not detected
could be similar to e.g https://github.com/storaged- project/udisks/issues/490 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1893562 Title: Second equal USB card reader not detected Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04.5 LTS, gnome-disks 3.28.3. Two exactly equal USB card readers ( 05e3:0749 genesys logic ) are inserted, each containing a formatted SD card, each with a single partition. Both disk partitions are correctly assigned devices on insertion. Only whichever adapter is inserted first automounts (as checked by mount) and only that adapter is listed in Gnome Disks. Both partitions names are listed in the gnome Places menu. After mounting the second partition via the Places menu, still only the first adapter is listed in Gnome Disks. The error occurs with NTFS, FAT or ext4 SD card partitions. This should be pretty easy to track down, but I can run more tests if required. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1893562/+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 1893470] Re: Cheese doesn't show image or video
** Changed in: cheese (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1893470 Title: Cheese doesn't show image or video Status in cheese package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.7 My webcam is connected to a USB port. Image/video in Cheese disappears within a fraction of a second. Only black window remains. I can't change anything on the window (except Preference) since all the other buttons are in disabled mode. But GTK UVC webcam app works very well without changing that port. I Changed the USB port for Cheese. Reinstalled and tried. But in vain. == ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cheese 3.18.1-2ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-187.217-generic 4.4.230 Uname: Linux 4.4.0-187-generic i686 ApportVersion: 2.20.1-0ubuntu2.24 Architecture: i386 CurrentDesktop: Unity Date: Fri Aug 28 23:13:38 2020 InstallationDate: Installed on 2018-05-07 (844 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: cheese3.18.1-2ubuntu3 cheese-common 3.18.1-2ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/10/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: PE94510M.86A.0050.2007.0710.1559 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D945GCPE dmi.board.vendor: Intel Corporation dmi.board.version: AAD97209-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1893470/+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 1893562] Re: Second equal USB card reader not detected
Thank you for your bug report, could you add the 'journalctl -b 0' log after triggering the issue as well as the 'udiskctl monitor' log from when connecting the devices? ** Changed in: gnome-disk-utility (Ubuntu) Importance: Undecided => High ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Incomplete ** Bug watch added: github.com/storaged-project/udisks/issues #490 https://github.com/storaged-project/udisks/issues/490 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1893562 Title: Second equal USB card reader not detected Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04.5 LTS, gnome-disks 3.28.3. Two exactly equal USB card readers ( 05e3:0749 genesys logic ) are inserted, each containing a formatted SD card, each with a single partition. Both disk partitions are correctly assigned devices on insertion. Only whichever adapter is inserted first automounts (as checked by mount) and only that adapter is listed in Gnome Disks. Both partitions names are listed in the gnome Places menu. After mounting the second partition via the Places menu, still only the first adapter is listed in Gnome Disks. The error occurs with NTFS, FAT or ext4 SD card partitions. This should be pretty easy to track down, but I can run more tests if required. Cheers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1893562/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
Does it work once the locale is installed? what language did you select during the installation? ** Changed in: gnome-calendar (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1891270] Re: Iranian calendar shows in Azerbaijani language
Which language did you select during the installation? Were you connected to internet from ubiquity? ** Changed in: ubiquity (Ubuntu) Importance: Undecided => Low ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1891270 Title: Iranian calendar shows in Azerbaijani language Status in gnome-calendar package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: Incomplete Bug description: I already installed Ubuntu 20.04.1 LTS and set location on Iran during installation. After finishing installation successfully, I open the calendar by clicking at the top of the screen (where the clock is shown), I see the calendar with Azerbaijani names for month and weekdays. Such as "آقوست" for August and "جومعه آخشامی" for Thursday. But it should show in Iranian names such as "اوت" for August and "پنجشنبه" for Thursday. Description: Ubuntu 20.04.1 LTS Release: 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1891270/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407602/+files/gdm3_3.34.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in OEM Priority Project: In Progress Status in gdm3 package in Ubuntu: In Progress Status in gnome-session package in Ubuntu: Confirmed Status in grub2 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash
[Desktop-packages] [Bug 1893827] Re: autopkgtest fails in groovy
that's the same as bug #1888062 right? ** Changed in: udisks2 (Ubuntu) Importance: Undecided => High ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- 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/1893827 Title: autopkgtest fails in groovy Status in udisks2 package in Ubuntu: Confirmed Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- groovy/groovy/arm64/u/udisks2/20200901_174238_f13fc@/log.gz ... == ERROR: test_loop_ro (__main__.Manager) loop device R/O -- Traceback (most recent call last): File "src/tests/integration-test", line 642, in test_loop_ro (path, out_fd_list) = self.manager.call_loop_setup_sync( gi.repository.GLib.GError: udisks-error-quark: GDBus.Error:org.freedesktop.UDisks2.Error.Failed: Error waiting for loop object after creating '/dev/loop0': Timed out waiting for object (0) -- Ran 31 tests in 371.897s FAILED (errors=1) Testing installed system binaries daemon path: /usr/libexec/udisks2/udisksd Set up test device: r/w: /dev/sda, r/o: /dev/sr0 autopkgtest [17:42:25]: test upstream-system: ---] autopkgtest [17:42:26]: test upstream-system: - - - - - - - - - - results - - - - - - - - - - upstream-system FAIL non-zero exit status 1 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1893827/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'd confirmed the regression with enabling Wayland. Due to nvidia-driver (nvidia-driver-440) disable wayland as default, I'll separate the verification to two scenarios. 1. Make sure the new gdm3 fixes this issue. 2. Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) --- * Make sure the new gdm3 fixes this issue * [Summary] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1. Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically". 2. Install with default options 2.1 Install nvidia-driver-440 (450.66-0ubuntu2) from ubuntu-archive. 2.2 Enable "Login automatically" from system settings. After reboot, the system won't login automatically even can not login manually. [Environment] HP 800 G6 DM + GeForce GTX 1660 [10de:2191] [Solution] Backport the solution from comment#119 as a debian package[2] (commit ID from upstream: f843233a, 690b3c01). The problem is solved. (Verified in scenario 2) The debdiff as attachment, please help to review. [1] sha256sum ``` $ sha256sum ~/Downloads/groovy-desktop-amd64.iso bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 /home/jeremysu/Downloads/groovy-desktop-amd64.iso ``` [2] gdm3 from https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801/+packages --- * Make sure the new gdm3 without the regression (https://gitlab.gnome.org/GNOME/gdm/-/issues/602) * This issue is happens when switching user under Wayland. I'd verified gdm3#602 issue when using intel graphic in the same machine because nvidia-driver disable Wayland as default. Steps to reproduce gdm3#602 issue: 1. Login a user "test" under x11 2. Create a user "test2" 3. Press "switch user ..." to "test2" under wayland 4. Switch back to "test" under x11 5. Switch to "test2" under wayland (then the running session be killed immediately) 6. Login again and then the mouse won't work. After applying commit 690b3c01, above problems are solved. Repeat to switch user and everything goes well. ** Patch added: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5407599/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Attachment removed: "gdm3_3.34.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1845801/+attachment/5406013/+files/gdm3_3.34.1-1ubuntu2.debdiff ** Description changed: [ Impact ] In some platforms with specific Nvidia cards (with nvidia-driver-440), enable auto-login (either during installation or after installation) will fail (either stuck in gdm login screen and not able to login even typing correct password). [ Test Case ] Here are two scenario of auto login with groovy (20.10) daily build[1]: 1) Checked "Install third-party software" (e.g. nvidia-driver) with enabling "Login automatically" during installation. 2) Install groovy daily build with default options, after installation completed: - 2.1) Install nvidia-driver-440 (450.57-0ubuntu2) from ubuntu-archive. + 2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive. 2.2) Enable "Login automatically" from system settings. Then reboot. [Expected result] System will boot into desktop environment without the login page. [Actual result] System boots to login page, and can't login to desktop environment with the correct password. [ Regression potential ] Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] and it works good. It passed the 30 times reboot stress test by using stress/reboot_30 from checkbox. [1] sha256sum: bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822 - [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 - [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm-1845801 + [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01 + [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801 --- I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64
[Desktop-packages] [Bug 1890772] Re: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8
** Changed in: xorg-server (Ubuntu) Status: Triaged => Invalid -- 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/1890772 Title: No signal on 4K 60Hz DisplayPort monitor by default, until "max bpc" is lowered to 8 Status in gnome-control-center: Unknown Status in HWE Next: New Status in Linux: Unknown Status in Mutter: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: The bug is originated from, https://bugs.launchpad.net/somerville/+bug/1887915/ https://bugs.launchpad.net/somerville/+bug/1886778 It has some problem when user connect to external 4K monitor with refresh rate 60. The problem can be solved by lower the bpc, or lower the refresh rate. `xrandr --output DP-3 --set "max bpc" 8` Would like to open this bug to open discussion for enhancing user experience. existed upstream bug: - https://gitlab.freedesktop.org/drm/intel/-/issues/1890 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-samwell-tgl+X42 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.6.0-1021-oem, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:09fc] Subsystem: Dell GP107M [GeForce MX350] [1028:09fc] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Package: xorg 1:7.7+19ubuntu14 [origin: unknown] PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=41be2253-410a-4ef7-a096-4193a58efdbd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Tags: third-party-packages focal ubuntu Uname: Linux 5.6.0-1021-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1890772/+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 1894018] Re: Visible Network list interface disconnects without user prompt upon just clicking the netowrk name
Thank you for your bug report, disconnecting from an access point doesn't seem destructive enough to require a confirmation but if you want to suggest that behaviour change the right place would be upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/issues ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Wishlist ** Changed in: gnome-control-center (Ubuntu) Status: New => Opinion -- 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/1894018 Title: Visible Network list interface disconnects without user prompt upon just clicking the netowrk name Status in gnome-control-center package in Ubuntu: Opinion Bug description: Visible Network wifi list interface Be connected to some wifi network Click on any network name (reconnects if clicked on currently connected network, and disconnects when clicked on some other network) Current wifi connection disconnects. No prompt no nothing. Just disconnects/reconnects. It would be best to ask prior to disconnect. It would be good to prompt whether user wants to initiate connection (and just then prompt for password). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 03:16:05 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-09-01 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894018/+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 1894090] Re: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78
** Changed in: thunderbird (Ubuntu) Importance: Undecided => Wishlist -- 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/1894090 Title: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78 Status in thunderbird package in Ubuntu: New Bug description: I suggest consolidating the thunderbird Ubuntu packaging with Debian for versions >= 78. Now that the lightning calendar extension is part of thunderbird, the thunderbird packaging between Ubuntu and Debian is getting closer except for the naming of the locale packages. The latest thunderbird version always gets updated in Debian 10 stable-security and Debian 9 oldstable-security since thunderbird follows the Firefox ESR versioning and Debian follows that. Ubuntu does a similar thing with its stable LTS releases, and hence could benefit from the Debian packaging. And when a new major release of Thunderbird is out, it gets updated in Debian unstable/experimental then backported to stable and oldstable. A similar thing happens in Ubuntu development and stable LTS releases. So I suggest a plan like this: 1. Transition the thunderbird locale packages in Ubuntu to the Debian naming 2. Merge the latest thunderbird with Debian unstable/experimental to Ubuntu development If the Debian maintainer agrees, the Ubuntu packaging could also happen in Debian salsa similar to what is already happening with GNOME packaging. I think sharing the thunderbird packaging between Ubuntu and Debian is beneficial to both sides going forward in the future, and especially if thunderbird packaging gets more complicated to backport to stable releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1894090/+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 1892897] Re: Cannot access a Samba file share anymore due to "Failed to retrieve file list from server"
That's not a nautilus bug, also it's discussed there https://askubuntu.com/questions/1229929/cant-acces-nas-anymore-after- upgrading-to-20-04 and mentioned on https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Samba_4.11 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1892897 Title: Cannot access a Samba file share anymore due to "Failed to retrieve file list from server" Status in nautilus package in Ubuntu: Invalid Bug description: This is a regression bug as I have no problems with another laptop running Ubuntu 18.04 LTS. Trying to access Samba file share on my Synology Diskstation (smb://diskstation.local) gives me just "Failed to retrieve file list from server: Software caused connection abort". See the attached screenshot of the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Aug 25 20:34:44 2020 InstallationDate: Installed on 2016-09-13 (1442 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-19 (98 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1892897/+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 1893579] Re: Ctrl + Alt + T and Fn keys not working
The issue is due to the gnome-settings-daemon update, the component got reverted now and blocked in proposed since it shouldn't be updated without the gnome shell new version. You either need to wait for the other component or manually revert to the previous binaries ** Package changed: gnome-terminal (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1893579/+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 1893855] Re: Mouse cursor hangs on Nautilus
No, because the previous bug hasn't the right log to be able to understand the issue. Anyway this issue 3-4 years old, and noone fixed it. -- 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/1893855 Title: Mouse cursor hangs on Nautilus Status in nautilus package in Ubuntu: Invalid Bug description: In "Files" file manager mouse cursor hangs, while opening a file: Reproduction 1) click on a text file in Nautilus (gedit opened with the file content) 2) click again on the same text file in Nautilus (5% a second window opens with the file content and a yellow header with buttons saying "edit anyway" - the file already opened, 95% chance the second window won't open, and the mouse cursor hangs (loading icon), and times out 10-15 sec later) In gedit there are tabs, i would expect that the file will be opened in the next tab or in a new window - if the file has been changed. If it's not just activate the previous window and release the mouse cursor. I have reported similar bugs, however i was not able to figure out the exact problem before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 00:18:17 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x454+138+136'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (99 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893855/+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 1893855] Re: Mouse cursor hangs on Nautilus
closing then since it's already reported ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- 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/1893855 Title: Mouse cursor hangs on Nautilus Status in nautilus package in Ubuntu: Invalid Bug description: In "Files" file manager mouse cursor hangs, while opening a file: Reproduction 1) click on a text file in Nautilus (gedit opened with the file content) 2) click again on the same text file in Nautilus (5% a second window opens with the file content and a yellow header with buttons saying "edit anyway" - the file already opened, 95% chance the second window won't open, and the mouse cursor hangs (loading icon), and times out 10-15 sec later) In gedit there are tabs, i would expect that the file will be opened in the next tab or in a new window - if the file has been changed. If it's not just activate the previous window and release the mouse cursor. I have reported similar bugs, however i was not able to figure out the exact problem before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 00:18:17 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x454+138+136'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (99 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893855/+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 1893855] Re: Mouse cursor hangs on Nautilus
Yes -- 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/1893855 Title: Mouse cursor hangs on Nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: In "Files" file manager mouse cursor hangs, while opening a file: Reproduction 1) click on a text file in Nautilus (gedit opened with the file content) 2) click again on the same text file in Nautilus (5% a second window opens with the file content and a yellow header with buttons saying "edit anyway" - the file already opened, 95% chance the second window won't open, and the mouse cursor hangs (loading icon), and times out 10-15 sec later) In gedit there are tabs, i would expect that the file will be opened in the next tab or in a new window - if the file has been changed. If it's not just activate the previous window and release the mouse cursor. I have reported similar bugs, however i was not able to figure out the exact problem before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 00:18:17 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x454+138+136'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (99 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893855/+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 1894031] Re: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen
** Tags added: rls-gg-incoming -- 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/1894031 Title: Ubuntu 20.10 gnome-control-center dropdowns missing for screen resolution and primary screen Status in gnome-control-center package in Ubuntu: Confirmed Bug description: The Ubuntu 20.10 version of g-c-c lacks the dropdown controls for changing screen resolution or selecting the primary monitor. Where there is normally a dropdown, there is just a label showing the current screen resolution or primary monitor. In some cases the dropdown is there, eg it might be there for the laptop monitor but not the external monitor(s). Changing the resolution of a monitor using xrandr sometimes makes the dropdown appear in g-c-c. I have attached a screenshot showing the issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.37.90-1ubuntu2 Uname: Linux 5.9.0-050900rc3-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 12:55:12 2020 InstallationDate: Installed on 2019-07-01 (429 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-09-01 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894031/+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 1893855] Re: Mouse cursor hangs on Nautilus
Thank you for your bug report, is that the issue than you reported on bug #1892400? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/1893855 Title: Mouse cursor hangs on Nautilus Status in nautilus package in Ubuntu: Incomplete Bug description: In "Files" file manager mouse cursor hangs, while opening a file: Reproduction 1) click on a text file in Nautilus (gedit opened with the file content) 2) click again on the same text file in Nautilus (5% a second window opens with the file content and a yellow header with buttons saying "edit anyway" - the file already opened, 95% chance the second window won't open, and the mouse cursor hangs (loading icon), and times out 10-15 sec later) In gedit there are tabs, i would expect that the file will be opened in the next tab or in a new window - if the file has been changed. If it's not just activate the previous window and release the mouse cursor. I have reported similar bugs, however i was not able to figure out the exact problem before. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 00:18:17 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'288' b'org.gnome.nautilus.window-state' b'geometry' b"'864x454+138+136'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified']" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified_with_time', 'recency']" InstallationDate: Installed on 2017-08-07 (1121 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2020-05-25 (99 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1893855/+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 1893021] Re: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar)
Awesome the bug patch just came through for me and now flash in Firefox 80.0.1 is working, thank-you very much Olivier Tilloy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1893021 Title: Flash plugin symbol lookup error with firefox 80.0+build2 on xenial (gtk_window_set_titlebar) Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: When testing firefox 80.0+build2 on xenial (from https://launchpad.net /~ubuntu-mozilla-security/+archive/ubuntu/ppa/+packages), I'm observing that the flash plugin (installed by flashplugin-installer) doesn't work. This appears to affect only xenial, flash is working in the bionic and focal builds. This is what I'm seeing when launching firefox from a terminal: /usr/lib/firefox/plugin-container: symbol lookup error: /usr/lib/firefox/libxul.so: undefined symbol: gtk_window_set_titlebar This is most likely caused by this recent upstream change: https://phabricator.services.mozilla.com/D84623 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1893021/+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 1894097] Re: Unable to switch from HSP to A2DP on BOSE blutoot headphones
Thank you for your bug report. The first issues sounds similar to bug #1870356 Could you add your 'journalctl -b 0' log after trying to change the profile? Could you also try with pavucontrol and see if it behaves the same way? ** 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/1894097 Title: Unable to switch from HSP to A2DP on BOSE blutoot headphones Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a Bose NC 700 pair of headphones. The device works correctly with Android and Windows (al be it more cumbersome and confusing in Windows). Device: Firmware 1.5.1-9303+d287f23 GUID: 5c097385-cd87-d8dd-bab9-4c726a0ac560 I am available to test. Problem 1: I am required to click on the "connect" toggle button for the Bluetooth audio device about 20 - 30 times to make it connect. This is also true for other speakers as for example JBL Bluetooth speakers. Problem 2: BOSE Headset/Gnome BT Audio configuration. I am unable to switch between HSP/DSP mode to A2DP Sink. The device remains connected as a communication device and not as an audio device. I remain stuck with mono sound. Though the gnome control panel indicates that I have indeed switched to A2DP Sink. However, when I click "test" I only get the mono test and the sound is absolutely unusable. Because there is a microphone on the headphones, Gnome control panel and the underlying Bluetooth service refuse to change from HSP/DSP. Clearly this is not by design. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 13:45:22 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-08-04 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1894097/+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 1893579] Re: Ctrl + Alt + T and Fn keys not working
@Geziel: well, Ubuntu 20.10 *is* a development version, so you expect some bugs. It is normally more usable at this stage of the development cycle, though. FWIW, I ran evtest, and the keys are mostly being reported the same in groovy and focal - they just don't work in groovy. eg the function keys all report their expected values (eg KEY_VOLUMEDOWN, KEY_VOLUMEUP, KEY_MUTE), with the exception of the brightness up/down keys, which aren't reported in either focal or groovy. One exception to this is that Alt-PrtScr is reported in groovy as unknown, whereas it's reported in focal as KEY_SYSRQ and KEY_LEFTALT. PrtScr is reported correctly in both as KEY_SYSRQ. It's still possible to read and change the system brightness in groovy via the kernel, ie on my Dell XPS 15 by catting or echoing an appropriate number to /sys/class/backlight/intel_backlight/brightness, but the function keys don't work and nor does the task bar system menu's dropdown menu slider. The dropdown menu slider is initially set to zero, so it looks like it can't read the brightness, either. -- 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/1893579 Title: Ctrl + Alt + T and Fn keys not working Status in gnome-terminal package in Ubuntu: Confirmed Bug description: The refered key combinations are no longer working on my desktop. The first one refers to opening the terminal. And the second one should work in combination with F2 or F3 or some other similars for incresing the volumen, or modifying brightness. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-08-05 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: gnome-terminal 3.36.2-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: third-party-packages groovy Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-08-05 (25 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1893579/+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
