[Desktop-packages] [Bug 1887795] Re: snap "chromium" has bad plugs or slots: system-packages-doc
To silence the warning run the command `snap okay` If you are concerned, you may uninstall chromium from snap `snap remove --purge chromium` and instead install using apt `sudo apt install chromium-browser` -- 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/1887795 Title: snap "chromium" has bad plugs or slots: system-packages-doc Status in chromium-browser package in Ubuntu: Fix Committed Bug description: I just installed chromium on my 20.04 machine. I've not used chromium on this system before. It installed but I get this warning: snap "chromium" has bad plugs or slots: system-packages-doc $ snap install chromium 2020-07-16T11:52:42+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") 2020-07-16T11:52:45+01:00 INFO snap "chromium" has bad plugs or slots: system-packages-doc (unknown interface "system-packages-doc") chromium 84.0.4147.89 from Canonical✓ installed WARNING: There is 1 new warning. See 'snap warnings'. $ snap version snap2.45.1+20.04.2 snapd 2.45.1+20.04.2 series 16 ubuntu 20.04 kernel 5.4.0-40-generic According to the documentation for system-packages-doc, this isn't available until snapd 2.46+, which isn't available in any channel. https://snapcraft.io/docs/the-system-package-doc-interface channels: latest/stable:2.45.2 2020-07-15 (8542) 31MB - latest/candidate: 2.45.2 2020-07-15 (8542) 31MB - latest/beta: 2.45.1 2020-06-05 (8140) 31MB - latest/edge: 2.45.2+git2005.gfdaa74a 2020-07-16 (8596) 31MB - installed: 2.45.1 (8140) 31MB snapd Perhaps we shouldn't use interfaces which aren't available yet? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1887795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898926] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
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/1898926
Title:
package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
NIL
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Oct 6 21:18:25 2020
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 1
InstallationDate: Installed on 2015-11-29 (1774 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2,
2.7.17-4
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
Snap.Changes:
ID Status Spawn Ready Summary
183 Error 2020-10-06T21:16:52+01:00 2020-10-06T21:18:24+01:00 Install
"chromium" snap
184 Done2020-10-07T20:26:53+01:00 2020-10-07T20:30:42+01:00 Install
"chromium" snap
185 Done2020-10-07T20:30:42+01:00 2020-10-07T20:30:45+01:00 Connect
chromium:password-manager-service to core:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 85.0.4183.121 snap
SourcePackage: chromium-browser
Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
UpgradeStatus: Upgraded to focal on 2020-10-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898926/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899356] Re: [snap] file chooser has no icons
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
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/1899356
Title:
[snap] file chooser has no icons
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on
Wayland session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing
all of the icons (see screenshot).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:06:45 2020
InstallationDate: Installed on 2020-10-08 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Snap.Changes: Error: command ['snap', 'changes', '--abs-time', 'chromium']
failed with exit code 1: error: no changes found
Snap.ChromeDriverVersion: ChromeDriver 85.0.4183.121
(a81aa729a8e1fd413943a339393c82e7b8055ddc-refs/branch-heads/4183@{#1864})
Snap.ChromiumVersion: Chromium 85.0.4183.121 snap
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899356/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898213] Re: package chromium-browser (not installed) failed to install/upgrade: subproces van het nieuwe pakket chromium-browser het script pre-installation gaf de foutwaarde
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1898213 Title: package chromium-browser (not installed) failed to install/upgrade: subproces van het nieuwe pakket chromium-browser het script pre- installation gaf de foutwaarde 1 terug Status in chromium-browser package in Ubuntu: Expired Bug description: I tried to install from the terminal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: chromium-browser:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 2 16:32:17 2020 ErrorMessage: subproces van het nieuwe pakket chromium-browser het script pre-installation gaf de foutwaarde 1 terug InstallationDate: Installed on 2020-06-22 (102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: subproces van het nieuwe pakket chromium-browser het script pre-installation gaf de foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902219] Re: Online Accounts Credentials Not Working
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1902219 Title: Online Accounts Credentials Not Working Status in gnome-control-center package in Ubuntu: Expired Bug description: I just booted up ubuntu 20.04 (Groovy Gorilla) and I couldn't use my google drive account in files. It was telling me that the credentials are wrong but I relogined then also no result same credentials expired. The Microsoft account was also showing wrong credentials. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 30 16:47:53 2020 InstallationDate: Installed on 2020-10-27 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash 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/1902219/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902911] Re: GNOME desktop does not suspend on lid close with HDMI TV connected
*** This bug is a duplicate of bug 1793918 ***
https://bugs.launchpad.net/bugs/1793918
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
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/1902911
Title:
GNOME desktop does not suspend on lid close with HDMI TV connected
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
Ubuntu 20.04 with all current updates, GNOME/Wayland desktop, Dell
Latitude E5450 notebook.
I have external TV connected via HDMI and I want notebook to suspend
when I close lid even if TV is connected. This does not work. Even
though logind is configured to suspend in this case:
$ cat /etc/systemd/logind.conf.d/allow-suspend-with-hdmi.conf
[Login]
HandleLidSwitchDocked=suspend
$
gnome-settings-daemon starts inhibitor as soon as it detects external
monitor:
WHO UID USER PID COMMWHAT
WHY
MODE
bor 1001 bor 96600 gsd-power
handle-lid-switchExternal monitor
attached or configuration changed recently block
so sytemd-logind does not initiate suspend, but there is also no code
in gnome-settings-daemon itself to handle lid close (as it completely
relies on systemd-logind today).
Ubuntu package includes patch ubuntu-lid-close-suspend.patch that
restores gsettings keys, but as there is no code to actually *use*
these keys patch has no effect:
$ gsettings list-recursively org.gnome.settings-daemon.plugins.power | grep
-w lid
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'suspend'
org.gnome.settings-daemon.plugins.power
lid-close-suspend-with-external-monitor true
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'suspend'
$
This most trivial (untested) patch to use this settings seems to be:
diff --git a/plugins/power/gsd-power-manager.c
b/plugins/power/gsd-power-manager.c
index c7a16e8d..9b7a99b5 100644
--- a/plugins/power/gsd-power-manager.c
+++ b/plugins/power/gsd-power-manager.c
@@ -1196,7 +1196,7 @@ upower_kbd_toggle (GsdPowerManager *manager,
static gboolean
suspend_on_lid_close (GsdPowerManager *manager)
{
-return !external_monitor_is_connected (manager->rr_screen);
+return g_settings_get_boolean (manager->settings,
"lid-close-suspend-with-external-monitor") || !external_monitor_is_connected
(manager->rr_screen);
}
static gboolean
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26~20.04.1-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 4 18:43:56 2020
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-trusty-amd64-20140620-0
InstallationDate: Installed on 2015-07-02 (1952 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary
20140620-04:25
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=ru_RU.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to focal on 2020-10-03 (32 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1902911/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909616] Re: Same user appears to be logged multiple times
Thank you for taking the time to report this bug and helping to make Ubuntu better. Are you sure you're not logged in multiple times? eg. via a text terminal (ctrl+alt+f4 for example) (I'm not sure if this should be filed against gnome-shell, gnome-session or gdm3; I've selected gnome-session for now) Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1909616 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. ** Package changed: ubuntu => gnome-session (Ubuntu) -- 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/1909616 Title: Same user appears to be logged multiple times Status in gnome-session package in Ubuntu: New Bug description: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description: Ubuntu 20.04.1 LTS Release: 20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1909616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909616] [NEW] Same user appears to be logged multiple times
You have been subscribed to a public bug: When I try to reboot it appears same user (the one I`m currently logged) is logged two additional times simultaneously. Check attached image Description:Ubuntu 20.04.1 LTS Release:20.04 Not sure what this package is related to. Expected to happen: When the reboot option was selected to start rebooting. What happened: Showed the window from the attached image with multiple logins from the same user. ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- Same user appears to be logged multiple times https://bugs.launchpad.net/bugs/1909616 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I can also confirm #322 works on manjaro after installing Linux
5.10.rc5.d1122 through the "Manjaro Settings Manager". Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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
[Desktop-packages] [Bug 1894090] Re: Consolidate thunderbird Ubuntu packaging with Debian for versions >= 78
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- 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: Confirmed 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 1898335] Re: Vino server stops when connecting to VPN after upgrade to 20.04
I've installed 20.04.1 from the scratch and unfortunately i'm able to reproduce the issue, so is not related to release upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1898335 Title: Vino server stops when connecting to VPN after upgrade to 20.04 Status in vino package in Ubuntu: Confirmed Bug description: After I upgraded from 18.04 to 20.04, whenever I am making a connection to a VPN server (using Network Manager), vino-server will stop when the VPN connection is established. This did not happen in 18.04 before the upgrade. syslog show the following when I connect to VPN 10:02:00 systemd: Stopped Vino VNC server. 10:02:00 systemd: Stopped Vino VNC server. 10:02:00 systemd: vino-server.service: Succeeded. 10:02:00 systemd: Stopping Vino VNC server... 10:02:00 NetworkManager: [1601712120.6080] device (tun0): Activation: successful, device activated. 10:02:00 NetworkManager: [1601712120.6080] device (tun0): Activation: successful, device activated. 10:02:00 NetworkManager: [1601712120.6065] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') 10:02:00 NetworkManager: [1601712120.6059] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') 10:02:00 NetworkManager: [1601712120.6030] policy: set 'CH-Zurich-zur-c04' (tun0) as default for IPv4 routing and DNS 10:02:00 systemd: Started Network Manager Script Dispatcher Service. 10:02:00 dbus-daemon: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' 10:02:00 NetworkManager: [1601712120.5706] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') 10:02:00 systemd: Starting Network Manager Script Dispatcher Service... 10:02:00 NetworkManager: [1601712120.5442] device (tun0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external') 10:02:00 dbus-daemon: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.12' (uid=0 pid=817 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined") 10:02:00 NetworkManager: [1601712120.5428] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: VPN connection: (IP Config Get) complete 10:02:00 openvpn: Initialization Sequence Completed 10:02:00 NetworkManager: [1601712120.5307] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: VPN plugin: state changed: started (4) 10:02:00 openvpn: UID set to nm-openvpn 10:02:00 NetworkManager: [1601712120.5297] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",4:(tun0)]: Data: Internal Point-to-Point Address: 172.21.24.45 10:02:00 openvpn: GID set to nm-openvpn 10:02:00 NetworkManager: [1601712120.5202] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",0]: VPN connection: (IP Config Get) reply received. 10:02:00 openvpn: /usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --debug 0 2287 --bus-name org.freedesktop.NetworkManager.openvpn.Connection_2 --tun -- tun0 1500 1553 172.21.24.45 255.255.254.0 init 10:02:00 systemd-udevd: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. 10:02:00 openvpn: TUN/TAP device tun0 opened 10:01:58 NetworkManager: [1601712118.4499] vpn-connection[0x55c9c0868150,7eaf9e98-1048-4bb3-96ee-5c1dcf4e9b5a,"CH-Zurich-zur-c04",0]: VPN connection: (ConnectInteractive) reply received 10:01:54 gnome-shell: ../clutter/clutter/clutter-actor.c:10556: The clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 3 10:08:27 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-09-29 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1898335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from Des
I have enabled groovy-proposed, and I have not seen this error for 5 ~days. Previously the problem occurred 2-3 times per day. This seems to have solved the problem for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898910 Title: gnome-shell crashes when you try to change the resolution [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206] Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Groovy: Confirmed Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Confirmed Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Regression potential] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898005 --- Ubuntu on Wayland crashes when you try to change the resolution even if your display supports the Version: 3.38.0-1ubuntu2 Release: 20.10 Groovy Gorilla (development branch) What I expected to happen 1. Login to Wayland 2. Change the resolution 3. Go on with my day What actually happened 1. Login to Wayland 2. Change the resolution 3. Wait a minute to get kicked to the gdm login screen 4. Now I am here. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 12:55:35 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909599] [NEW] LibreOffice fails to fully resume focus with alt+tab
Public bug reported: Using updated focal, with nvidia proprietary driver, rtl (Hebrew) interface, all gnome-shell extensions disabled. When navigating to an open copy of LibreOffice with Alt+Tab, the application window receives focus, but fails to reflect user input. The carret is not shown, typed characters are not shown, clicking menus does not show response, etc. In order to resolve this I have to use Alt+Tab to navigate away to another app and back to LibreOffice. To reproduce: 1. Load Firefox, then load LibreOffice Writer and open a document. 2. Use Alt+Tab to move to Firefox. 3. Click several times inside the Firefox window, highlight text, etc. 4. Use Alt+Tab to move back to Writer. 5. Type any character. Expected result: - The character is shown on screen. Actual result: - More often than not, the character is typed in Writer, but the screen is not updated to reflect this. Using Alt+Tab again to navigate to firefox and back to Writer resolves this. This makes working with LibreOffice quite difficult. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Dec 29 20:10:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (846 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (103 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1909599 Title: LibreOffice fails to fully resume focus with alt+tab Status in gnome-shell package in Ubuntu: New Bug description: Using updated focal, with nvidia proprietary driver, rtl (Hebrew) interface, all gnome-shell extensions disabled. When navigating to an open copy of LibreOffice with Alt+Tab, the application window receives focus, but fails to reflect user input. The carret is not shown, typed characters are not shown, clicking menus does not show response, etc. In order to resolve this I have to use Alt+Tab to navigate away to another app and back to LibreOffice. To reproduce: 1. Load Firefox, then load LibreOffice Writer and open a document. 2. Use Alt+Tab to move to Firefox. 3. Click several times inside the Firefox window, highlight text, etc. 4. Use Alt+Tab to move back to Writer. 5. Type any character. Expected result: - The character is shown on screen. Actual result: - More often than not, the character is typed in Writer, but the screen is not updated to reflect this. Using Alt+Tab again to navigate to firefox and back to Writer resolves this. This makes working with LibreOffice quite difficult. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue Dec 29 20:10:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-05 (846 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-09-17 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909599/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
This happens to me also. Weirdly, only Twitter videos seem affected. It's possible it happens elsewhere, but I haven't seen it yet. Ubuntu 20.10 Firefox 84 -- 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/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909594] [NEW] No feedback when unmounting is finished
Public bug reported: I'm using "Files" 3.36.3-stable on Ubuntu 20.04. When writing large amounts of data to USB HDD it can take up to a minute to fully flush the data to HDD. "Files" provides a button for unmounting of my USB HDD. When I click this button unmount is started with "Unmounting usbdisk - Disconnecting from filesystem" appearing in notification area. This notification stays on the screen until I remove it with "X". It stays on the screen even after unmounting is finished. But in GUI there is NO notification that unmounting has finished! And if the notification is removed (with "X") there is also no indication that unmounting is still in progress. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1909594 Title: No feedback when unmounting is finished Status in nautilus package in Ubuntu: New Bug description: I'm using "Files" 3.36.3-stable on Ubuntu 20.04. When writing large amounts of data to USB HDD it can take up to a minute to fully flush the data to HDD. "Files" provides a button for unmounting of my USB HDD. When I click this button unmount is started with "Unmounting usbdisk - Disconnecting from filesystem" appearing in notification area. This notification stays on the screen until I remove it with "X". It stays on the screen even after unmounting is finished. But in GUI there is NO notification that unmounting has finished! And if the notification is removed (with "X") there is also no indication that unmounting is still in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1909594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@wangjun (biggerchina) i can confirm that #311 is working without any
workarounds when applied on 5.10.3 with touchpad MSFT0001:00 04F3:3140
and Ubuntu 20.04, thanks!
If anyone on a Debian based system is interested: i've uploaded the
patched version as .deb-packages here
https://drive.google.com/drive/folders/1ICZmuBx3ecwxtwufhSHbYmfnv9Prw-
kc?usp=sharing
@Coiby Xu (coiby) Phan Thanh Long (phanlong2811) any chance to get #311
backported to 5.10?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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" -
[Desktop-packages] [Bug 1909563] [NEW] Unknown to me
Public bug reported: Just Returning to Ubuntu and system produced some errors, reporting them but don't know how they were produced or how to repeat them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 29 13:47:12 2020 DistUpgraded: 2020-12-29 12:56:20,466 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a12] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics Controller [103c:30d8] Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics Controller [103c:30d8] InstallationDate: Installed on 2020-12-28 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic root=UUID=cec6ddcf-c54f-459c-97a6-0e6a2b0640f5 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-29 (0 days ago) dmi.bios.date: 01/10/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MDU Ver. F.09 dmi.board.name: 30D8 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 83.0E dmi.chassis.asset.tag: CNU8090376 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MDUVer.F.09:bd01/10/2008:svnHewlett-Packard:pnHPCompaq6720s:pvrF.09:rvnHewlett-Packard:rn30D8:rvrKBCVersion83.0E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP Compaq 6720s dmi.product.version: F.09 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 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: Tue Dec 29 12:59:58 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic compiz-0.9 i386 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909563 Title: Unknown to me Status in xorg package in Ubuntu: New Bug description: Just Returning to Ubuntu and system produced some errors, reporting them but don't know how they were produced or how to repeat them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Dec 29 13:47:12 2020 DistUpgraded: 2020-12-29 12:56:20,466 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller [8086:2a12] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics Controller [103c:30d8] Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated Graphics Controller [103c:30d8] InstallationDate: Installed on 2020-12-28 (1 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) MachineType: Hewlett-Packard HP Compaq 6720s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-128-generic root=UUID=cec6ddcf-c54f-459c-97a6-0e6a2b0640f5 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-29 (0 days ago) dmi.bios.date: 01/10/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MDU Ver. F.09 dmi.board.name: 30D8 dmi.board.vendor: Hewlett-Packard
[Desktop-packages] [Bug 1870822] Re: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
** Project changed: gnome-shell => mutter ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1870822 Title: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: just what I said in the title, the gnome user interface hung for a minute or so, after pressing 'x' to close a terminal window... been having other issues with the gnome-shell, in this ubuntu beta, this is new. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:40:19 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 335662] Re: [jaunty] hplip status service cannot find system tray
I can confirm seeing this issue on a number of computers running Ubuntu 20.04 in the last month or so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/335662 Title: [jaunty] hplip status service cannot find system tray Status in HPLIP: Fix Released Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: Fix Released Bug description: Binary package hint: hplip After login to ubuntu hplip status service cannot find system tray. It shows dialog box: "No system tray detected on this system. Unable to start, exiting". hplip version is 2.8.12-3ubuntu1 on jaunty I found the same bug reported in Debian http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg618714.html Regards To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/335662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909543] [NEW] "Failed to start Sound Service" in security logs
Public bug reported: Security logs are complaining about failing to start the sound service, on a new installation of Ubuntu 20.04 LTS. This is concerning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3182 F pulseaudio /dev/snd/pcmC0D0c: vadi 3182 F...m pulseaudio /dev/snd/pcmC0D0p: vadi 3182 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 29 09:35:00 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1412 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Selection_560.png" https://bugs.launchpad.net/bugs/1909543/+attachment/5447585/+files/Selection_560.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1909543 Title: "Failed to start Sound Service" in security logs Status in pulseaudio package in Ubuntu: New Bug description: Security logs are complaining about failing to start the sound service, on a new installation of Ubuntu 20.04 LTS. This is concerning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.8 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vadi 3182 F pulseaudio /dev/snd/pcmC0D0c: vadi 3182 F...m pulseaudio /dev/snd/pcmC0D0p: vadi 3182 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 29 09:35:00 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-15 (1412 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.3:bd07/30/2020:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1909543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232872]
Removing the strace -f command also avoids the stall (which is much longer than 30 seconds, about 80 seconds in my last attempt) -- 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/1232872 Title: [upstream] NFS / lock problem with LibreOffice wth 13.04 Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Hi all, I have a problem very similar to what is exposed in question #234375. Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing documents via NFS with LibreOffice. The slash screen display for about 30s, then there is a popup warning saying that another user has opened the file, and offering to open a copy, open as readonly or cancel. The point is, no other user has opened that file (being the only user on my personal PC, but storing my documents on NAS). So I tried the suggestion about adding "noauto" in /etc/fstab and changing /etc/rc.local, with no luck. But the modification of /usr/lib/libreoffice/program/soffice: ## # STAR_PROFILE_LOCKING_DISABLED=1 export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ... #export SAL_ENABLE_FILE_LOCKING ### (That is, uncomment the first 2 lines, and commenting the other 2) This works OK. If this is the official way of fixing things, then I guess LibreOffice deserves an update on Ubuntu at least. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232872]
Hello,
I've just downloaded libre office 7.0.4 from
https://www.libreoffice.org/download/download/
Version: 7.0.4.2
Build: dcf040e67528d9187c66b2379df5ea4407429775
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3;
Locale: fr-FR (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Same command as in comment #8, different trace, where we now can see many uses
of UNLCK.
However when the trace reaches the point marked with '***', opening the
document stalls for a long while (about 30 seconds I guess), then resumes, and
we see another use of l_type=F_WRLCK.
When quiting Libre Office, we can see 6 uses of l_type=F_WRLCK:
[pid 11281] fcntl(15, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(15, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(19, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(19, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11287] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}
[pid 11281] fcntl(20, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(3, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741825, l_len=1}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=2}) = 0
[pid 11281] fcntl(21, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741825, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=2}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0,
l_len=0}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET,
l_start=1073741826, l_len=510}) = 0
[pid 11281] fcntl(22, F_SETLK, {l_type=F_UNLCK, l_whence=SEEK_SET,
l_start=1073741824, l_len=1}) = 0
[Desktop-packages] [Bug 1232872]
Hello, Just re-tested with libreoffice from my Ubuntu-20.04.1 machine. Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3; Locale: fr-FR (en_US.UTF-8); UI-Language: en-US Calc: threaded Same command as in comment #8, same issue. -- 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/1232872 Title: [upstream] NFS / lock problem with LibreOffice wth 13.04 Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Hi all, I have a problem very similar to what is exposed in question #234375. Since I upgraded to Ubuntu 13.04 (host x86_64), I have trouble accessing documents via NFS with LibreOffice. The slash screen display for about 30s, then there is a popup warning saying that another user has opened the file, and offering to open a copy, open as readonly or cancel. The point is, no other user has opened that file (being the only user on my personal PC, but storing my documents on NAS). So I tried the suggestion about adding "noauto" in /etc/fstab and changing /etc/rc.local, with no luck. But the modification of /usr/lib/libreoffice/program/soffice: ## # STAR_PROFILE_LOCKING_DISABLED=1 export STAR_PROFILE_LOCKING_DISABLED # # file locking now enabled by default #SAL_ENABLE_FILE_LOCKING=1 # <<- if set to 0 ; same trouble ... #export SAL_ENABLE_FILE_LOCKING ### (That is, uncomment the first 2 lines, and commenting the other 2) This works OK. If this is the official way of fixing things, then I guess LibreOffice deserves an update on Ubuntu at least. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1232872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
