[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Hi Alkis, You are absolutely correct. I just removed the firefox snap and installed it through the mozillateam PPA instead, and indeed, gdebi ends up parented by init when launched through Firefox's downloads, just like what I saw with Chrome, and the same issue is reproducible (my patch fixes it). So snap has been hiding the problem. Thanks for pointing that out! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
Feedback on the patch has been addressed and it has been resubmitted. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
I take back what I said in my previous comment. This does still affect 23.04, at least with Ubuntu MATE and Chrome. It all depends on how the processes are parented, which changes based on how you launch Chrome. If I launch Chrome from the MATE menu, it gets parented to "systemd --user" and this problem doesn't occur. If I launch Chrome by clicking its icon in mate-panel, it gets parented to mate-panel instead, which follows a parenting chain of mate-session -> lightdm -> init. This difference also affects how gdebi ends up being parented when Chrome launches it from its downloads. gdebi ends up parented to init if I try to open a Chrome download from Chrome after I've launched Chrome from the panel, and this problem occurs. The same can be said about the "setsid gdebi-gtk package.deb" command. If I start MATE Terminal from the MATE menu and run that command, it works fine. If I start MATE Terminal from mate-panel and run the same command, it immediately exits and I get the "Refusing to render service to dead parents." message instead. I suspect this difference explains why some people haven't been able to reproduce this problem but others have. I will point out that Firefox, regardless of how it's launched, seems to not be affected anymore. gdebi always ends up parented by systemd when Firefox launches it. Clearly there is still value in fixing this in gdebi. I'll look into addressing Julian's feedback and resubmitting the fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
It appears that this bug no longer affects newer versions of Ubuntu. It's unclear to me exactly how this change happened, but in 23.04, running "setsid pkexec echo hello" for example no longer prints the "Refusing to render service to dead parents." message, and instead works correctly. The original reproduction steps with Firefox/Chrome also don't cause the problem anymore. The difference seems to be that when you run pkexec like that, it now gets parented to "systemd --user" in modern Ubuntu versions instead of init, so pkexec is no longer unhappy about it. I can still spend some time tweaking the merge request as per Julian's feedback if there is any chance that this would result in new builds of gdebi for the older affected versions like 20.04 and 22.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
Wow, thanks for responding so quickly! That's great to hear. FWIW, to this day, Ubuntu MATE 23.04 is still using the gtk2 style plugin (export QT_QPA_PLATFORMTHEME=gtk2 in /etc/profile.d) so indeterminate progress bars have been broken in Ubuntu MATE for years. I think there would be value in at least patching this in Ubuntu's build or something... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1906138] Re: Indeterminate Qt progress bars don't display properly in 20.04
I finally found some time to look further into this, it appears to be an upstream problem with qtstyleplugins. The logic in the gtk2 plugin (used by Ubuntu MATE by default) doesn't animate indeterminate progress bars if QT_NO_ANIMATION is defined, yet it seems to be intentionally defined to disable animation for some reason: https://code.qt.io/cgit/qt/qtstyleplugins.git/commit/src/plugins/styles/gtk2/gtk2.pro?id=102da7d50231fc5723dba6e72340bef3d29471aa Removing DEFINES += QT_NO_ANIMATION from gtk2.pro fixes the problem and allows the indeterminate progress bars to animate properly. ** Also affects: qtstyleplugins-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1906138 Title: Indeterminate Qt progress bars don't display properly in 20.04 Status in qtbase-opensource-src package in Ubuntu: New Status in qtstyleplugins-src package in Ubuntu: New Bug description: In Ubuntu MATE 20.04, a Qt program with an indeterminate progress bar (meaning its minimum and maximum values have both been set to zero) does not display properly. It is supposed to animate in a way that shows that something is happening with an unknown time remaining. Instead, it sits still with its progress bar showing approximately 25 to 30% progress. To test this, make a simple Qt program with a QProgressBar in the main window, and add these lines to the constructor of the main window: ui->progressBar->setMinimum(0); ui->progressBar->setMaximum(0); This problem is not present in standard Ubuntu 20.04. Standard Ubuntu correctly animates the indeterminate progress bar. It's unclear to me which package is at fault, but it seems to be something specific to Ubuntu MATE because standard Ubuntu 20.04 doesn't have this problem. Ubuntu MATE 18.04 also has this problem with Qt 5. With Qt 4 it doesn't have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1906138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854588] Re: gdebi-gtk calls pkexec inappropriately
I have no idea what I'm doing here in terms of submission processes, but I attempted to submit a patch for this issue: https://code.launchpad.net/~macg3/ubuntu/+source/gdebi/+git/gdebi/+merge/414211 I suspect I may have done something wrong in the submission process because "git-ubuntu import" is listed as the code reviewer. It was really confusing because there was also a bzr project for this package that is outdated, and it appears it has been moved to Git. Anyway, this patch fixes the issue by adding a separate python script that acts as the parent process for pkexec. Special thanks to Alkis Georgopoulos for all of the info provided above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1854588 Title: gdebi-gtk calls pkexec inappropriately Status in gdebi: Confirmed Status in gdebi package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu with gdebi-gtk installed 2. Open Firefox 3. Visit some site with deb-package download link or use direct link like https://github.com/jgm/pandoc/releases/download/2.9.2.1/pandoc-2.9.2.1-1-amd64.deb 4. Proceed with file downloading 5. In Firefox select Library → Downloads, click on downloaded deb-file Expected results: * gdebi-gtk is opened, the package installs normally after users clicks Install button Actual results: * gdebi-gtk is opened, the package is not installed because of vanishing of gdebi-gtk window just after clicking Install button Before anyone says this bug already exists... it doesn't (at least as far as I can see). It's just that a lot of similar bugs do/did exist where people have also experienced the same symptoms (of gdebi-gtk vanishing upon clicking 'Install'). So yes this is the same symptoms, but it must be a different cause as the circumstances are different and doesn't have the same resolution. The meat of it... Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or with Chrome if you installed that) go to any site that offers a .deb package and either... a) choose to open it directly from the browser (rather than saving it to 'Downloads' folder) b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that file from within the browser itself. You should find that gdebi-gtk appears but vanishes the moment you click 'Install' without a prompt for a password, an explanation or the package actually getting installed. This bug has existed since the beginning of Ubuntu 18.04 however it's been largely confused with other similar bugs. I've had it on half a dozen machines and confirmed it exists with IRC users on #ubuntu-mate of freenode. However with *this* bug (compared to others) gdebi-gtk works perfectly fine if you run it from the terminal or just double click the .deb package from your file manager. It's the kind of bug which if you're a hardened desktop Linux user, you'd just work around it... But if you're a novice and you can't get a simple thing like Teamviewer installed (which is a .deb, and a thing I might ask someone to do over the phone to try to help them) you likely get fed up and re-install Windows :S Any input on this would be brilliant as I can't seem to get any logs/output. ~lantizia To manage notifications about this bug go to: https://bugs.launchpad.net/gdebi/+bug/1854588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363723] [NEW] QTextEdit jumps to keyboard cursor when losing focus
Public bug reported: Ubuntu Version: Ubuntu 14.04.1 LTS libqt5gui5 version: 5.2.1+dfsg-1ubuntu14.2 I am running a stock install of Ubuntu 14.04.1, fully updated as of this writing. If you are using the ibus input method (chosen by default in Ubuntu), there is a problem that can cause QTextEdit to lose its scroll position when it loses focus. I first noticed this inside of Qt Creator but it actually affects all Qt 5 programs. Here are the steps to reproduce it: - Fill a QTextEdit (for example, a Qt Creator editor window) with enough text so that there is a scrollbar. - Make sure the text insertion cursor is at the bottom of the file. - With your mouse wheel, scroll up so that the text insertion cursor is no longer visible on-screen. - Now click on the containing window's title bar, or choose an item from a menu, or click on another widget in the window. Just something to cause focus to change. What I expect to happen: Nothing should happen to the QTextEdit's scroll position. It should stay where it is. What actually happens: The QTextEdit scrolls down so the text insertion cursor is visible, as if I had typed a character. This is actually a known bug in the ibus input method plugin (libibusplatforminputcontextplugin.so), which is installed as part of Ubuntu's libqt5gui5 package: https://bugreports.qt-project.org/browse/QTBUG-40755 A fix was committed upstream to the qtbase 5.4 branch: https://qt.gitorious.org/qt/qtbase/commit/e5f3a25253263b67f3f211d76ed76ddc2298916e I don't know about what the release schedule looks like for trusty and Qt, but I'd like to respectfully request that this patch somehow makes its way into 14.04 for my own sanity while working inside of Qt Creator. :-) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1363723 Title: QTextEdit jumps to keyboard cursor when losing focus Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: Ubuntu Version: Ubuntu 14.04.1 LTS libqt5gui5 version: 5.2.1+dfsg-1ubuntu14.2 I am running a stock install of Ubuntu 14.04.1, fully updated as of this writing. If you are using the ibus input method (chosen by default in Ubuntu), there is a problem that can cause QTextEdit to lose its scroll position when it loses focus. I first noticed this inside of Qt Creator but it actually affects all Qt 5 programs. Here are the steps to reproduce it: - Fill a QTextEdit (for example, a Qt Creator editor window) with enough text so that there is a scrollbar. - Make sure the text insertion cursor is at the bottom of the file. - With your mouse wheel, scroll up so that the text insertion cursor is no longer visible on-screen. - Now click on the containing window's title bar, or choose an item from a menu, or click on another widget in the window. Just something to cause focus to change. What I expect to happen: Nothing should happen to the QTextEdit's scroll position. It should stay where it is. What actually happens: The QTextEdit scrolls down so the text insertion cursor is visible, as if I had typed a character. This is actually a known bug in the ibus input method plugin (libibusplatforminputcontextplugin.so), which is installed as part of Ubuntu's libqt5gui5 package: https://bugreports.qt-project.org/browse/QTBUG-40755 A fix was committed upstream to the qtbase 5.4 branch: https://qt.gitorious.org/qt/qtbase/commit/e5f3a25253263b67f3f211d76ed76ddc2298916e I don't know about what the release schedule looks like for trusty and Qt, but I'd like to respectfully request that this patch somehow makes its way into 14.04 for my own sanity while working inside of Qt Creator. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1363723/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp