Re: startx xauth fails after upgrade to Bullseye 11.3

> my workstation's hostname is the same as my login > username, which is (obviously) also the name of my home directory. > And yet, I've never seen this problem before. > So, there are definitely a few more variables involved in this one. To reproduce, run xauth list $(hostname -f):0 from a

Re: startx xauth fails after upgrade to Bullseye 11.3

On Thu 31 Mar 2022 at 07:30:14 (-0400), Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote: > > I seem to have rediscovered Debian bug 889720 > > xauth crashes when directory name matches host name > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720 > >

Re: startx xauth fails after upgrade to Bullseye 11.3

On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote: > I seem to have rediscovered Debian bug 889720 > xauth crashes when directory name matches host name > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720 > (Feb 2018) > > So, nothing to do with the Bullseye upgrade. > I must

Re: startx xauth fails after upgrade to Bullseye 11.3

I seem to have rediscovered Debian bug 889720 xauth crashes when directory name matches host name https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720 (Feb 2018) So, nothing to do with the Bullseye upgrade. I must have created that directory-matching-hostname in the process of setting up for

Re: startx xauth fails after upgrade to Bullseye 11.3

Larry Doolittle composed on 2022-03-30 19:31 (UTC-0700): > Felix Miata wrote: >> Is the problem avoided if you login via a display manager (gdm, sddm, >> lightdm, >> etc.) instead of using startx? > Beats me. I don't have any software like that installed. You could

Re: startx xauth fails after upgrade to Bullseye 11.3

Felix - Felix Miata wrote: > Is the problem avoided if you login via a display manager (gdm, sddm, lightdm, > etc.) instead of using startx? Beats me. I don't have any software like that installed. Would they run xauth before or after cd'ing to my home directory? - Larry P.S. Sorry

Re: startx xauth fails after upgrade to Bullseye 11.3

Larry Doolittle composed on 2022-03-30 08:57 (UTC-0700): > The xauth segfault is definitely real and > a problem for me. Is the problem avoided if you login via a display manager (gdm, sddm, lightdm, etc.) instead of using startx? -- Evolution as taught in public schools is, like re

Re: startx xauth fails after upgrade to Bullseye 11.3

Esteemed Debian experts and maintainers - On Sun, Mar 27, 2022 at 11:26:37PM -0700, Larry Doolittle wrote: > On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote: > > I just upgraded my first machine from 11.2 to 11.3. > > xauth fails in the context of startx. >

Re: startx xauth fails after upgrade to Bullseye 11.3

Esteemed Debian experts and maintainers - On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote: > I just upgraded my first machine from 11.2 to 11.3. > xauth fails in the context of startx. > Message is > xauth: timeout in locking authority file /home/[redacted]/.Xauth

startx xauth fails after upgrade to Bullseye 11.3

Esteemed Debian experts and maintainers - I just upgraded my first machine from 11.2 to 11.3. xauth fails in the context of startx. Message is xauth: timeout in locking authority file /home/[redacted]/.Xauthority both in the startx console, and if I run "xauth list" in the resulting

Re: Startx works, but sddm/lightdm/xdm doesn't

John Goerzen writes: > But sddm doesn't work. In fact, when it starts, it causes my monitor to > go "no signal". Oddly, though, if I can log in blindly, then once I hit > enter after putting in my password, KDE will come up and work like it > should. > > I also tried lightdm and xdm. Both of

Re: Startx works, but sddm/lightdm/xdm doesn't

On Mon, Feb 28 2022, Felix Miata wrote: >> However, removing modesetting_drv.so from >> /usr/lib/xorg/modules/drivers did. That solved the problem. > >> But it didn't switch to nouveau; it went to fbdev. > > You likely created a new problem. modesetting_drv.so is the default DIX for > AMD, >

Re: Startx works, but sddm/lightdm/xdm doesn't

John Goerzen composed on 2022-02-28 22:11 (UTC-0600): > Interestingly, purging xserver-xorg-video-nouveau didn't change > anything. That means you must have been /using/ the modesetting DIX driver. > However, removing modesetting_drv.so from > /usr/lib/xorg/modules/drivers did. That solved

