Re: KDE peculiarities and questions
# update-alternatives --list x-cursor-theme only shows one cursor theme installed: /usr/share/icons/Industrial/cursor.theme. I think that this theme is the default Gnome cursor theme, because when I tried to remove it aptitude wanted to remove Gnome-desktop-environment as well. Of course, what I wanted was NO cursor theme at all, only the default system cursor themes. So I removed both the industrial cursor theme and Gnome-desktop environment and thereby got what I wanted. Hooray! Previously I had removed the desktop-base package, which did not make any difference, at least to the login-manager and the cursor style. Since desktop-base is used by both KDE and Gnome I reinstalled it. In doing so aptitude also insisted in installing three other packages: kdebase-dbg, kdelibs-dbg and qt-x11-free-dbg. I am not sure what all these do, no harm, I hope. One thing that did appear was a blue icon on the panel which looks like a squashed half jelly bean. It is something called SuperKarumba. Useful? Another discovery. Days ago I wanted to change my login manager from Gnome to KDE, but it did not work. This morning when I booted my desktop this morning to my amazement and surprise the KDE login manager appeared! I wonder what I had done in the meantime to deserve this prise. Regards, Ken Heard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
Kent West wrote: Log into an ordinary terminal, and stop/kill any X-related processes. (Use ps ax and kill as necessary, or use other means such as /etc/init.d/kdm stop). Earlier I had purged xserver-xorg and all its dependencies and reinstalled it. No change. Then I logged in as directed. ps ax produced a long list of processes, none of which seemed to me to be X-related. In view of my knowledge level, the fact that I could not recognize any of them as such that does not mean they weren't. Jobs returned no jobs; so there was nothing for kill to kill. I stopped kdm, with the effect that terminal F7 was blank. Now as a normal (non-root) user, run startx. What happens? I logged in as my user and ran startx. It returned three lines: xauth: creating new authority file /home/ken/.serverauth.3110 /etc/X11/X is not executable xinit: Server error However, as root user I was able to run startx. KDE opened in terminal F7 logged in as root without my intervention. Also check /var/log/Xorg.0.log (or /var/log/XFree86.0.log) for clues, especially lines containing EE. My user x-server-errors log file was empty. I could find nothing untoward in either dmesg or syslog, except the following line in the latter, which really does not tell us anything we do not already know. Feb 13 12:02:11 LAP kdm: :0[2736]: Session /etc/kde3/kdm/Xsession execution failed: Permission denied The only other specific error messages I could find were in kdm.log. There was one line: (EE) AIGLX: Screen 0 is not DRT capable. There were three other (EE) lines saying that a Synaptic touchpad could not be found and therefore was not activated; but the Toshiba Tecra 8000 uses an Accupoint instead of a touchpad. To make matters worse, an hour later I booted my desktop and met with the same result: a fail-safe terminal emulator and a hung machine. This failure happened to a P4 box on which I had installed Sarge and KDE in June 2005 when Sarge first came out. Other than a few glitches encountered on initial installation, it has worked perfectly ever since. Made the same checks as before. No error reports in dmesg or kdm.log. There were two lines near the end of syslog, as follows: Feb 13 14:00:22 localhost kdm_greet[2792]: Can't open default user face Feb 13 14:00:28 localhost kdm: :0[2797]: Session /etc/kde3/kdm/Xsession execution failed: Permission denied Run ifconfig and see if you have an expected IP address; my first suspicion is that zeroconf got installed; it tends to cause problems with networking. Ifconfig only reports the loop back IP address. The IP address assigned by the gateway, 192.168.0.114, was not reported by ifconfig, presumably because the operating system cannot connect to the network. As I have managed to remove all my data from the Sarge box, fixing it is not my priority. Getting the laptop working is. As I have not yet any data on it, the only thing I can think of to do is to start the installation all over again, this time using Etch RC2. As for the P4 box with Sarge, I can think of nothing better to do and wait until Etch becomes stable. Regards, Ken Heard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
Ken Heard wrote: Kent West wrote: Now as a normal (non-root) user, run startx. What happens? I logged in as my user and ran startx. It returned three lines: xauth: creating new authority file /home/ken/.serverauth.3110 /etc/X11/X is not executable xinit: Server error However, as root user I was able to run startx. KDE opened in terminal F7 logged in as root without my intervention. I suspect your /etc/X11/Xwrapper.config file is set to allow root only. Either edit that file manually to: [EMAIL PROTECTED]:/home/westk: sudo cat /etc/X11/Xwrapper.config # Xwrapper.config (Debian X Window System server wrapper configuration file) # # This file was generated by the post-installation script of the x11-common # package using values from the debconf database. # # See the Xwrapper.config(5) manual page for more information. # # This file is automatically updated on upgrades of the x11-common package # *only* if it has not been modified since the last upgrade of that package. # # If you have edited this file but would like it to be automatically updated # again, run the following command as root: # dpkg-reconfigure x11-common allowed_users=console nice_value=-10 or better yet, do as the file says and run dpkg-reconfigure x11-common and change the setting that way. The following issue should really be broken out into a different thread: Run ifconfig and see if you have an expected IP address; my first suspicion is that zeroconf got installed; it tends to cause problems with networking. Ifconfig only reports the loop back IP address. The IP address assigned by the gateway, 192.168.0.114, was not reported by ifconfig, presumably because the operating system cannot connect to the network. What happens when you run /etc/init.d/networking restart? What does your /etc/network/interfaces file look like? PS. No need to CC: me; I'm subscribed to the list. -- Kent West http://kentwest.blogspot.com http://kentwest.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
Kent West wrote: I suspect your /etc/X11/Xwrapper.config file is set to allow root only. or better yet, do as the file says and run dpkg-reconfigure x11-common and change the setting that way. I ran dpkg-reconfigure x11-common. When the option to set allowed users appeared, the option Console Users Only was highlighted; so I assume that x11-common was already configured to that option. In any event I hit Ok. Nice was set to 0; I changed it as you suggested, to -10. I then shut the machine off and did a cold boot. No change; problem persists. With respect to my other desktop's not being able to connect to the network, I am starting another thread called My Sarge box no longer connects to the network. You will recall however that the sudden inability to run the xserver occurred on my Sarge desktop the same day (Feb 7) as it occurred on my laptop. So I will keep on this thread that particular problem for both computers. (For the time being I am using a third desktop on which after that date I installed Etch RC1 as the only operating system thereon.) Sarge of course does not have X-common; so I ran dpkg-reconfigure xfree86, which returned: System startup links for /etc/init.d/xfree86-common already exist. Setting up X server socket directory /tmp/.X11-unix...done. Setting up ICE socket directory /tmp/.ICE-unix...done. I am not sure whether that information is of any help. Regards, Ken Heard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
Ken Heard wrote: Kent West wrote: I suspect your /etc/X11/Xwrapper.config file is set to allow root only. or better yet, do as the file says and run dpkg-reconfigure x11-common and change the setting that way. I ran dpkg-reconfigure x11-common. When the option to set allowed users appeared, the option Console Users Only was highlighted; so I assume that x11-common was already configured to that option. In any event I hit Ok. Nice was set to 0; I changed it as you suggested, to -10. I then shut the machine off and did a cold boot. No change; problem persists. I'd manually look in /etc/X11/Xwrapper.config to make sure it's right; sometimes the dpkg-reconfigure routine doesn't take. The three legal options for that line, according to man Xwrapper.config, are rootonly, console, and anybody. For most situations, you'd want console. I logged in as my user and ran startx. It returned three lines: xauth: creating new authority file /home/ken/.serverauth.3110 /etc/X11/X is not executable xinit: Server error What is the output of ls -lh /etc/X11/X? [EMAIL PROTECTED]:/home/westk: ls -lh /etc/X11/X lrwxrwxrwx 1 root root 13 2006-04-28 12:11 /etc/X11/X - /usr/bin/Xorg (Yours will likely be slightly different.) Then, what is the output of ls -lh /usr/bin/Xorg? [EMAIL PROTECTED]:/home/westk: ls -lh /usr/bin/Xorg -rwxr-xr-x 1 root root 1.6M 2007-02-03 17:30 /usr/bin/Xorg You will recall however that the sudden inability to run the xserver occurred on my Sarge desktop the same day (Feb 7) as it occurred on my laptop. So I will keep on this thread that particular problem for both computers. Sarge of course does not have X-common; so I ran dpkg-reconfigure xfree86, which returned: System startup links for /etc/init.d/xfree86-common already exist. Setting up X server socket directory /tmp/.X11-unix...done. Setting up ICE socket directory /tmp/.ICE-unix...done. This brings to recollection a vague memory; seems like a year or two ago there was a problem with permissions in one or more of the Debian branches. What do these files look like? [EMAIL PROTECTED]:/home/westk: ls -lha /tmp snips drwxrwxrwt 2 root root 1.0K 2007-02-08 10:22 .ICE-unix drwxrwxrwt 2 root root 1.0K 2007-02-08 10:21 .X11-unix Also, what do the perms on your /tmp directory look like? [EMAIL PROTECTED]:/home/westk: ls -lhd /tmp drwxrwxrwt 14 root root 4.0K 2007-02-13 17:18 /tmp -- Kent West http://kentwest.blogspot.com http://kentwest.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
Kent West wrote: I'd manually look in /etc/X11/Xwrapper.config to make sure it's right; sometimes the dpkg-reconfigure routine doesn't take. The three legal options for that line, according to man Xwrapper.config, are rootonly, console, and anybody. For most situations, you'd want console. Did so; returns allowed_users=console and nice_value=-10. What is the output of ls -lh /etc/X11/X? [EMAIL PROTECTED]:/home/westk: ls -lh /etc/X11/X lrwxrwxrwx 1 root root 13 2006-04-28 12:11 /etc/X11/X - /usr/bin/Xorg (Yours will likely be slightly different.) Mine is exactly the same as yours, except for the date. Then, what is the output of ls -lh /usr/bin/Xorg? [EMAIL PROTECTED]:/home/westk: ls -lh /usr/bin/Xorg -rwxr-xr-x 1 root root 1.6M 2007-02-03 17:30 /usr/bin/Xorg Again, exactly the same as yours, except for the date. You will recall however that the sudden inability to run the xserver occurred on my Sarge desktop the same day (Feb 7) as it occurred on my laptop. So I will keep on this thread that particular problem for both computers. Sarge of course does not have X-common; so I ran dpkg-reconfigure xfree86, which returned: System startup links for /etc/init.d/xfree86-common already exist. Setting up X server socket directory /tmp/.X11-unix...done. Setting up ICE socket directory /tmp/.ICE-unix...done. This brings to recollection a vague memory; seems like a year or two ago there was a problem with permissions in one or more of the Debian branches. What do these files look like? [EMAIL PROTECTED]:/home/westk: ls -lha /tmp snips drwxrwxrwt 2 root root 1.0K 2007-02-08 10:22 .ICE-unix drwxrwxrwt 2 root root 1.0K 2007-02-08 10:21 .X11-unix On the Laptop with Etch, once again the same, except for the dates. Mine are dated today. Also, what do the perms on your /tmp directory look like? [EMAIL PROTECTED]:/home/westk: ls -lhd /tmp drwxrwxrwt 14 root root 4.0K 2007-02-13 17:18 /tmp On the laptop, the same, except for the time and the number following the perms is 5 instead of 14. Regards, Ken Heard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: X doesn't start [Was: KDE peculiarities and questions]
On Tue, Feb 13, 2007 at 05:24:24PM -0600, Kent West wrote: Ken Heard wrote: xauth: creating new authority file /home/ken/.serverauth.3110 /etc/X11/X is not executable xinit: Server error This brings to recollection a vague memory; seems like a year or two ago there was a problem with permissions in one or more of the Debian branches. What do these files look like? [EMAIL PROTECTED]:/home/westk: ls -lha /tmp snips drwxrwxrwt 2 root root 1.0K 2007-02-08 10:22 .ICE-unix drwxrwxrwt 2 root root 1.0K 2007-02-08 10:21 .X11-unix Also, what do the perms on your /tmp directory look like? [EMAIL PROTECTED]:/home/westk: ls -lhd /tmp drwxrwxrwt 14 root root 4.0K 2007-02-13 17:18 /tmp which brings to mind a problem that cropped up a bunch in the xfree86-xorg transition... ugh, my poor brain. Seems like there were a bunch of posts about people losing X with similar errors. I'll see if I can grep it out of the archives. A signature.asc Description: Digital signature
Re: KDE peculiarities and questions
Kent West wrote: Ken Heard wrote: I have KDE installed on all three of the boxes my spouse and I use. The box with Sarge installed, a P4 desktop, uses KDE 3.3.?; whereas the other two, one a P3 desktop and the other a P2 Tecra 8000 Toshiba laptop, have Etch, which uses KDE 3.5.5. The latter has some nice new features, but I have also run into four peculiarities. 1. On the P3 desktop only, the panel displays the taskbar three times. Once is surely enough. I tried to fix it by purging KDE and reinstalling it, to no avail. Any ideas on what I can do to remove this redundancy? Does this happen for all users, or just one user? If just one user, I'd rename the ~/.kde? directory for that user and restart KDE. I only have one user so far on this particular desktop computer. In any event it was Ben Breslauer who showed me the way on question 1. I had not realized that the taskbar was an applet. I somehow got the idea that it was integral to the panel; probably because one is on the panel by default, I think. I had installed other applets on the panel; I must have inadvertently installed two more taskbars in addition to the default one. It was easy to remove the two redundant ones once I knew how they got there. 3. On both the laptop and desktop I seem to be stuck with the Gnome login manager. Selecting options in the System AdministrationLogin Manager of the KDE control manager are not implemented. Is there file somewhere I can substitute the KDE login manager for the Gnome one? Try aptitude install kdm and/or dpkg-reconfigure kdm. Or aptitude purge gdm. I have already made kdm the default display manager. Which is what the above commands should allow you to do. How did you accomplish this? In the KDE Control Panel stuff? The behavour described in my questions two and three may be due to the same cause. I think that if gdm, and possibly other parts of the Gnome desktop environment, remain unpurged from a box where KDE is preferred, some Gnome applications override their KDE counterparts. On my laptop I had purged all Gnome apps and I think that only after the purge was I able to use other mouse cursor themes rather than the one Gnome mandates. On the laptop however I was still presented with the Gnome login manager rather than KDE's; it had that Gnomial look about it. I say I think because since my laptop gui hung I have been unable to use it. I am consequently reluctant to experiment further on the computer I had hurriedly to install Etch RC1 on so that I could have one computer at least operational. I had described the problem with the laptop in another post I made to the list yesterday. Unfortunately nobody has (yet?) answered it. I hope somebody does, as I am really screwed up if I cannot get at least the laptop working SOON. I have copied that post below. Regards and thanks, Ken Heard Toronto A few weeks ago I installed Etch RC1 on a Toshiba Tecra 8000 P2 laptop. The installation itself went without hitch, and I set about customizing it to my taste and installing various applications. For example I replaced Gnome with KDE, as I had been using KDE since I converted to Linux and don't want at this stage to lean a new desktop environment. Then, on 6 February -- completely out of the blue -- I booted the computer, which I had set to log on automatically to my user. Instead however of seeing the KDE desktop, I got an xterm screen, which I assumed was a fail-safe xterm session. When I tried to use it, it did not respond; the machine hung. I was however able to log in, both as root and my user, on the ordinary terminals, ctl-alt-F1 to F6. It seems to me that the xserver-xorg is broken somehow. I tried aptitude from the command line but could find no broken packages. The only configuration option I know about is dkpg-reconfigure xserver-xorg which was of no help. Another change I noticed that on this fatal boot-up, both the avahi-daemon, whatever that is, and the HP linux printing and imaging system failed to load. To make matters worse, an hour later I booted my desktop and met with the same result: a fail-safe terminal emulator and a hung machine. This failure happened to a P4 box on which I had installed Sarge and KDE in June 2005 when Sarge first came out. Other than a few glitches encountered on initial installation, it has worked perfectly ever since. In this case I was also able to access the box from a native terminal, and so was able to write to zip750 disks all my document files. Again I used aptitude from the command line and also found no broken packages, this time the x-server being xfree86 rather than xorg. I did however discover that aptitude wanted to upgrade xserver-xfree86 to xserver-xfree86-dbg and also upgrade
X doesn't start [Was: KDE peculiarities and questions]
Ken Heard wrote: A few weeks ago I installed Etch RC1 on a Toshiba Tecra 8000 P2 laptop. The installation itself went without hitch, and I set about customizing it to my taste and installing various applications. For example I replaced Gnome with KDE, as I had been using KDE since I converted to Linux and don't want at this stage to lean a new desktop environment. Then, on 6 February -- completely out of the blue -- I booted the computer, which I had set to log on automatically to my user. Instead however of seeing the KDE desktop, I got an xterm screen, which I assumed was a fail-safe xterm session. When I tried to use it, it did not respond; the machine hung. I was however able to log in, both as root and my user, on the ordinary terminals, ctl-alt-F1 to F6. It seems to me that the xserver-xorg is broken somehow. I tried aptitude from the command line but could find no broken packages. The only configuration option I know about is dkpg-reconfigure xserver-xorg which was of no help. Another change I noticed that on this fatal boot-up, both the avahi-daemon, whatever that is, and the HP linux printing and imaging system failed to load. Log into an ordinary terminal, and stop/kill any X-related processes. (Use ps ax and kill as necessary, or use other means such as /etc/init.d/kdm stop). Now as a normal (non-root) user, run startx. What happens? Also check /var/log/Xorg.0.log (or /var/log/XFree86.0.log) for clues, especially lines containing EE. To make matters worse, an hour later I booted my desktop and met with the same result: a fail-safe terminal emulator and a hung machine. This failure happened to a P4 box on which I had installed Sarge and KDE in June 2005 when Sarge first came out. Other than a few glitches encountered on initial installation, it has worked perfectly ever since. Ditto. Again I used aptitude from the command line and also found no broken packages, this time the x-server being xfree86 rather than xorg. I did however discover that aptitude wanted to upgrade xserver-xfree86 to xserver-xfree86-dbg and also upgrade some of the dependencies. Two lines of the syslog read as follows: Feb 8 09:04:41 localhost kdm_greet[2943]: Can't open default user face Feb 8 09:04:47 localhost kdm: :0[2948]: Session /etc/kde3/kdm/Xsession execution failed: Permission denied Unfortunately however I was unable to do any upgrades, because on this boot-up the the operating system -- for the first time ever -- was unable to connect to the LAN. As always, the NIC was detected and the driver installed. It could not connect to the network. The system tried to connect to the network five times, each time reporting Network is down, when I knew it was not. My first instinct was to check the hardware. The card was properly seated in the mainboard, and all the cables and connections worked with another computer and the print server. I swapped the NIC with another one of the same make and model from another desktop. The one swapped to that other desktop worked. The desktop previously reporting network is down still so reports with the swapped NIC which had worked before in the other desktop. The LAN, by the way, is restricted to our residence where only two desktops, one laptop, a print server and a gateway-switch are connected to it. This installation is only ever used by my spouse and me. Run ifconfig and see if you have an expected IP address; my first suspicion is that zeroconf got installed; it tends to cause problems with networking. -- Kent West http://kentwest.blogspot.com http://kentwest.blogspot.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE peculiarities and questions
On Sun, Feb 11, 2007 at 10:23:49PM -0600, Kent West wrote: Ken Heard wrote: 3. On both the laptop and desktop I seem to be stuck with the Gnome login manager. Selecting options in the System AdministrationLogin Manager of the KDE control manager are not implemented. Is there file somewhere I can substitute the KDE login manager for the Gnome one? Try aptitude install kdm and/or dpkg-reconfigure kdm. Or aptitude purge gdm. If kdm is running, this may be bug #407799. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407799 I would see the kdm login screen for a moment, then it would be over written. For me the fix was to purge the desktop-base package. -- Jerome signature.asc Description: Digital signature
Re: KDE peculiarities and questions
On Mon, 2007-02-12 at 14:54 -0500, Ken Heard wrote: The behavour described in my questions two and three may be due to the same cause. I think that if gdm, and possibly other parts of the Gnome desktop environment, remain unpurged from a box where KDE is preferred, some Gnome applications override their KDE counterparts. On my laptop I had purged all Gnome apps and I think that only after the purge was I able to use other mouse cursor themes rather than the one Gnome mandates. On the laptop however I was still presented with the Gnome login manager rather than KDE's; it had that Gnomial look about it. The cursor theme is controlled by the Debian alternatives system. See 'man(8) update-alternatives'. To list the cursor themes you have installed: # update-alternatives --list x-cursor-theme (You have to be root, or use sudo.) You can have more than one theme installed, and use update-alternatives to select the one you want to use. Same goes for a whole bunch of other things, including your default editor, www browser, shell, terminal emulator, window manager, session manager, etc. -- Michael M. ++ Portland, OR ++ USA No live organism can continue for long to exist sanely under conditions of absolute reality; even larks and katydids are supposed, by some, to dream. --S. Jackson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
KDE peculiarities and questions
I have KDE installed on all three of the boxes my spouse and I use. The box with Sarge installed, a P4 desktop, uses KDE 3.3.?; whereas the other two, one a P3 desktop and the other a P2 Tecra 8000 Toshiba laptop, have Etch, which uses KDE 3.5.5. The latter has some nice new features, but I have also run into four peculiarities. 1. On the P3 desktop only, the panel displays the taskbar three times. Once is surely enough. I tried to fix it by purging KDE and reinstalling it, to no avail. Any ideas on what I can do to remove this redundancy? 2. Also on the P3 desktop only, I want to use the system mouse cursor themes; but any options I select from PeripheralsMouseCursor Theme window of the KDE Control Centre are never installed, even after rebooting. It seems that I am stuck with a Gnome mouse cursor theme no matter what I do. On the laptop, where I purged Gnome, this cursor theme option works. Should I purge Gnome from the desktop as well? 3. On both the laptop and desktop I seem to be stuck with the Gnome login manager. Selecting options in the System AdministrationLogin Manager of the KDE control manager are not implemented. Is there file somewhere I can substitute the KDE login manager for the Gnome one? I have already made kdm the default display manager. By running update-alternatives I made startkde the default x-session-manager, konsole the default x-terminal-emulator and kwin the default x-window-manager. 4. On both the laptop and the desktop I would like to remove the Trash icon but cannot find a way to do so. I don't like any icons on the desktop; they spoil my slide show. Help will be appreciated. Regards, Ken Heard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE peculiarities and questions
Ken Heard wrote: 1. On the P3 desktop only, the panel displays the taskbar three times. Once is surely enough. I tried to fix it by purging KDE and reinstalling it, to no avail. Any ideas on what I can do to remove this redundancy? Right-click on the panel, move your mouse over Remove from Panel, then over Applet. You'll probably see 3 instances of an applet named Taskbar, in which case you should remove two of them. --Ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE peculiarities and questions
Ken Heard wrote: I have KDE installed on all three of the boxes my spouse and I use. The box with Sarge installed, a P4 desktop, uses KDE 3.3.?; whereas the other two, one a P3 desktop and the other a P2 Tecra 8000 Toshiba laptop, have Etch, which uses KDE 3.5.5. The latter has some nice new features, but I have also run into four peculiarities. 1.On the P3 desktop only, the panel displays the taskbar three times. Once is surely enough. I tried to fix it by purging KDE and reinstalling it, to no avail. Any ideas on what I can do to remove this redundancy? Does this happen for all users, or just one user? If just one user, I'd rename the ~/.kde? directory for that user and restart KDE. 3.On both the laptop and desktop I seem to be stuck with the Gnome login manager. Selecting options in the System AdministrationLogin Manager of the KDE control manager are not implemented. Is there file somewhere I can substitute the KDE login manager for the Gnome one? Try aptitude install kdm and/or dpkg-reconfigure kdm. Or aptitude purge gdm. I have already made kdm the default display manager. Which is what the above commands should allow you to do. How did you accomplish this? In the KDE Control Panel stuff? -- Kent West Westing Peacefully http://kentwest.blogspot.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
