[Desktop-packages] [Bug 2022916] [NEW] gdbusconnection: Explicitly destroy an idle source on cleanup
Public bug reported: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022916 Title: gdbusconnection: Explicitly destroy an idle source on cleanup Status in glib2.0 package in Ubuntu: New Bug description: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2022916/+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 2022916] Re: gdbusconnection: Explicitly destroy an idle source on cleanup
See UT issue discussion here: https://gitlab.com/ubports/development/core/lomiri-app- launch/-/merge_requests/49 ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2022916 Title: gdbusconnection: Explicitly destroy an idle source on cleanup Status in glib2.0 package in Ubuntu: New Bug description: In Ubuntu Touch we run into regular unit test freezes of lomiri-app- launch (formerly known as ubuntu-app-launch) based on some race time conditions (number of CPUs to build/test on, CPU speed, etc.). As it turned out, the game changer is a commit in glib2.0 upstream: https://gitlab.gnome.org/GNOME/glib/-/commit/5a69cc22dc9564db55e68531fb8250dcca7aaf17 It would be super-cool to see this commit applied on top of glib2.0 in Ubuntu focal and Ubuntu jammy. Thanks+Greets, Mike (aka sunweaver @ Debian, working for the UBports core dev team these days) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2022916/+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 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix
@ginggs: What else is needed to get this fix for X2Go Client into Ubuntu
updates?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1856795
Title:
[SRU] X2Go Client broken by libssh CVE-2019-14889 fix
Status in libssh package in Ubuntu:
Invalid
Status in x2goclient package in Ubuntu:
Fix Released
Status in libssh source package in Xenial:
Invalid
Status in x2goclient source package in Xenial:
In Progress
Status in libssh source package in Bionic:
Invalid
Status in x2goclient source package in Bionic:
In Progress
Status in libssh source package in Disco:
Invalid
Status in x2goclient source package in Disco:
Confirmed
Status in libssh source package in Eoan:
Invalid
Status in x2goclient source package in Eoan:
In Progress
Status in x2goclient package in Debian:
Fix Released
Bug description:
[Test case]
Connect to a x2go server on a session that has file sharing or
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received:
scp: ~/.x2go/ssh: No such file or directory" needs to be clicked away
with "ok".
[Regression potential]
Very low as the patch removes "~" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
--
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status
code 1 received: scp: ~username/.x2go/ssh: No such file or
directory\n". (Also note the literal "\n" there, but I guess we don't
really need to care about that.)
The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed
security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is
very difficult due to the reformatting that was done at the same time.
This degraded the patch(es) into one big blob.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1856795] Re: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5
See Debian bug 947129 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947129 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1856795 Title: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5 Status in libssh package in Ubuntu: Confirmed Bug description: The recent CVE fix broke SCP support in libssh, which X2Go Client (x2goclient) relies on. Sessions now fail with error messages such as "SCP: Warning: status code 1 received: scp: ~username/.x2go/ssh: No such file or directory\n". (Also note the literal "\n" there, but I guess we don't really need to care about that.) The previous version worked fine and rolling the libssh4 package back fixes this issue, but also leaves users vulnerable to the fixed security issue in its scp implementation. I've been looking at the debdiff, but spotting the actual changes is very difficult due to the reformatting that was done at the same time. This degraded the patch(es) into one big blob. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1856795] Re: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5
I think, this issue needs to be re-assigned and someone needs to provide updates for x2goclient in all supported Ubuntu releases that have received the fix for CVE-2019-14889. This patch needs to be applied on top of X2Go Client: https://code.x2go.org/gitweb?p=x2goclient.git;a=patch;h=ce559d163a943737fe4160f7233925df2eee1f9a For Debian, I am currently on this... ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14889 ** Bug watch added: Debian Bug tracker #947129 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947129 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libssh in Ubuntu. https://bugs.launchpad.net/bugs/1856795 Title: X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5 Status in libssh package in Ubuntu: Confirmed Bug description: The recent CVE fix broke SCP support in libssh, which X2Go Client (x2goclient) relies on. Sessions now fail with error messages such as "SCP: Warning: status code 1 received: scp: ~username/.x2go/ssh: No such file or directory\n". (Also note the literal "\n" there, but I guess we don't really need to care about that.) The previous version worked fine and rolling the libssh4 package back fixes this issue, but also leaves users vulnerable to the fixed security issue in its scp implementation. I've been looking at the debdiff, but spotting the actual changes is very difficult due to the reformatting that was done at the same time. This degraded the patch(es) into one big blob. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1765664] Re: Make cmdline option --indicator available again (as no-op)
As I side note... I will submit various Ubuntu patches for nm-applet upstream in the next couple of days. Also, I submitted an upstream patch, that enables building nm-applet against Ayatana AppIndicator. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1765664 Title: Make cmdline option --indicator available again (as no-op) Status in network-manager-applet package in Ubuntu: New Bug description: This is about this nm-applet patch: https://bazaar.launchpad.net/~ubuntu-desktop/network-manager-applet/ubuntu/view/head:/debian/patches/Have-the-appindicator-enabled-by-default.patch In the referenced patch you remove the --indicator option and add --no-indicator. This breaks applications launching nm-applet with --indicator option set. I am esp. interested in arctica-greeter, that needs to launch nm- applet with --indicator option on all non-Ubuntu platforms (all that don' have your patch). Thus, my request is: please keep --indicator and make it a no-op option in Ubuntu. Thanks! Mike To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1765664/+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 1765664] [NEW] Make cmdline option --indicator available again (as no-op)
Public bug reported: This is about this nm-applet patch: https://bazaar.launchpad.net/~ubuntu-desktop/network-manager-applet/ubuntu/view/head:/debian/patches/Have-the-appindicator-enabled-by-default.patch In the referenced patch you remove the --indicator option and add --no- indicator. This breaks applications launching nm-applet with --indicator option set. I am esp. interested in arctica-greeter, that needs to launch nm- applet with --indicator option on all non-Ubuntu platforms (all that don' have your patch). Thus, my request is: please keep --indicator and make it a no-op option in Ubuntu. Thanks! Mike ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1765664 Title: Make cmdline option --indicator available again (as no-op) Status in network-manager-applet package in Ubuntu: New Bug description: This is about this nm-applet patch: https://bazaar.launchpad.net/~ubuntu-desktop/network-manager-applet/ubuntu/view/head:/debian/patches/Have-the-appindicator-enabled-by-default.patch In the referenced patch you remove the --indicator option and add --no-indicator. This breaks applications launching nm-applet with --indicator option set. I am esp. interested in arctica-greeter, that needs to launch nm- applet with --indicator option on all non-Ubuntu platforms (all that don' have your patch). Thus, my request is: please keep --indicator and make it a no-op option in Ubuntu. Thanks! Mike To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1765664/+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 985202] Re: libx11 causes kwin to crash on login (over NX protocol)
Hi all, I just tested the new libxrandr2 package on precise with X2Go and nx- libs 2:3.5.0.20. The kwin crashes are gone, indeed. So far so good. However, the NX capability of resizing a non-fullscreen desktop session window is completely gone now. Expected behaviour: o Start a (KDE) session with a geometry of 1024x768 in non-full screen mode o Resize the NX agent window (i.e. maximize it or drag with the mouse pointer on one of the window corners o Expectation: the desktop shell inside resizes all its elements and adapts to the new desktop size What happens: o the desktop shell stubbornly remains at its initial geometry (1024x768 in this example) and refuses to adapt its elements to the new desktop session window size Greets, Mike (from X2Go upstream) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/985202 Title: libx11 causes kwin to crash on login (over NX protocol) Status in X.Org X server: Confirmed Status in “libxrandr” package in Ubuntu: Fix Released Status in “libxrandr” source package in Precise: Fix Released Bug description: [Impact] xserver crash with kwin and NX [Test Case] install NX server, log in remotely using kde session [Regression Potential] small, patch has been in raring for a couple of weeks now without issues -- This behavior is 100% reproducible. I have freenx-server installed from here: https://launchpad.net/~freenx-team/+archive/ppa And am logging in from a remote machine with the newest nxclient from nomachine.org. What happens is that upon login or shortly thereafter, kwin crashes with a segfault. After restarting, it crashes at regular intervals as well. I reported a bug to the KDE4 tracker: https://bugs.kde.org/show_bug.cgi?id=298370 And it was marked a duplicate of a bug NOT related to NX: https://bugs.kde.org/show_bug.cgi?id=293209 Judging from the backtrace, and from the comments in bug 293209, the problem is related to Xorg, and the people at KDE seem to think that the problem might even be Ubuntu 12.04 specific. So I decided to re- report the bug here and give you pointers to the relevant KDE bugreports. We are really desperate to get Kwin working under NX and are willing to test whatever you like! Many thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libx11-6 2:1.4.99.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 ApportVersion: 2.0.1-0ubuntu4 Architecture: i386 Date: Wed Apr 18 16:18:16 2012 ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) SHELL=/bin/bash SourcePackage: libx11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/985202/+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