Re: Startx works, but sddm/lightdm/xdm doesn't

ut it didn't switch to nouveau; it went to fbdev. But, since I also want to boot this drive on other machines that need it, I can't just leave it that way. It also leaves open the question of why it worked fine in startx, or after logging in with sddm, which is darn weird to me. > Try disabling

Re: Startx works, but sddm/lightdm/xdm doesn't

On Mon, Feb 28, 2022, 3:43 PM John Goerzen wrote: > Hi, > > I have a system with a GeForce 1050 Ti on bullseye. > > On this system, if I log in as a regular user and run startx, everything > works fine; KDE Plasma comes up and it's all good. > > But sddm doesn't work.

Re: Startx works, but sddm/lightdm/xdm doesn't

John Goerzen composed on 2022-02-28 15:43 (UTC-0600): > I have a system with a GeForce 1050 Ti on bullseye. > On this system, if I log in as a regular user and run startx, everything > works fine; KDE Plasma comes up and it's all good. > But sddm doesn't work. In fact, wh

Startx works, but sddm/lightdm/xdm doesn't

Hi, I have a system with a GeForce 1050 Ti on bullseye. On this system, if I log in as a regular user and run startx, everything works fine; KDE Plasma comes up and it's all good. But sddm doesn't work. In fact, when it starts, it causes my monitor to go "no signal". Oddly, though

systemctl can not start X, but startx can.

to initialize the NVIDIA graphics device! [ 340.372] (EE) NVIDIA(0): Failing initialization of X screen 0 on the other hand: startx initializes it with no problems. [ 150.685] (--) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:5:0:0 [ 150.685] (--) NVIDIA(0): CRT-0 [ 150.685] (--) NVIDIA(0

Re: is this a bug of startx?

On Sun, Feb 18, 2018 at 03:20:11AM +, Long Wind wrote: > maybe few users still use startx? Depends on where you draw your samples from. If you consider "all Debian users", then you are probably correct. The vast majority of users probably use one of the Display Managers. If

Re: is this a bug of startx?

On Sun 18 Feb 2018 at 03:20:11 (+), Long Wind wrote: > maybe few users still use startx?at first i found some strange problems with > stretchand unable to run X > now i'm able to describe the problemafter i install twm , i can't run > startxthen i create .xinitrc: >

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

Felix Miata composed on 2017-10-17 17:40 (UTC-0400): > Brian composed on 2017-10-17 20:54 (UTC+0100): >> On Tue 17 Oct 2017 at 15:30:36 -0400, Felix Miata wrote: >>> Startx continues to work more or less as always in Mageia, just as in >>> Debian, >>&

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

David Wright composed on 2017-10-21 11:34 (UTC-0500): > On Fri 20 Oct 2017 at 04:42:53 (-0400), Felix Miata wrote: >> It's not resolutions per se, but resolution increases have considerable >> tendency >> to carry higher pixel density, notwithstanding the considerable average >> density >>

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On Fri 20 Oct 2017 at 04:42:53 (-0400), Felix Miata wrote: > David Wright composed on 2017-10-19 17:00 (UTC-0500): > > > On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote: > > >> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 > >> or > >> more applications is

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

David Wright composed on 2017-10-19 17:00 (UTC-0500): > On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote: >> Finding a wanted app to run from a classified tree list of 30 or 40 or 50 or >> more applications is easier for most people than remembering the name and any >> required startup

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On Wed 18 Oct 2017 at 19:22:53 (-0400), Felix Miata wrote: > Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200): > > > I never understood the need for desktop managers. I use Debian since > > hamm and Linux/Unix since 1995. My take is that desktop managers are > > for people more used

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Oct 18, 2017 at 07:22:53PM -0400, Felix Miata wrote: > Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200): > > > I never understood the need for desktop managers. I use Debian since > > hamm and Linux/Unix since 1995. My take is

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

Ionel Mugurel Ciobîcă composed on 2017-10-18 20:47 (UTC+0200): > I never understood the need for desktop managers. I use Debian since > hamm and Linux/Unix since 1995. My take is that desktop managers are > for people more used to microsoft OS'. Why do I need to click on > something when the

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

