Bug#818366: synaptic: fails to start under Wayland

Package: synaptic Version: 0.84.6 Followup-For: Bug #818366 Dear Maintainer, I can confirm this on Buster. If Synaptic is started from KDE applications menu when using Wayland, it does not ask for root privileges but starts without privileges instead. It is not very useful in that state. If I

Bug#818366: synaptic: fails to start under Wayland

On Mon, Mar 11, 2019 at 10:00:38PM +0100, Paul Gevers wrote: I am going to raise my question again, if synaptic can't be run on the default desktop in the default login mode, isn't the average user better of if we don't ship synaptic with buster? I think you've got that logic backwards. If the

Bug#818366: synaptic: fails to start under Wayland

Great thank you

Bug#818366: synaptic: fails to start under Wayland

Hi Shengjing, On 09-04-2019 18:01, Shengjing Zhu wrote: > However I want to known if it's too late for buster, given the fact > that synaptic is popular... If it's too late whatever, I'll just stop > here. If somebody comes up with a decent Wayland detection and (also graphical) error message to

Bug#818366: synaptic: fails to start under Wayland

Only when things got broken, more people(like me) are aware of this sad news. On Sun, 17 Mar 2019 08:29:31 +0100 Paul Gevers wrote: > For the reasoning I set out above, it's not the failure I consider the > worst issue here, but the regression without proper error message. It's not the

Bug#818366: synaptic: fails to start under Wayland

Hello everyone, Let me give my opinion, I think that Synaptic is a graphical manager that is important and used a lot, not having synaptic would cause a lot of worries and discontent, removed the part of repair facility that Debian was too big to bring . Why not make a conflict with Wayland

Bug#818366: synaptic: fails to start under Wayland

Hi, On 17-03-2019 03:47, Axel Beckert wrote: > Hi Paul, > > Paul Gevers wrote: >> I am going to raise my question again, if synaptic can't be run on the >> default desktop in the default login mode, isn't the average user better >> of if we don't ship synaptic with buster? > > Huh? What kind of

Bug#818366: synaptic: fails to start under Wayland

Hi Paul, Paul Gevers wrote: > I am going to raise my question again, if synaptic can't be run on the > default desktop in the default login mode, isn't the average user better > of if we don't ship synaptic with buster? Huh? What kind of logic is that? So any X program which doesn't run under

Bug#818366: synaptic: fails to start under Wayland

Hi Trevis, all, On Sun, 10 Mar 2019 20:46:02 +0530 Trevis Schiffer wrote: > Check this commit. > > > Looks like it is fixed on version 0.84.3 The reported failure in one of the recent merged bug reports was for

Bug#818366: synaptic: fails to start under Wayland

On Wed, 16 Mar 2016 08:24:40 -0500 Ryan Colgan wrote: > Package: synaptic > Version: 0.83+b1 > Severity: normal > > Dear Maintainer, > > When attempting to start Synaptic on GNOME Wayland, it fails to start. When > attempting to run as root via sudo from a terminal, the following error >

Bug#818366: synaptic: fails to start under Wayland

Package: synaptic Version: 0.84.3 Followup-For: Bug #818366 I updated to 0.84.3 version and I got these messages in the log when starting Synaptic as user, after being asked the root password: synaptic-pkexec - Unable to init server: Impossible de se connecter : Connexion refusée synaptic-pkexec

Bug#818366: synaptic: fails to start under Wayland

On Wed, 16 Mar 2016 08:24:40 -0500 Ryan Colgan wrote: > Dear Maintainer, > > When attempting to start Synaptic on GNOME Wayland, it fails to start. When > attempting to run as root via sudo from a terminal, the following error > appears: > > ryan@ArchibaldColgan:~$ sudo

Bug#818366: synaptic: fails to start under Wayland

Package: synaptic Version: 0.83+b1 Severity: normal Dear Maintainer, When attempting to start Synaptic on GNOME Wayland, it fails to start. When attempting to run as root via sudo from a terminal, the following error appears: ryan@ArchibaldColgan:~$ sudo synaptic No protocol specified Unable to