Two problems

2023-08-04 Thread Karel Lucas
Hi all, On a desktop PC on which I have openBSD, I installed KDE. When I start the X-window system, I still see Fvwm, and no KDE. I also want to start the X window system when I start this PC, and that is not yet the case. How can I solve both problems?

Re: Two problems

2023-08-04 Thread Stuart Henderson
On 2023-08-04, Karel Lucas wrote: > > On a desktop PC on which I have openBSD, I installed KDE. When I start > the X-window system, I still see Fvwm, and no KDE. I also want to start > the X window system when I start this PC, and that is not yet the case. > How can I solve both problems? ther

Re: Two problems

2023-08-04 Thread Maja Reberc
On Fri, 4 Aug 2023 16:12:49 +0200 Karel Lucas wrote: > Hi all, > > On a desktop PC on which I have openBSD, I installed KDE. When I > start the X-window system, I still see Fvwm, and no KDE. I also want > to start the X window system when I start this PC, and that is not > yet the case. How can

Re: Two problems

2023-08-06 Thread Daniele B.
Just to pass you some hints. The desktop environment choise is very like any very important personal choise: it is about gui, it is about resources and it is about software manufact (ie, I like C lighter ones). KDE and many Gnome applications are often service and resource usage intensive. Start

Re: Two problems

2023-08-06 Thread Chris Bennett
On Fri, Aug 04, 2023 at 04:12:49PM +0200, Karel Lucas wrote: > > Hi all, > > On a desktop PC on which I have openBSD, I installed KDE. When I start the > X-window system, I still see Fvwm, and no KDE. I also want to start the X > window system when I start this PC, and that is not yet the case. H

Two problems upgrading to 4.9

2011-07-04 Thread Federico Giannici
I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it doesn't seem to work anymore. It's still there but seems to be ignored. If I set it manually by c

Re: Two problems upgrading to 4.9

2011-07-05 Thread Mark Solocinski
On Mon, 04 Jul 2011 10:26:56 +0200, Federico Giannici wrote: I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it doesn't seem to work anymore. It's

Re: Two problems upgrading to 4.9

2011-07-07 Thread Federico Giannici
On 07/05/11 20:37, Mark Solocinski wrote: On Mon, 04 Jul 2011 10:26:56 +0200, Federico Giannici wrote: I have just upgraded my amd64 desktop pc from 4.8 to 4.9. I encountered two problems: 1) I have "mouse.resolution=90" in "/etc/wsconsctl.conf". Since the upgrade it

two problems with the recent X @ i386

2011-08-22 Thread Jan Stary
With today's snapshot, I can no longer kill X with crtl+alt+backspace. Has something changed? Is DontZap turned on by default now? I am not using any config file. Also, the starting X says cwm: config file /home/hans/.cwmrc has errors, not loading but I don't have a ~/.cwmrc

Re: two problems with the recent X @ i386

2011-08-22 Thread Benny Lofgren
On 2011-08-22 17.19, Jan Stary wrote: > With today's snapshot, I can no longer kill X with crtl+alt+backspace. > Has something changed? Is DontZap turned on by default now? I am not > using any config file. Ah, I've experienced the same thing but in an amd64 environment. In my case it started a c

Re: two problems with the recent X @ i386

2011-08-22 Thread Okan Demirmen
On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: > With today's snapshot, I can no longer kill X with crtl+alt+backspace. > Has something changed? Is DontZap turned on by default now? I am not > using any config file. I believe that's fixed in -current. > Also, the starting X says > > cw

Re: two problems with the recent X @ i386

2011-08-22 Thread Amit Kulkarni
> On 2011-08-22 17.19, Jan Stary wrote: >> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >> Has something changed? Is DontZap turned on by default now? I am not >> using any config file. > > Ah, I've experienced the same thing but in an amd64 environment. > > In my case it

Re: two problems with the recent X @ i386

2011-08-23 Thread ropers
On 22 August 2011 17:19, Jan Stary wrote: > With today's snapshot, I can no longer kill X with crtl+alt+backspace. > Has something changed? Is DontZap turned on by default now? I am not > using any config file. I'm completely talking out of my arse here, but I have a strong hunch that this change

Re: two problems with the recent X @ i386

2011-09-11 Thread patrick keshishian
On Mon, Aug 22, 2011 at 8:38 AM, Okan Demirmen wrote: > On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: >> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >> Has something changed? Is DontZap turned on by default now? I am not >> using any config file. > > I believe that'

Re: two problems with the recent X @ i386

2011-09-11 Thread patrick keshishian
On Sun, Sep 11, 2011 at 10:32 AM, patrick keshishian wrote: > On Mon, Aug 22, 2011 at 8:38 AM, Okan Demirmen wrote: >> On Mon 2011.08.22 at 17:19 +0200, Jan Stary wrote: >>> With today's snapshot, I can no longer kill X with crtl+alt+backspace. >>> Has something changed? Is DontZap turned on by d