KDE 3.4.x is highly unpredictable
Since installing SuSE 10 last week, I have been met with unpredictability that is staggering. I mentioned the Synaptics touchpad in another post and once I realized it was 'gestures' that were causing problems I disabled all gestures *and* unloaded the khotkeys daemon (since only shutting everything else off didn't work). When I booted, this morning, all the gestures were working as if I had done nothing to turn anything off. I double-checked all the settings from Control Center and found that everything was as I left it --everything shut off & the daemon [supposed to be] not loaded. KDE-3.4.x's window focusing is highly problematic. I had a terminal window open and, before I had typed in the short command, I had four other konsoles on the desktop (thank you, Synaptics touchpad that enters taps via pressure beside the touchpad when neither heel of hand or finger is anywhere near it) and every last one of those konsoles was in the background. (One could argue that it was a good thing given the fact I was trying to enter a command ...puhleeze!) Every other application opened when anything else is loaded cannot consistently decide whether or not to load in the foreground. Sometimes yes, mostly no. Kget hardly downloads anything before stalling out entirely. I use wget on the comnand line and do not experience the long stalls --only an occasional short stall is apparent, and files download quickly. Korganizer's alarm daemon works, and successfully brings up a reminder in the background --unless nothing else is on the desktop, in which case it'll be in the foreground. This has been happening since v9.1, and it isn't even arguable that it should have been fixed long ago. This problem is not so serious since it can be ignored altogether (though disabling it leads to a desktop msg each and every time one boots, trying to encourage me to turn it back on): The Powersave daemon shuts down the box okay but, in the case of my HP ze5570us notebook the video RAM isn't turned back on when it resumes --either from suspend2disk or suspend2ram. This, too, had been around since about 9.2, I believe, and definitely since 9.3. Finally, the question: Is there a way to install KDE-3.2.1 (or 3.2.2) on SuSE 10?? I'd go back to 9, except for the fact that, after using it for several months, it started locking up on every 3rd boot just prior to starting kdm. I had the box checked out by an HP service center and they indicated that there was nothing physically wrong with the box. So... I dumped SuSE altogether until 10 came out, hoping that the bugs would be now fixed. Alas, that was not to be the case. -- ...Yogich SuSE rox --when it wants to. ...But not today.
On Monday 14 November 2005 05:14 pm, Yogich wrote:
Since installing SuSE 10 last week, I have been met with unpredictability that is staggering. I mentioned the Synaptics touchpad in another post and
Have you run SaX2 in the system? I know nothing about touchpads other than they are mentioned in the SaX2 setup. Steven
On Monday 14 November 2005 05:14 pm, Yogich wrote:
Since installing SuSE 10 last week, I have been met with unpredictability that is staggering. I mentioned the Synaptics touchpad in another post andasystem?
Have you run SaX2 in the asystem? I know nothing about touchpads other than they are mentioned in the SaX2 setup.
Steven Yep... ran it more than once. Even tried changing to the driver that I used in v9 ...but it won't change --as in, xorg.conf still reads the same as it did before I [supposedly] changed the driver. Add to that the fact that, as I wrote the above, the mouse pointer was in the middle of your post and the cursor also went there several times w/o any influence of my having touched
On Monday 14 November 2005 16:24, Steven T. Hatton wrote: the touchpad. Slight pressure on the plastic case is enough, since the driver is overly sensitive ...and always has been. -- ...Yogich
On Monday 14 November 2005 07:52 pm, Yogich wrote:
Yep... ran it more than once. Even tried changing to the driver that I used in v9 ...but it won't change --as in, xorg.conf still reads the same as it did before I [supposedly] changed the driver. Add to that the fact that, as I wrote the above, the mouse pointer was in the middle of your post and the cursor also went there several times w/o any influence of my having touched the touchpad. Slight pressure on the plastic case is enough, since the driver is overly sensitive ...and always has been. -- ...Yogich
Is your /etc/X11/XF86Config symlinked to /etc/X11/xorg.conf? It should be. Steven
On Monday 14 November 2005 18:57, Steven T. Hatton wrote:
On Monday 14 November 2005 07:52 pm, Yogich wrote:
Yep... ran it more than once. Even tried changing to the driver that I used in v9 ...but it won't change --as in, xorg.conf still reads the same as it did before I [supposedly] changed the driver. Add to that the fact that, as I wrote the above, the mouse pointer was in the middle of your post and the cursor also went there several times w/o any influence of my having touched the touchpad. Slight pressure on the plastic case is enough, since the driver is overly sensitive ...and always has been. -- ...Yogich
Is your /etc/X11/XF86Config symlinked to /etc/X11/xorg.conf? It should be.
Steven
Nope... actually it is in /usr/X11R6/bin (?) ...and it points to xorgconfig in the same directory. I was having many problems getting sax to take care of business but finally managed to get the driver changed. I'm now ready for some suggestions as to how to get newly-opened windows to appear *above* all the rest. I still can hardly believe that, after all this time, the KDE people have not put the kibosh on that bug! I can't be the only one experiencing this, can I?? I think this is the most frustrating of the lot in my original post! -- ...Yogich
On Monday 14 November 2005 09:56 pm, Yogich wrote:
On Monday 14 November 2005 18:57, Steven T. Hatton wrote:
On Monday 14 November 2005 07:52 pm, Yogich wrote:
Yep... ran it more than once. Even tried changing to the driver that I used in v9 ...but it won't change --as in, xorg.conf still reads the same as it did before I [supposedly] changed the driver. Add to that the fact that, as I wrote the above, the mouse pointer was in the middle of your post and the cursor also went there several times w/o any influence of my having touched the touchpad. Slight pressure on the plastic case is enough, since the driver is overly sensitive ...and always has been. -- ...Yogich
Is your /etc/X11/XF86Config symlinked to /etc/X11/xorg.conf? It should be.
Steven
Nope... actually it is in /usr/X11R6/bin (?) ...and it points to xorgconfig in the same directory.
You should have, more or less, this in your /etc/X11 $ ls -l /etc/X11 total 81 drwxr-xr-x 2 root root 320 2005-10-27 21:03 WindowMaker lrwxrwxrwx 1 root root 9 2005-11-03 12:38 XF86Config -> xorg.conf -r--r--r-- 1 root root 1353 2005-09-12 19:25 Xmodmap -r--r--r-- 1 root root 1049 2005-09-12 19:25 Xmodmap.remote -r--r--r-- 1 root root 6250 2005-09-12 19:25 Xresources -r--r--r-- 1 root root 6289 2004-06-18 14:47 Xresources.rpmsave drwxr-xr-x 4 root root 104 2004-05-25 12:47 applnk drwxr-xr-x 2 root root 72 2005-11-03 12:20 fs drwxr-xr-x 2 root root 200 2005-10-27 21:03 fvwm2 drwxr-xr-x 2 root root 184 2005-10-27 21:07 icewm -rw-r--r-- 1 root root 170 2005-08-29 05:47 kstylerc drwxr-xr-x 2 root root 80 2005-11-03 12:20 lbxproxy drwxr-xr-x 2 root root 336 2005-10-27 21:19 mlterm drwxr-xr-x 2 root root 72 2005-11-03 12:20 proxymngr -rw-r--r-- 1 root root 117 2003-03-03 05:08 qt_gtk_fnt2fntrc -rw-r--r-- 1 root root 6794 2005-11-14 04:35 qt_plugins_3.3rc -rw-r--r-- 1 root root 5286 2005-09-12 20:19 qtrc -rw-r--r-- 1 root root 4971 2005-05-05 15:38 qtrc.rpmsave drwxr-xr-x 4 root root 120 2005-11-03 12:20 rstart drwxr-xr-x 3 root root 104 2004-01-22 08:03 susewm drwxr-xr-x 2 root root 80 2005-11-03 12:20 twm drwxr-xr-x 3 root root 704 2005-11-13 23:03 xdm -rw-r--r-- 1 root root 4515 2005-10-28 10:13 xim drwxr-xr-x 2 root root 72 2005-11-03 11:39 xim.d drwxr-xr-x 3 root root 136 2005-11-03 12:20 xinit drwxr-xr-x 10 root root 560 2005-11-12 11:16 xkb -rw-r--r-- 1 root root 10105 2005-11-03 12:32 xorg.conf -rw-r--r-- 1 root root 33 2005-11-03 12:32 xorg.conf.md5 drwxr-xr-x 3 root root 104 2005-11-03 12:20 xserver drwxr-xr-x 2 root root 80 2005-11-03 12:20 xsm
I was having many problems getting sax to take care of business but finally managed to get the driver changed.
That's good. BTW, when you try to run SaX2, be sure you don't have xorg.conf or XF86Config in the root directory, nor in the current directory(unless that is /etc/X11. Basically that is the only place for xorg.conf and XF86Config. Im not talking about the program xf86config, I'm talking about the configuration file XF86Config.
I'm now ready for some suggestions as to how to get newly-opened windows to appear *above* all the rest. I still can hardly believe that, after all this time, the KDE people have not put the kibosh on that bug!
I'm not sure it's a "bug". It may depend on the app. I don't have that problem with most apps. Really the only time a window doesn't come to the front is when I select it programmatically after it's opened. For example, in Mathematica, if I hit F1 for help and the HelpBrowser is already opened, it doesn't come to the top. What app is causing problems?
I can't be the only one experiencing this, can I?? I think this is the most frustrating of the lot in my original post!
It's hard to know exactly what you are experiencing. Can you provide more specifics about what's opened, and what you are trying to open? Steven
On Monday 14 November 2005 21:48, Steven T. Hatton wrote:
On Monday 14 November 2005 09:56 pm, Yogich wrote:
Is your /etc/X11/XF86Config symlinked to /etc/X11/xorg.conf? It should be.
Steven
Nope... actually it is in /usr/X11R6/bin (?) ...and it points to xorgconfig in the same directory.
You should have, more or less, this in your /etc/X11
$ ls -l /etc/X11 total 81 drwxr-xr-x 2 root root 320 2005-10-27 21:03 WindowMaker lrwxrwxrwx 1 root root 9 2005-11-03 12:38 XF86Config -> xorg.conf -r--r--r-- 1 root root 1353 2005-09-12 19:25 Xmodmap -r--r--r-- 1 root root 1049 2005-09-12 19:25 Xmodmap.remote -r--r--r-- 1 root root 6250 2005-09-12 19:25 Xresources -r--r--r-- 1 root root 6289 2004-06-18 14:47 Xresources.rpmsave drwxr-xr-x 4 root root 104 2004-05-25 12:47 applnk drwxr-xr-x 2 root root 72 2005-11-03 12:20 fs drwxr-xr-x 2 root root 200 2005-10-27 21:03 fvwm2 drwxr-xr-x 2 root root 184 2005-10-27 21:07 icewm -rw-r--r-- 1 root root 170 2005-08-29 05:47 kstylerc drwxr-xr-x 2 root root 80 2005-11-03 12:20 lbxproxy drwxr-xr-x 2 root root 336 2005-10-27 21:19 mlterm drwxr-xr-x 2 root root 72 2005-11-03 12:20 proxymngr -rw-r--r-- 1 root root 117 2003-03-03 05:08 qt_gtk_fnt2fntrc -rw-r--r-- 1 root root 6794 2005-11-14 04:35 qt_plugins_3.3rc -rw-r--r-- 1 root root 5286 2005-09-12 20:19 qtrc -rw-r--r-- 1 root root 4971 2005-05-05 15:38 qtrc.rpmsave drwxr-xr-x 4 root root 120 2005-11-03 12:20 rstart drwxr-xr-x 3 root root 104 2004-01-22 08:03 susewm drwxr-xr-x 2 root root 80 2005-11-03 12:20 twm drwxr-xr-x 3 root root 704 2005-11-13 23:03 xdm -rw-r--r-- 1 root root 4515 2005-10-28 10:13 xim drwxr-xr-x 2 root root 72 2005-11-03 11:39 xim.d drwxr-xr-x 3 root root 136 2005-11-03 12:20 xinit drwxr-xr-x 10 root root 560 2005-11-12 11:16 xkb -rw-r--r-- 1 root root 10105 2005-11-03 12:32 xorg.conf -rw-r--r-- 1 root root 33 2005-11-03 12:32 xorg.conf.md5 drwxr-xr-x 3 root root 104 2005-11-03 12:20 xserver drwxr-xr-x 2 root root 80 2005-11-03 12:20 xsm
More or less, I guess... I'm on the downloadable 5-CD version. I don't have that much in the directory.
I was having many problems getting sax to take care of business but finally managed to get the driver changed.
That's good. BTW, when you try to run SaX2, be sure you don't have xorg.conf or XF86Config in the root directory, nor in the current directory(unless that is /etc/X11. Basically that is the only place for xorg.conf and XF86Config. Im not talking about the program xf86config, I'm talking about the configuration file XF86Config. Noted.
I'm now ready for some suggestions as to how to get newly-opened windows to appear *above* all the rest. I still can hardly believe that, after all this time, the KDE people have not put the kibosh on that bug!
I'm not sure it's a "bug". It may depend on the app. I don't have that problem with most apps. Really the only time a window doesn't come to the front is when I select it programmatically after it's opened. For example, in Mathematica, if I hit F1 for help and the HelpBrowser is already opened, it doesn't come to the top. What app is causing problems?
You name it. <LOL> If this phenomenon is supposed to be a feature, I don't like it. It is really hard to explain with any amount of clarity. A video would be better. :-\
I can't be the only one experiencing this, can I?? I think this is the most frustrating of the lot in my original post!
It's hard to know exactly what you are experiencing. Can you provide more specifics about what's opened, and what you are trying to open?
Steven
The most noteable problem was the multiple konsole problem I mentioned in my original post. I opened one konsole & while I was putting something on the command line, four other konsoles opened ...all out of focus. Turned out the mouse pointer was on the taskbar icon and the slight pressure on the case surrounding the touchpad was recognized as a tap. ...BTW, the touchpad is behaving more-or-less normally, now --if you take into consideration the fact that the overly-sensitive touchpad will register a tap if one breathes on it. -- ...Yogich
participants (2)
-
Steven T. Hatton
-
Yogich