[Desktop-packages] [Bug 1853894] Re: Strange Hang with old SWT Apps
I have tried to create a small application with this issue, but after some updates, i can't seem to be able to reproduce the issue anymore. I suppose this issue can be closed. Sorry for the inconvenience. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 1853894] Re: Strange Hang with old SWT Apps
I don't see how this can be in the Java stack, if it works on LTS but doesn't on later releases. Also, using the "dbus-launch" command solves the issue. I have not been able to make a smaller release yet. I have read of other people with a similar issue: https://askubuntu.com/questions/1184774/some-applications-on- ubuntu-19-10-very-slow-to-start -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: Incomplete Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 1853894] Re: Strange Hang with old SWT Apps
I have also tried to see if this issue arises on PopOS, which it does in the versions after the last LTS. The current PopOS LTS does not have the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: New Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 1853894] [NEW] Strange Hang with old SWT Apps
Public bug reported: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1853894 Title: Strange Hang with old SWT Apps Status in gtk+2.0 package in Ubuntu: New Bug description: I have a weird issue where an old app of mine which is written in Eclipse RCP using SWT. It is an older Eclipse 3.x version. I am running uptodate Ubuntu 19.10, on Ubuntu 18.4 LTS everything works fine. When i start the app after compiling it using the latest Eclipse edition, then when i start the app, first i needed to install libgtk2.0-0. Which i found out using ldd. The app then doesn't start for quite a while. I can't see any errors ore warnings anywhere. Maybe someone can point me in the right area? Anyhow, searching the web i did find a solution: Either i start the app as root, or using the following command: dbus-launch --exit-with-session java -jar MyApp.jar But both are not very helpful as i can't start the app like this from Eclipse to allow for debugging and modifying. And starting as root isn't optimal either. Has anyone got any idea on how i can fix this, or is this perhaps some kind of bug? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgtk2.0-0 2.24.32-4ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 20:34:58 2019 InstallationDate: Installed on 2019-11-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gtk+2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1853894/+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 950005] Re: screen doesn't lock when pressing ctrl+alt+l or using action from system menu
I finally found out what the problem is. gnome-screensave wasn't installed. Sorry for wasting your time, but still, how can this even happen? I just did an aptitude dist-upgrade and I saw that gnome-screensave was reccommended, but not installed. I guess this won't happen on a new installation now, right? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/950005 Title: screen doesn't lock when pressing ctrl+alt+l or using action from system menu Status in “gnome-screensaver” package in Ubuntu: Incomplete Bug description: On Ubuntu precise with all current updates, locking the screen does not work. If I press the lock key combination ctrl+alt+l or use the system menu action "Lock Screen" then nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/950005/+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 841541] Re: "num lock is on" warning remains even after num lock is turned off (thinkpad, numlock status for laptop and external keyboard different)
This is a weird message, as I am on a desktop computer and I have this message in all password fields. My Numlock key must be on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/841541 Title: "num lock is on" warning remains even after num lock is turned off (thinkpad, numlock status for laptop and external keyboard different) Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “gnome-screensaver” source package in Oneiric: Triaged Status in “gnome-screensaver” source package in Precise: Triaged Bug description: Version: 3.1.5-0ubuntu6 Release: 11.10 After fiddling with Num Lock, I noticed that the lock window claimed it was still enabled, and yet it is not. Comments info: "it might be connected with the fact that on (new) Thinkpads there are something like TWO num locks, one is for an external keyboard and the other - for the internal one." Sequence of events: * Turn on Num Lock. * Lock the screen. (On a ThinkPad, I do this by pressing Fn+F2. Whatever option it is that means "lock the screen immediately", I have it turned on.) * Tap a key to bring up the screen-locked/enter-password dialog. * Observe the warning. * Turn off Num Lock. * Observe the warning is still there. * Successfully unlock the screen. * Lock the screen again. * Observe the warning is still there. * [Optional] Unlock the screen. File a bug against gnome-screensaver. Not related to bug #835649, which concerns showing the warning when Num Lock is enabled but not otherwise problematic, e.g. when using a "full-size" (i.e. "has lots of extra keys") keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/841541/+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
