Ok. What's going on!?!?!?!
Ever since the lastest kde updates many of my (and other users - as demonstrated by various posts) have made my system less rather than more usable (from a GUI/KDE perspective). I fully understand that bugs are inherent to the upgrade process, however the amount of problems I'm having of late is getting very annoying. Konq won't open URL's in links in emails, or from the "run command" destop menu, Kpackage is blind, and having followed Anders (I believe it was him) who found a fix. Unless a really missed something, that hasn't worked in my case. And I don't get how a Kpackage could not include *.rpm extension? SuSEConfig keeps telling me that Gnome and WMaker has no name? I went to both the kde.org and suse sites and can't find the Koffice package version that was mentioned in a previous post that fixed Matt sys concerning this issue and can't find that specific version. Oh, and what's up with ksockets in my system tray, sometimes it's there and other times (mostly) it's not. I have a cable modem and a nic - why is this trying to run - does it get confused and think I have a 56k modem of something? Please don't misunderstand, I'm quite happy with the state of development of SuSE Linux. I just am very frustrated. It' seems that in the transition from kde 2.2.2 to kde 3.0.x that there is a lot of coding issues to be resolved. I know that SuSE is working on this and expect updates in a fairly timely manner - they are usually very good about this. I just had to vent my angst. Cheers, Curtis
On Tuesday 08 January 2002 20.09, Curtis Rey wrote:
Ever since the lastest kde updates many of my (and other users - as demonstrated by various posts) have made my system less rather than more usable (from a GUI/KDE perspective). I fully understand that bugs are inherent to the upgrade process, however the amount of problems I'm having
No they aren't. That's Redmond talk. An upgrade can be smooth, and in my case it has been.
of late is getting very annoying. Konq won't open URL's in links in emails, or from the "run command" destop menu, Kpackage is blind, and
Can you run konqi at all? Do you get any errors i ~/.xsession-errors?
having followed Anders (I believe it was him) who found a fix. Unless a really missed something, that hasn't worked in my case. And I don't get how a Kpackage could not include *.rpm extension?
What did you do?
SuSEConfig keeps telling me that Gnome and WMaker has no name? I went to both the kde.org and suse sites and can't find the Koffice package version that was mentioned in a previous post that fixed Matt sys concerning this issue and can't find that
Are you running the same version of SuSE that Matt is? Note that suse releases different build numbers of packages for different versions of the suse dist.
specific version. Oh, and what's up with ksockets in my system tray, sometimes it's there and other times (mostly) it's not. I have a cable modem and a nic - why is this trying to run - does it get confused and think I have a 56k modem of something?
What's ksockets? Do you mean kinternet? Is it perhaps in your Autostart folder?
Please don't misunderstand, I'm quite happy with the state of development of SuSE Linux. I just am very frustrated. It' seems that in the transition from kde 2.2.2 to kde 3.0.x that there is a lot of coding issues to be resolved. I know that SuSE is working on this and expect updates in a fairly timely manner - they are usually very good about this. I just had to vent my angst.
Am I to understand that you've started running kde3 already? Well, so have I, but note that kde3 is still in beta. There are many things not yet ported to it. It is very much a work in progress. Don't go there if you want a smooth system. regards Anders
Ok, here's the kongi stuff from the X.session errors file. I can run any url if I open konq first. I am not running any K-3 beta ware - I just mention this because, having read the change log I see that some of the package updates are similar to what's going to be implemented in K3. kdecore (KURL): KURL couldn't parse URL "www.charter.net" kdecore (KSocket): Time out while trying to connect to Inet 209.116.0.210 port 80 kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kdecore (KURL): KURL couldn't parse URL "www.charter.net" kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kicker: WARNING: KDE detected X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 14 kio (KIOConnection): ERROR: Header read failed, errno=104 kio (KIOConnection): ERROR: Header has invalid size (-1) kdecore (KURL): KURL couldn't parse URL "--silent" QObject::connect: No such signal KDockArea::docked() QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'view widget') QToolBar::QToolBar main window cannot be 0. ShowHidePage This is also happening with other browsers, but they will occasionally load from a link in an email or text page url. I will send other info about the other issues seperately. TIA Curtis On Tuesday 08 January 2002 13:26, Anders Johansson wrote:
On Tuesday 08 January 2002 20.09, Curtis Rey wrote:
Ever since the lastest kde updates many of my (and other users - as demonstrated by various posts) have made my system less rather than more usable (from a GUI/KDE perspective). I fully understand that bugs are inherent to the upgrade process, however the amount of problems I'm having
No they aren't. That's Redmond talk. An upgrade can be smooth, and in my case it has been.
of late is getting very annoying. Konq won't open URL's in links in emails, or from the "run command" destop menu, Kpackage is blind, and
Can you run konqi at all? Do you get any errors i ~/.xsession-errors?
having followed Anders (I believe it was him) who found a fix. Unless a really missed something, that hasn't worked in my case. And I don't get how a Kpackage could not include *.rpm extension?
What did you do?
SuSEConfig keeps telling me that Gnome and WMaker has no name? I went to both the kde.org and suse sites and can't find the Koffice package version that was mentioned in a previous post that fixed Matt sys concerning this issue and can't find that
Are you running the same version of SuSE that Matt is? Note that suse releases different build numbers of packages for different versions of the suse dist.
specific version. Oh, and what's up with ksockets in my system tray, sometimes it's there and other times (mostly) it's not. I have a cable modem and a nic - why is this trying to run - does it get confused and think I have a 56k modem of something?
What's ksockets? Do you mean kinternet? Is it perhaps in your Autostart folder?
Please don't misunderstand, I'm quite happy with the state of development of SuSE Linux. I just am very frustrated. It' seems that in the transition from kde 2.2.2 to kde 3.0.x that there is a lot of coding issues to be resolved. I know that SuSE is working on this and expect updates in a fairly timely manner - they are usually very good about this. I just had to vent my angst.
Am I to understand that you've started running kde3 already? Well, so have I, but note that kde3 is still in beta. There are many things not yet ported to it. It is very much a work in progress. Don't go there if you want a smooth system.
regards Anders
Hi all, On Wednesday 09 January 2002 02:26, Anders Johansson wrote:
On Tuesday 08 January 2002 20.09, Curtis Rey wrote:
Ever since the lastest kde updates many of my (and other users - as demonstrated by various posts) have made my system less rather than more usable (from a GUI/KDE perspective). I fully understand that bugs are inherent to the upgrade process, however the amount of problems I'm having
No they aren't. That's Redmond talk. An upgrade can be smooth, and in my case it has been.
For me also, besides some newbie problems, all the upgrades had been smooth. Just a few problems, where in most cases I was not sure if it just looks like a problem or really is a problem (e.g. the SuSEconfig messages.) It was nothing compared with the nightmare I had some time ago with trying an win2000 upgrade. I will never touch THAT junk again. Overall I must say that I really like the possibility to see what's going on in the different logs (which I discover one by one) and then to be able to configure about everything, once I learned what's going on.
of late is getting very annoying. Konq won't open URL's in links in emails, or from the "run command" destop menu, Kpackage is blind, and
Can you run konqi at all? Do you get any errors i ~/.xsession-errors?
After downgrading from qt2.3.2 to qt 2.3.1 all my konq problems, which came with the kde2.2.2 upgrade, have dissappeared again.
having followed Anders (I believe it was him) who found a fix. Unless a really missed something, that hasn't worked in my case. And I don't get how a Kpackage could not include *.rpm extension?
I also still have this problem. No big deal, I can run rpm from the command line. But I have to admit, it is difficult to understand that kpackage can not do its main task anymore.
SuSEConfig keeps telling me that Gnome and WMaker has no name? I went to both the kde.org and suse sites and can't find the Koffice package version that was mentioned in a previous post that fixed Matt sys concerning this issue and can't find that
Are you running the same version of SuSE that Matt is? Note that suse releases different build numbers of packages for different versions of the suse dist. specific version.
I still have these 'SuSEwm: ERROR: wmaker: no name defined !' errormessages, trying the latest koffice (koffice-1.1.1-14.rpm, on the SuSE ftp mirrors) did not fix it. However, as this does not hide a problem for kde users I can live with it. (Thanks for the explanation in the "SuSEwm: ERROR: wmaker: no name defined !" thread, Anders!) Here are some more, probably minor, but still irritating issues: - in xconsole within kde, whenever I stop the internet connection (using kinternet), it says: "Dec 28 20:10:47 pinguin pppd[2969]: Couldn't release PPP unit: Inappropriate ioctl for device" - some xconsole errormesages, as explained in the thread "weird behavior with and without nvidia drivers", when I log out from kde: Jan 9 16:14:19 penguin kernel: mtrr: no MTRR for d8000000,1000 found Jan 9 16:14:19 penguin kernel: unset mem range for 0xd8000000 0x2000000 Jan 9 16:14:20 penguin kdm[632]: Server for display :0 terminated unexpectedly Jan 9 16:14:22 penguin kdm[1081]: session start failed Jan 9 16:14:22 penguin kernel: mtrr: no MTRR for d8000000,1000 found Jan 9 16:14:22 penguin kernel: unset mem range for 0xd8000000 0x2000000 Again, it works, but these messages might hint to problems. I still have some freezes while working in kde, which I could not yet link to anything. So I would of course appreciate any ideas to fix it. Have Fun! Matt My configuration: Suse 7.2 prof with kde2.2.2 and qt2.3.1 on a MSI K7T Turbo RAID motherboard with an NVIDIA 2 MX 200 32 MB AGP Graphics Card. RAM is 512 MB. X as installed with 7.2 prof. not modified.
Still get the WMaker/Gnome error warnings in SuSEconfig. However, I have solved the Konq and other associated KDE2 problems. Silly, I should know this - mv the .kde2 dir in the home directory to kde-stuff/kdebk, etc... and delete the temp files in /tmp "kde-<user>", "ksocket-<user>", and "mcop-<user>" then delete the "socket_<computer-name>" and "tmp_<computer-name>" form the the /home/<user>/.kde2 dir, and the ".DCOPserver_<comp-name>" and the associated link (by the same name) and things have improved greatly. Cheers, Curtis On Thursday 10 January 2002 05:18 am, Matt T. wrote:
Hi all,
On Wednesday 09 January 2002 02:26, Anders Johansson wrote:
On Tuesday 08 January 2002 20.09, Curtis Rey wrote:
Ever since the lastest kde updates many of my (and other users - as demonstrated by various posts) have made my system less rather than more usable (from a GUI/KDE perspective). I fully understand that bugs are inherent to the upgrade process, however the amount of problems I'm having
No they aren't. That's Redmond talk. An upgrade can be smooth, and in my case it has been.
For me also, besides some newbie problems, all the upgrades had been smooth. Just a few problems, where in most cases I was not sure if it just looks like a problem or really is a problem (e.g. the SuSEconfig messages.) It was nothing compared with the nightmare I had some time ago with trying an win2000 upgrade. I will never touch THAT junk again.
Overall I must say that I really like the possibility to see what's going on in the different logs (which I discover one by one) and then to be able to configure about everything, once I learned what's going on.
of late is getting very annoying. Konq won't open URL's in links in emails, or from the "run command" destop menu, Kpackage is blind, and
Can you run konqi at all? Do you get any errors i ~/.xsession-errors?
After downgrading from qt2.3.2 to qt 2.3.1 all my konq problems, which came with the kde2.2.2 upgrade, have dissappeared again.
having followed Anders (I believe it was him) who found a fix. Unless a really missed something, that hasn't worked in my case. And I don't get how a Kpackage could not include *.rpm extension?
I also still have this problem. No big deal, I can run rpm from the command line. But I have to admit, it is difficult to understand that kpackage can not do its main task anymore.
SuSEConfig keeps telling me that Gnome and WMaker has no name? I went to both the kde.org and suse sites and can't find the Koffice package version that was mentioned in a previous post that fixed Matt sys concerning this issue and can't find that
Are you running the same version of SuSE that Matt is? Note that suse releases different build numbers of packages for different versions of the suse dist. specific version.
I still have these 'SuSEwm: ERROR: wmaker: no name defined !' errormessages, trying the latest koffice (koffice-1.1.1-14.rpm, on the SuSE ftp mirrors) did not fix it. However, as this does not hide a problem for kde users I can live with it. (Thanks for the explanation in the "SuSEwm: ERROR: wmaker: no name defined !" thread, Anders!)
Here are some more, probably minor, but still irritating issues:
- in xconsole within kde, whenever I stop the internet connection (using kinternet), it says: "Dec 28 20:10:47 pinguin pppd[2969]: Couldn't release PPP unit: Inappropriate ioctl for device"
- some xconsole errormesages, as explained in the thread "weird behavior with and without nvidia drivers", when I log out from kde:
Jan 9 16:14:19 penguin kernel: mtrr: no MTRR for d8000000,1000 found Jan 9 16:14:19 penguin kernel: unset mem range for 0xd8000000 0x2000000 Jan 9 16:14:20 penguin kdm[632]: Server for display :0 terminated unexpectedly Jan 9 16:14:22 penguin kdm[1081]: session start failed Jan 9 16:14:22 penguin kernel: mtrr: no MTRR for d8000000,1000 found Jan 9 16:14:22 penguin kernel: unset mem range for 0xd8000000 0x2000000
Again, it works, but these messages might hint to problems. I still have some freezes while working in kde, which I could not yet link to anything. So I would of course appreciate any ideas to fix it.
Have Fun! Matt
My configuration: Suse 7.2 prof with kde2.2.2 and qt2.3.1 on a MSI K7T Turbo RAID motherboard with an NVIDIA 2 MX 200 32 MB AGP Graphics Card. RAM is 512 MB. X as installed with 7.2 prof. not modified.
participants (3)
-
Anders Johansson
-
Curtis Rey
-
Matt T.