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
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
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
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
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
*** 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
*** 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,
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
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:
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-
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
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
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/
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
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
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
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:
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:
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:
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
20 matches
Mail list logo
