[Bug 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix
Hi, package x2goclient 4.1.2.1-2ubuntu0.19.10.1 fixes this issue on my Kubuntu 19.10. - Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856795 Title: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x2goclient/+bug/1856795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858205] Re: x2go-client connection failed. cannot create remote file
Ubuntu 19.10 is also affected. However, this bug has already been fixed in X2Go: https://code.x2go.org/gitweb?p=x2goclient.git;a=commit;h=ce559d163a943737fe4160f7233925df2eee1f9a And a nightly package has already been built: https://launchpad.net/ubuntu/+source/x2goclient/4.1.2.1-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858205 Title: x2go-client connection failed. cannot create remote file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x2goclient/+bug/1858205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811730] Re: Thermald does not set max CPU after reseting the voltage using RAPL
Is there any chance this fix will be available for 18.10 as well? Thanks, Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811730 Title: Thermald does not set max CPU after reseting the voltage using RAPL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1811730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume
I downloaded and installed bluez_5.48-0ubuntu3.1_amd64.deb. It seems that the bug is fixed. :) Thx! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759628 Title: bluez regression: Bluetooth audio fails to reconnect after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume
Will this fix (aka the new package version) be released to the 18.04 repos? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759628 Title: bluez regression: Bluetooth audio fails to reconnect after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773912] [NEW] bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 ***
https://bugs.launchpad.net/bugs/1759628
Public bug reported:
Description: Ubuntu 18.04 LTS
Release:18.04
bluez:
Installed: 5.48-0ubuntu3
Candidate: 5.48-0ubuntu3
Version table:
*** 5.48-0ubuntu3 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expect to happen:
After resuming my Ubuntu from standby I expect my bluetooth daemon to connect
to my BT headset properly if I tell it to do so.
4) What actually happens:
After resuming I can click 'Connect as ADP Sink' in, for example, blueman, it
starts connecting, and aborts after a while.
When I restart the bluetoothd ('systemctl restart bluetoothd'), I can easily
connect my BT headset.
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "bluetoothd-log.txt"
https://bugs.launchpad.net/bugs/1773912/+attachment/5145865/+files/bluetoothd-log.txt
** Package changed: strongswan (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773912
Title:
bluetoothd unable to establish connection after resume from suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773912] Re: bluetoothd unable to establish connection after resume from suspend
*** This bug is a duplicate of bug 1759628 *** https://bugs.launchpad.net/bugs/1759628 Kernel Version: 4.16.5 I also tried 'rfkill block bluetooth' and 'rfkill unblock bluetooth' after resume, but no success. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773912 Title: bluetoothd unable to establish connection after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772990] [NEW] Race condition when opening kwallet on login
Public bug reported:
Description:Ubuntu 18.04 LTS
Release:18.04
kde-runtime:
Installed: 4:17.08.3-0ubuntu1
Candidate: 4:17.08.3-0ubuntu1
Version table:
*** 4:17.08.3-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status
Setup:
My login password is the same as the password for my default kwallet
(kdewallet).
Hence, kde will automatically open it on login.
I added a script to ~/.config/autostart-scripts/ which loads my ssh key using
ksshaskpass.
What I expect to happen:
1) KDE/SDDM (or whatever) opens my default kwallet
2) KDE executes my autostart script which in my case loads my ssh keys. This
happens without prompting neither for the kwallet password nor for the
passphrase.
What does happen:
It looks like KDE executes step 1) and 2) in parallel. Step 2) is faster than
1) which blocks all remaining accesses to my wallet, e.g., Network-Manager
connecting to my wifi.
Moreover, step 2) prompts for my kwallet password.
If I abort that prompt, the kwallet won't be opened at all. It seems that step
1) is not executed.
If I add the following snippet to my addkeys.sh script, everything works as
expected:
DEFAULT_WALLET="kdewallet"
IS_OPEN_CMD="qdbus org.kde.kwalletd /modules/kwalletd org.kde.KWallet.isOpen"
while [ `${IS_OPEN_CMD} ${DEFAULT_WALLET}` == "false" ];
do
sleep 1
done
This code delays the loading of my ssh key until the kwallet is opened
correctly.
** Affects: kde-runtime (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772990
Title:
Race condition when opening kwallet on login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1772990/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758243] Re: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0
I can confirm as of today this bug is still present. I made the changes suggested by Rocko. Still primusrun does not work properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758243 Title: bumblebee needs configuration changes to work with nvidia-driver-390 and libglvnd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768390] Re: BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia-driver-390
Still broken as of today on Ubuntu 18.04 with kernel 4.16.7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768390 Title: BadMatch error in X_GLXSwapBuffers running OpenGL apps with nvidia- driver-390 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1768390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772705] [NEW] IKEv2 VPN connections fail to use DNS servers provided by the server
Public bug reported: Description:Ubuntu 18.04 LTS Release:18.04 strongswan-nm: Installed: 5.6.2-1ubuntu2 Candidate: 5.6.2-1ubuntu2 Version table: *** 5.6.2-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Expectation: Strongswan should actually receive and set the DNS server properly. What does happen: Strongswan-nm (charon-nm) does set a random DNS server which breaks the name resolution completely. The bug has already been reported for RedHat, and has been fixed in the strongswan upstream repo: https://bugzilla.redhat.com/show_bug.cgi?id=1574939 ** Affects: strongswan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772705 Title: IKEv2 VPN connections fail to use DNS servers provided by the server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1772705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
I finally solved the problem with the help of Ian Kent. He pointed me in the right direction: https://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git/commit/?id=37dd05dd1bccdedc4157902420e1da506b2bf35f A trailing slash in the /etc/auto.master was the problem. I consider it both a config problem and a bug. However, it has already been fixed in the upstream sources. I therefore ask you to update Ubuntu's version of autofs daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
Just a little update: I think I've figured out what causes autofs to stall. Since I've tested sshfs and cifs, and reproduced it using both, I can rule out a specific target fs. I think it has something to do with the indirekt map feature: #/etc/auto.master /media/auto-smb/ program:/etc/auto.smb /media/single-smb/ /etc/auto-single.smb #/etc/auto.smb #Same file as shipped with the Ubuntu package. #/etc/auto-single.smb * -fstype=cifs,vers=1.0,credentials=/etc/creds/myhost ://myhost/& Every mount under /media/single-smb/ will automatically disappear after $timeout. Whereas, a mount under /media/auto-smb/ will *not* disappear. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
Some additional information: By further digging into it, I've learned that for some reasons the smb is reported busy. In autofs4_mount_busy(https://elixir.bootlin.com/linux/v4.15.6/source/fs/autofs4/expire.c#L34) the call of may_umount_tree() returns 0. This indicates that the mount is considered busy. I'll keep you posted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
Some additional information: I enabled the debug output for autofs4 module: echo -n 'module autofs4 +p' > /sys/kernel/debug/dynamic_debug/control According to the kernel log, the mount is reported busy: autofs4:pid:7051:autofs4_mount_busy: returning = 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] Re: AutoFS does not automatically umount SMB shares
As far as I know, just a few steps are necessary to reproduce this issue: 1. Setup a simple smb server on machine a, like the one I've attached to this report. 2. Create a smb user on machine a: smbpasswd -a $username 3. Enable smb in auto.master on machine b (and set the timeout to something small, e.g., 30 secs): /media/smb/ program:/etc/auto.smb 4. Save the credentials on machine b: echo "username=$username\npassword=$password" > /etc/creds/machineb 5. Try to access the home directory from machine b: user@machineb:~$ ls -lh /media/smb/machineb/$username 6. The smb mount is still there after more than 30 seconds ** Attachment added: "smb.conf" https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+attachment/5078500/+files/smb.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754506] [NEW] AutoFS does not automatically umount SMB shares
Public bug reported: Description:Ubuntu 17.10 Release:17.10 autofs: Installed: 5.1.2-1ubuntu1 Candidate: 5.1.2-1ubuntu1 Version table: *** 5.1.2-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Kernel: self-built 4.15.6 What I expect: I expect AutoFS to automatically unmount my samba share after the timeout. However, it does not. The share is still mounted. I've turned the autofs debug output in the kernel module. As far as I can tell, the kernel thinks the cifs mount is still busy. I'm using the smb automount script provided by the package: /etc/auto.smb. I've just added an additional cifs parameter(vers=2.0). My auto.master looks as follows: /media/smb/ program:/etc/auto.smb ** Affects: autofs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "autofs.conf" https://bugs.launchpad.net/bugs/1754506/+attachment/5073761/+files/autofs.conf ** Description changed: Description:Ubuntu 17.10 Release:17.10 autofs: - Installed: 5.1.2-1ubuntu1 - Candidate: 5.1.2-1ubuntu1 - Version table: - *** 5.1.2-1ubuntu1 500 - 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 5.1.2-1ubuntu1 + Candidate: 5.1.2-1ubuntu1 + Version table: + *** 5.1.2-1ubuntu1 500 + 500 http://de.archive.ubuntu.com/ubuntu artful/main amd64 Packages + 100 /var/lib/dpkg/status + + Kernel: self-built 4.15.6 What I expect: - I expect AutoFS to automatically unmount my samba share after the timeout. However, it does not. - The share is still mounted. + I expect AutoFS to automatically unmount my samba share after the timeout. However, it does not. The share is still mounted. + I've turned the autofs debug output in the kernel module. As far as I can tell, the kernel thinks the cifs mount is still busy. I'm using the smb automount script provided by the package: /etc/auto.smb. I've just added an additional cifs parameter(vers=2.0). My auto.master looks as follows: /media/smb/ program:/etc/auto.smb ** Package changed: libreoffice (Ubuntu) => autofs (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754506 Title: AutoFS does not automatically umount SMB shares To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1754506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750087] Re: [libreoffice-kde4] LO crashes when trying to save
Oh. If so, please excuse my harsh question. I was not aware that apparmor profiles never been activated before for LO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750087 Title: [libreoffice-kde4] LO crashes when trying to save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750087] Re: [libreoffice-kde4] LO crashes when trying to save
Do you seriously consider "added to disable apparmor profiles on" as a fix for this issue? On my opinion, this is just a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750087 Title: [libreoffice-kde4] LO crashes when trying to save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1750087] Re: [libreoffice-kde4] LO crashes when trying to save
As I've already mentioned, one of my machines is also affected. I posted context information for that machine which is *not* affected: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751783 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750087 Title: [libreoffice-kde4] LO crashes when trying to save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