(or had ever heard of it before today) that might carry some weight with me. Just curious, what are Mageia users expected to use instead of startx if they want to start a traditional X session from a console? Or is that no longer a supported configuration at all? (By traditional, I mean a ~/.xsession

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

> > [ It might be clearer to write "Desktop Environment" (or DE) instead > of "desktop manager" because of the latter's having the same initials > as Display Manager (or DM). ] You are right. > That said, what are the advantages of running a DM in your case

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On Wed 18 Oct 2017 at 20:47:08 (+0200), Ionel Mugurel Ciobîcă wrote: > On 18-10-2017, at 22h 17'14", Richard Hector wrote about "Re: removing of > sddm (debian 9 -kde5) to start in console mode then startx to start kde5" > > > > > > Did they simply t

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On 18-10-2017, at 22h 17'14", Richard Hector wrote about "Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5" > > > > Did they simply throw every window manager under the bus and say "Nope, > > sorry, you gotta run a

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

OK. If I were a Mageia user (or > had ever heard of it before today) that might carry some weight with me. > > Just curious, what are Mageia users expected to use instead of startx if > they want to start a traditional X session from a console? Or is that > no longer a support

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

viation from upstream. Thus, if upstream says something is >> deprecated, Mageia either claims it's deprecated, or is silent on the >> subject. >> Startx continues to work more or less as always in Mageia, just as in Debian, >> though not necessarily perfectly: >

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

regards Stéphane Le Mardi 17 octobre 2017 21h07, Alexander V. Makartsev <avbe...@gmail.com> a écrit : Stephane asked for a help and got it. I also given him the best advice based on my experience with "startx" shell script. "$ sudo systemctl start display-manager.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

> deprecated, Mageia either claims it's deprecated, or is silent on the subject. > > Startx continues to work more or less as always in Mageia, just as in Debian, > though not necessarily perfectly: > https://bugs.mageia.org/show_bug.cgi?id=15662 Not "more or less" in Debia

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

me. >> > https://forums.mageia.org/en/viewtopic.php?f=8=8737 >> So it's deprecated in Mageia GNU/Linux? OK. If I were a Mageia user (or >> had ever heard of it before today) that might carry some weight with me. >> Just curious, what are Mageia u

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

Stephane asked for a help and got it. I also given him the best advice based on my experience with "startx" shell script. "$ sudo systemctl start display-manager.service" is most fail-safe command to start desktop environment from console session on any systemd-adopted d

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

So it's deprecated in Mageia GNU/Linux? OK. If I were a Mageia user (or > had ever heard of it before today) that might carry some weight with me. > > Just curious, what are Mageia users expected to use instead of startx if > they want to start a traditional X session from a console?

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

So it's deprecated in Mageia GNU/Linux? OK. If I were a Mageia user (or > had ever heard of it before today) that might carry some weight with me. > > Just curious, what are Mageia users expected to use instead of startx if > they want to start a traditional X session from a console?

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

might carry some weight with me. Just curious, what are Mageia users expected to use instead of startx if they want to start a traditional X session from a console? Or is that no longer a supported configuration at all? (By traditional, I mean a ~/.xsession or ~/.xinitrc file that contains "exe

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

up, it was deprecated for quite some time. > > Please get a grip and provide a reference. For what is quoted? https://forums.mageia.org/en/viewtopic.php?f=8=8737 Debian has gone to quite some trouble to fit startx into all the changes which have taken place in xorg and the init system. Kudos. -- Brian.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

reference. > On 17.10.2017 19:16, Greg Wooledge wrote: > > On Tue, Oct 17, 2017 at 07:05:13PM +0500, Alexander V. Makartsev wrote: > >> I think "startx" command is deprecated now and you shouldn't use it > >> anymore. > > Nonsense. Many people (including me

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On 10/17/2017 07:39 AM, Greg Wooledge wrote: On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote: Deprecated doesn't mean it doesn't exist or work anymore at all, it means it isn't supported anymore and should not be used. Look it up, it [startx] was deprecated for quite some

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On Tue, Oct 17, 2017 at 07:32:11PM +0500, Alexander V. Makartsev wrote: > Deprecated doesn't mean it doesn't exist or work anymore at all, it > means it isn't supported anymore and should not be used. > Look it up, it [startx] was deprecated for quite some time. Quoting f

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

gt;> I think "startx" command is deprecated now and you shouldn't use it >> anymore. > Nonsense. Many people (including me) use it all the time. Granted, > I don't use KDE. > -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org ⠈⠳⣄

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

On Tue, Oct 17, 2017 at 07:05:13PM +0500, Alexander V. Makartsev wrote: > I think "startx" command is deprecated now and you shouldn't use it > anymore. Nonsense. Many people (including me) use it all the time. Granted, I don't use KDE.

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

OK thank you AlexanderI will try this... bests regards stephane Le Mardi 17 octobre 2017 16h05, Alexander V. Makartsev <avbe...@gmail.com> a écrit : I think "startx" command is deprecated now and you shouldn't use it anymore. Right way to start DE is by starting

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

I think "startx" command is deprecated now and you shouldn't use it anymore. Right way to start DE is by starting display manager service. This command should work in your case:     $ sudo systemctl start sddm.service On 17.10.2017 18:55, Stephane L wrote: > Hi, Alexander >

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

Hi, AlexanderI Want to boot debian 9 in multi user mode (console),then do something then and then to startx kde5/xorg with startx as I do with debian8/kde4 Le Mardi 17 octobre 2017 14h46, Alexander V. Makartsev <avbe...@gmail.com> a écrit : What are you trying to archieve?

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

gt;     $ sudo systemctl set-default graphical.target > > You have to reboot to apply changes. > > > > On 17.10.2017 16:59, Stephane L wrote: >> Hi I have tried to remove sddm from /etc/init.d but it starts always >> with sddm.I want to boot my debian 9 in console

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

want to start DE by default:     $ sudo systemctl set-default graphical.target You have to reboot to apply changes. On 17.10.2017 16:59, Stephane L wrote: Hi I have tried to remove sddm from /etc/init.d but it starts always with sddm.I want to boot my debian 9 in console mode and do start

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

$ sudo systemctl set-default graphical.target You have to reboot to apply changes. On 17.10.2017 16:59, Stephane L wrote: Hi I have tried to remove sddm from /etc/init.d but it starts always with sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as I

Re: removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

ddm from /etc/init.d but it starts always > with sddm.I want to boot my debian 9 in console mode and do startx to > launch kde5 as I do with debian 8 and kde4.does anyone know exactly > how to do that ? -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operatin

removing of sddm (debian 9 -kde5) to start in console mode then startx to start kde5

Hi I have tried to remove sddm from /etc/init.d but it starts always with sddm.I want to boot my debian 9 in console mode and do startx to launch kde5 as I do with debian 8 and kde4.does anyone know exactly how to do that ?

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Mon 19 Jun 2017 at 14:43:08 -0400, Felix Miata wrote: > Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400): > > > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: > . > >> I have a dozen machines with Stretch installed, most with Jessie and/or > >> Sid as > >> well. Only

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

Greg Wooledge composed on 2017-06-19 11:05 (UTC-0400): > On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: . >> I have a dozen machines with Stretch installed, most with Jessie and/or Sid >> as >> well. Only Stretch on host big41 produces the subject problem. . > According to a

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Mon, 19 Jun 2017, Brian wrote: > The same experience as yours on tty1 to tty6. Except a couple of days > ago when I used nouveau.modeset=0 on GRUB's linux line and got what is > in the subject header. Kernel modeset must be enabled non-root X to work, as you found out... -- Henrique

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Mon, Jun 19, 2017 at 11:00:32AM -0400, Felix Miata wrote: > I have a dozen machines with Stretch installed, most with Jessie and/or Sid as > well. Only Stretch on host big41 produces the subject problem. According to a previous message in this thread, it could be triggered by a specific kernel

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

Greg Wooledge composed on 2017-06-19 09:29 (UTC-0400): . > On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: . >> When I try as ordinary user (on host big41), I get the subject message. >> Anyone >> know how to get startx to work in Stretch, either on :0, :1 or :

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Mon 19 Jun 2017 at 09:29:40 -0400, Greg Wooledge wrote: > On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: > > When I try as ordinary user (on host big41), I get the subject message. > > Anyone > > know how to get startx to work in Stretch, e

Re: [Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

On Sun, Jun 18, 2017 at 05:53:43PM -0400, Felix Miata wrote: > When I try as ordinary user (on host big41), I get the subject message. Anyone > know how to get startx to work in Stretch, either on :0, :1 or :2, with or > without a greeter running (multi-user.targer vs. graphical.targe

[Stretch] startx: /bin/sh: 0: Can't open /usr/bin/X; xinit: unable to connect to X server: Connection refused

ser on a virtual terminal via startx. When I try as ordinary user (on host big41), I get the subject message. Anyone know how to get startx to work in Stretch, either on :0, :1 or :2, with or without a greeter running (multi-user.targer vs. graphical.target)? -- "The wise a

Re: stretch, startx impossible

Re, On Sun, Feb 19, 2017 at 10:11:46PM +0100, David Pinson wrote: > Est-ce que ce lien pourrait vous aider ? > https://github.com/dnschneid/crouton/issues/2926 Tkx, déjà vu, mais pas exploitable :-/ -- JFS.

Re: stretch, startx impossible

Le 19/02/2017 à 21:42, JF Straeten a écrit : > Lo, > > > On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote: > > [...] >>> il m'est impossible de lancer startx. [...] >>> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not >>> permitt

Re: stretch, startx impossible

Lo, On Sun, Feb 19, 2017 at 09:20:52PM +0100, maderios wrote: [...] > >il m'est impossible de lancer startx. [...] > >xf86EnableIOPorts: failed to set IOPL for I/O (Operation not > >permitted) [...] > As tu installé xinit? /usr/bin/startx fait partie du paquet xinit Oui

Re: stretch, startx impossible

Le 19/02/2017 à 21:20, maderios a écrit : Bonjour As tu installé xinit? /usr/bin/startx fait partie du paquet xinit oui, du moins il l'ait par défaut jerem.

Re: stretch, startx impossible

On 02/19/2017 01:58 PM, jérémy prego wrote: bonjour à tous, après avoir installé Stretch sur une machine avec le bureau mate, il m'est impossible de lancer startx. Google me donne plein de résultat mais c'est trop vieux et les commande ne fonctionnent plus sur ma stretch. L'erreur que j'ai est

stretch, startx impossible

bonjour à tous, après avoir installé Stretch sur une machine avec le bureau mate, il m'est impossible de lancer startx. Google me donne plein de résultat mais c'est trop vieux et les commande ne fonctionnent plus sur ma stretch. L'erreur que j'ai est la suivante: [82.260

Re: veeger is infected ...startx again

On 10/17/2016 06:48 PM, Felix Miata wrote: Ric Moore composed on 2016-10-17 17:47 (UTC-0400): Felix Miata wrote: Did you consider trying with both NVidia and Nouveau purged? Apparently, development focus has been migrating into the server-integrated modesetting driver:

Re: veeger is infected ...startx again

Ric Moore composed on 2016-10-17 17:47 (UTC-0400): Felix Miata wrote: Did you consider trying with both NVidia and Nouveau purged? Apparently, development focus has been migrating into the server-integrated modesetting driver:

Re: Fwd: Re: veeger is infected ...startx again

On 17/10/16 05:48 PM, Ric Moore wrote: On 10/17/2016 02:43 PM, Felix Miata wrote: Ric Moore composed on 2016-10-17 14:25 (UTC-0400): I finally went ape and re-installed from the latest stretch build. Initially, with the nouveau driver, XFCE$ synaptic (and others) drop down menus worked. I

Fwd: Re: veeger is infected ...startx again

On 10/17/2016 02:43 PM, Felix Miata wrote: Ric Moore composed on 2016-10-17 14:25 (UTC-0400): I finally went ape and re-installed from the latest stretch build. Initially, with the nouveau driver, XFCE$ synaptic (and others) drop down menus worked. I installed nvidia-driver and it installed

Re: veeger is infected ...startx again

Ric Moore composed on 2016-10-17 14:25 (UTC-0400): I finally went ape and re-installed from the latest stretch build. Initially, with the nouveau driver, XFCE$ synaptic (and others) drop down menus worked. I installed nvidia-driver and it installed everything related to nvidia. Rebooted and

Re: veeger is infected ...startx again

On 10/10/2016 08:49 AM, Charlie Kravetz wrote: It sounds like GTK3 themes is taking over. I had a similar situation I finally went ape and re-installed from the latest stretch build. Initially, with the nouveau driver, XFCE$ synaptic (and others) drop down menus worked. I installed

Re: veeger is infected ...startx again

icks in, as all the monitors come to life, the harddrive is checked and >then I get the black screen and mouse cursor which is active and moves >with movement of the mouse. Buggers. What package should I file a >bugreport against?? If I log into a terminal and issue "startx", >

Re: veeger is infected ...startx again

is active and moves with movement of the mouse. Buggers. What package should I file a bugreport against?? If I log into a terminal and issue "startx", everything comes up normally into XFCE4 desktop. Synaptic menus still refuse to drop down. Thanks all, Ric -- My father, Victor Moore (Vic) u

Re: veeger is infected ...startx again

. Login / greeter is~ still~ broken. Maybe I need an ASCII greeter with blinking X's for the outline?? startx works for now. :) Synaptic drop down menus are broke again. Office drop down menus thankfully DO work. A new one is that background selection greys out source directory selection, while Thunar

Re: veeger is infected ...startx again

On 10/01/2016 12:49 PM, Ric Moore wrote: ... humans are infecting Veeger. I figured I'd fix the display manager problem with a clean install. Here's the fun part that gives me the giggles: I downloaded the testing DVD to install clean from, whilst thinking it would be stretch or sid. Best laid

Re: veeger is infected ...startx again

On Sun, 2 Oct 2016, Liam O'Toole wrote: At the risk of stating the obvious ... an 'apt-get update' is required first. Stating the obvious is a dirty job, but someone has to do it. I'm trying to make a Pat 'n Mike joke out of this, but the thing eludes me. -- IMPORTANT: This email is

Re: veeger is infected ...startx again

On 2016-10-02, Bob Bernstein wrote: > On Sat, 1 Oct 2016, Ric Moore wrote: > >> Surprise, my sources list reflected Jessie, not Stretch or >> Sid. I FIXED that. > > Did you run an 'apt-get dist-upgrade' after making changes to > sources.list? > > Hang in there. > At

Re: veeger is infected ...startx again

On Sat, 1 Oct 2016, Ric Moore wrote: Surprise, my sources list reflected Jessie, not Stretch or Sid. I FIXED that. Did you run an 'apt-get dist-upgrade' after making changes to sources.list? Hang in there. -- IMPORTANT: This email is intended for the use of the individual addressee(s)

Re: veeger is infected ...startx again

Erwan David wrote: > You'd better explain what you call "veeger" nobody will understand > your problem. I think he means "V'ger", which would be a reference to the first Star Trek Movie. S! -- Sigmentation fault. Core dumped.

Re: veeger is infected ...startx again

Le 01/10/2016 à 21:49, Ric Moore a écrit : > ... humans are infecting Veeger. I figured I'd fix the display manager > problem with a clean install. Here's the fun part that gives me the > giggles: I downloaded the testing DVD to install clean from, whilst > thinking it would be stretch or sid.

veeger is infected ...startx again

... humans are infecting Veeger. I figured I'd fix the display manager problem with a clean install. Here's the fun part that gives me the giggles: I downloaded the testing DVD to install clean from, whilst thinking it would be stretch or sid. Best laid plans of mice. I rebooted upon

veeger is infected ...startx again

-- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html

Re: Login impossible/ startx ne demarre pas/Xauth timeout

. Startx ne fonctionnait toujours pas mais avec un message different: user not authorized to start X... ( ou qqchose du genre) du coup j'ai reessaye le login et cela a marché. Cordialement Le 14 févr. 2016 12:04, "Jean-Michel OLTRA" <jm.oltra.antis...@espinasse.net> a écrit :

Re: Login impossible/ startx ne demarre pas/Xauth timeout

Bonjour, Le samedi 13 février 2016, dfertin a écrit... > Résolu Mais encore…? -- jm

Login impossible/ startx ne demarre pas/Xauth timeout

Bonjour, Je viens d'installer debian sur un pc lap top neuf. Tout fonctionnaitnickel mais j'ai laisser le Pcen veille la nuit. Depuis je ne peux plus me logger normalement. En mode recovery, root peut executer startx. Lorsque l'utilisateur dfertin essaye de lancer startx, j'obtiens le message

Re: Login impossible/ startx ne demarre pas/Xauth timeout

Résolu

Re: Can't startx as normal user

On Tue, 2015-12-01 at 22:23 -0300, Draco Metallium(Rodrigo S. Cañibano) > > The NEWS entry should have been picked up by apt-listchanges: > > I must have missed it. Thanks! Looks like it was added after the change was made, so it's possible that you made the upgrade before it was added. --

Re: Can't startx as normal user

On 1 December 2015 at 16:47, Sven Arvidsson wrote: > The NEWS entry should have been picked up by apt-listchanges: I must have missed it. Thanks!

Re: Can't startx as normal user

On Mon, 2015-11-30 at 19:20 -0300, Draco Metallium(Rodrigo S. Cañibano) wrote: > It could be that, since I don't have systemd, nor systemd-shim > installed (I just checked again). > > I had to install xserver-xorg-legacy, just as Harald Dunkel > suggested. > > Should't apt-get have warned me

Re: Can't startx as normal user

On 30 November 2015 at 06:10, Ansgar Burchardt <"Ansgar Burchardt"@43-1.org> wrote: > which looks like some DBus policy forbids Xorg to talk to logind. Xorg > does so in order to get access to devices w/o being setuid root since > recently. It could be that, since I don't have systemd, nor

Re: Can't startx as normal user

If you are using startx/xinit: Try installing xserver-xorg-legacy. I had the same problem. Good luck Harri

Re: Can't startx as normal user

"Draco Metallium(Rodrigo S. Cañibano)" <draco@gmail.com> writes: > No only root can run startx. If a user tries the following error appears: > > "(EE) AddScreen/ScreenInit failed for driver 0" The first error in the log you attached is: > [ 4203.0

Can't startx as normal user

Hi! Today I made a dist-upgrade and everything worked fine until I rebooted. No only root can run startx. If a user tries the following error appears: "(EE) AddScreen/ScreenInit failed for driver 0" (I will attach the full log). Does anyone have any idea what might be

Re: Can't startx as normal user

On Mon, 30 Nov 2015 01:48:40 -0300 Draco Metallium(Rodrigo S. Cañibano) sent: > Today I made a dist-upgrade and everything worked fine until I > rebooted. > > No only root can run startx. If a user tries the following error > appears: > > "(EE) AddScreen/ScreenInit fa

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

On Vi, 21 mar 14, 10:34:03, Darac Marjal wrote: On Fri, Mar 21, 2014 at 11:46:38AM +0200, Andrei POPESCU wrote: On Vi, 21 mar 14, 09:52:09, Gian Uberto Lauri wrote: You can access the console X was started from even when the machine is locked. Seriously? I'd find that to be a

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

On 2014-03-25 12:08:12 +0200, Andrei POPESCU wrote: Alt-SysRq-F is disabled on sid: mar 25 12:03:28 sid kernel: SysRq : This sysrq operation is disabled. But what if someone logs in, uses all the memory left (possibly not even in a malicious way) so that this triggers the OOM killer, and the

Re: Security Implications of running startx from command line - was Re: Startx: was Great Debian experience

On 2014-03-23 21:06:55 +0100, Jörg-Volker Peetz wrote: Seems I'm a little bit old-fashioned ;-) According to the man-page Xsession(5) the system scripts take care of using a log-file, given that you indeed don't have ~/.xinitrc . So maybe the man-page of startx(1) has to be updated, since

  1   2   3   4   5   6   7   8   9   10   >