LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   After upgrading to KDE 3.4... (https://www.linuxquestions.org/questions/suse-opensuse-60/after-upgrading-to-kde-3-4-a-303103/)

seelk 03-18-2005 05:28 AM

After upgrading to KDE 3.4...
 
my backgrounds from the login window doesn't show up. I have set it multiple times; have done ctrl-alt-backspace and have verified the background but when powering off the system and turn it back on I get this black background with the splash-screen of choice. Anyone aware of this?

I'm starting this thread for anyone that's experiencing anything unusual after upgrading to KDE 3.4 to post it here.

piscikeeper 03-18-2005 12:43 PM

same issue on 9.1,had to re-configure the login screen a couple times before it held.also had an issue on the first boot with grub,updated config and back to normal.now to fix gxine associations......

removing the log from the greeter
as root: /etc/opt/kde3/share/config/kdm/kdmrc --edit as follows:
[X-:0-Greeter]
LogSource=/dev/xconsole
ShowLog=false

Marrea 03-19-2005 10:46 AM

I've just upgraded this morning and discover that Gnome is no longer listed as an option at log-in. There now seems to be no way of adding Gnome to the list of sessions available at log-in from the Log-In Manager in Control Center either. I don't know what the command is to start Gnome from text mode, so at the moment I'm Gnomeless !!

cootetom 03-19-2005 12:21 PM

I take it u upgraded kdm aswell. Do you get a load of lines from the /var/log/messages file listed below the loggin screen. I do but want to know how to get rid of this output. There are two threads on this but no one seems to know anything about it.

http://www.linuxquestions.org/questi...hreadid=303070
http://www.linuxquestions.org/questi...hreadid=302792

Marrea 03-19-2005 03:34 PM

Yes, I do indeed get a load of lines as you describe, which I also find annoying.

I upgraded KDE through YaST's Install and Remove Software using the ftp.mirrorservice.org supplementary KDE update for 9.2 site as an installation source. I don't know whether that would have also upgraded kdm.

cootetom 03-19-2005 05:41 PM

i think it would have. I updated by downloading all the rpms, adding the directory to yaste and updating all kde/qt3 packages. Maybe thats how they decided kdm will look, looks ugly to me, it could atleast be optional!

piscikeeper 03-19-2005 07:25 PM

the fix for the log messages is part of post #2 in this thread.

canon 03-19-2005 08:27 PM

Missing icons?
 
The loader background is black, but that's no biggie for me. What IS bothering me is that a couple of the icons in my system tray (SuSE Watcher and SuSE Hardware Tool) are invisible. I can still click and otherwise access them, they're just invisible. And The bouncing mini icons of starting programs that show up next to the cursor are just colored sqares... Like 3.4 brok the icon-sizing ability... anyone else experience or (preferably) fix this issue already?

Marrea 03-20-2005 07:48 AM

Quote:

Originally posted by piscikeeper
the fix for the log messages is part of post #2 in this thread.
Thanks, I'll give that a try.

The Stranger 03-20-2005 09:59 AM

Quote:

Originally posted by Marrea
Yes, I do indeed get a load of lines as you describe, which I also find annoying.

I upgraded KDE through YaST's Install and Remove Software using the ftp.mirrorservice.org supplementary KDE update for 9.2 site as an installation source. I don't know whether that would have also upgraded kdm.

At the risk of sounding ignorant, well I am ignorant being new to this, I was wondering how exactly one goes about upgrading from KDE 3.2 to later versions? You mentioned that you did it through YaST's install and remove using the supplementary KDE update for 9.2. I am running 9.1 and would like to attempt this, but was wondering is it just a matter of selecting KDE packages and an upgrade is preformed? Or is there more to it than that?(my guess is there is more to it, hence the question) Any suggestions would be greatly appreciated. I have searched the boards, but have yet to find this answer...

-TS-

piscikeeper 03-20-2005 12:17 PM

you need to add the repositories as a souce this thread tells how to do it.post 10 for exact directions.also using GNOME instead of KDE in the directory listing will give the updates for gnome.

Marrea 03-20-2005 12:36 PM

piscikeeper, you got in first !

All I would add is that when you want to check on subsequent occasions for new packages, you need first to go into the Software Source Media window in Change Source of Installation, highlight the site you are using as a source, click on the arrow beside Edit (at the bottom of the window), and select Refresh. If you don't do this, when you go into Install and Remove Software any new updates won't show.

The Stranger 03-20-2005 04:08 PM

Hey Thanks guys, I'll try it out and let you know if I have any problems...

-TS-

The Stranger 03-20-2005 05:27 PM

Okay, so I have added a supplementary source, but where does one find the updates for KDE?

Marrea 03-21-2005 07:27 AM

Quote:

Originally posted by The Stranger
Okay, so I have added a supplementary source, but where does one find the updates for KDE?
The Stranger

You've already added your KDE supplementary source, so now have a look at the "Performing the Update" section of http://www.novell.com/coolsolutions/feature/11504.html which sets out the procedure.

The Stranger 03-21-2005 09:06 AM

Sweet! Thanks Marrea for the site! This is a great place...although I should have known that Novell would have the info needed...

Hope I wasn't a bother, and thanks again!!

-TS-

Marrea 03-21-2005 09:30 AM

No bother at all. I hope it works for you.

KimVette 03-21-2005 10:28 AM

Be sure to bump the supplementary tree higher in the install source list in YaST. I recommend making it the first entry in the list.

abisko00 03-21-2005 10:35 AM

Quote:

Be sure to bump the supplementary tree higher in the install source list in YaST. I recommend making it the first entry in the list.
Just a further comment on already existing supplementary sources:

Since these directories are not static (means that the existing packages will be replaced by newer versions), it is advisable to refresh the installation source prior to updates. This will update the local copy of the database. Otherwise you may not see the correct packages in YaST.

Yast -> Software -> Change Source of Installation -> Edit -> Refresh

EDIT: just found out that this has been said before. Please excuse my ignorance.

The Stranger 03-21-2005 11:52 AM

Hey thanks for the advice...

Well I tried this, but there seems to be a lot of conflicts with things, so I guess I am going to have to go through it all one by one...:(

-TS-

abisko00 03-21-2005 12:29 PM

I think some conflicts are normal. Some packages may no more exist since they have been merged (e.g. kdepim3 now contains kdepim3-organizer). Also some packages may be set to protected (because you installed them from other sources). In this case you may 'unprotect' them and allow YaST to install the new version (has happened with 'arts' elsewhere).

The Stranger 03-22-2005 08:44 AM

Well guys (and gals) I installed it all and I think it worked, HOWEVER:( Now it boots up in a command screen and asks for login and password. This is a doozy since I tried my other logins and passwords to no avail. Any thoughts on how to get a password and login?

-TS-

EDIT** Okay it seems that I can get into a user account, but how do I get the graphic interface to start up?

piscikeeper 03-22-2005 05:03 PM

try startx to make sure the settings work.afterwards edit /etc/inittab to read "id:5:initdefault".(minus quotes) it is probably currently set to "id:3:initdefault"

The Stranger 03-22-2005 06:19 PM

I would try that, but I can't seem to get into the root account. The old password will not work. I tried init 5, but I don't have permission to do that. I also tried Sax2 but I have to switch to init 3 which i am having trouble doing. I think that YaST wasn't able to configure the video card for some reason after the upgrade. Still need to get that root password though...

-TS-

Marrea 03-23-2005 05:22 PM

Quote:

Originally posted by piscikeeper
the fix for the log messages is part of post #2 in this thread.
piscikeeper - I've only just got round to editing the file today. It worked a treat, so very many thanks.

piscikeeper 03-23-2005 08:01 PM

i've had the same issue after a gentoo update.search the net for a how-to on using a chroot environment for lost passwords.
you need to mount the root partition as read/write and edit the password and shadow files.

avidwriter 03-23-2005 08:16 PM

see my mouse posting wierdness thread on the main suse page. optical settings not being saved.

also,

what does one do when kdelibs are a requirement that it must be < kde level -0.999 now that we're at 3.4? i can't install anything!!!! all these older programs won't install now... plz help.........

adamberns 03-25-2005 12:00 PM

1) Lost all System Notification sounds - No sound from any of them. Although games, MPlayer, RealPlayer etc. work fine.

2) kicker error on "Turn Off Computer", but not on "End Current Session".

piscikeeper 03-25-2005 01:13 PM

for sounds,as root:
/opt/kde3/bin/startkde

test -n "$KDEWM"&&KDEWM="--windowmanager $KDEWM"
kdeinit +knotify
kwrapper ksmserver $KDEWM

-------add the kdeinit line,it's probably missing---------

same audio issue as the 3.3.2 update,but it was faster to look through my notes than to lookup the link.besides,it might be a good idea to pull all the issues and fixes into a single thread .

for the kicker issue i dont have a clue just yet,but it's probably in the kicker config.

youngtom 03-25-2005 01:32 PM

Quote:

Originally posted by piscikeeper
besides,it might be a good idea to pull all the issues and fixes into a single thread .
That sounds like a good idea. Maybe we can make this thread 'sticky' and then folks can add other issues to it.

adamberns 03-25-2005 02:08 PM

Quote:

Originally posted by piscikeeper
for sounds,as root:
/opt/kde3/bin/startkde

test -n "$KDEWM"&&KDEWM="--windowmanager $KDEWM"
kdeinit +knotify
kwrapper ksmserver $KDEWM

-------add the kdeinit line,it's probably missing---------

same audio issue as the 3.3.2 update,but it was faster to look through my notes than to lookup the link.besides,it might be a good idea to pull all the issues and fixes into a single thread .

for the kicker issue i dont have a clue just yet,but it's probably in the kicker config.

That did the trick for the System Notifications. Now I have some audio feedback in KDE.

Thank you piscikeeper!

dasbooter 03-28-2005 07:15 PM

ohhh god I have spent hours on this I just don't want to give up on it.

(sigh) I just cant get the Suse 9.2 's search feature of KDE HelpCenter/Suse HelpCenter(the lifebuoy in the panel menu) to work since I upgraded KDE to 3.4

It prompts me to build an index but there is nothing to check off under search scope in the build search index window that opens. I therefore cannot build a search index.

I have done alot of googling on the subject and it seems this happens to quite a few people after upgrading KDE from all the way back to really old versions. I have tried alot of stuff from these old threads and nothing seems to work

here is what I have tried:
Deleting ~.kde/share/config/khelpcenterrc so new config file would be written

running from konsole susehelpindex --force. It builds the index for 20 docs but I cant seem them in the above window.

I have tried editing this file to make sure it had the appropriate stuff in it : /etc/sysconfig/susehelp:
DOC_HOST="yourhost.yourdmain"
DOC_ALLOW="localhost .yourdomain"
DOC_AUTOINDEX="yes"

I have from the console, run "rundig" but I only partially understand what it is doing. I simply tried to follow directions from another thread I found.

I checked all the susehelp/help related packages and pressed update to force a reinstallation of those packages anyways.

One curious thing though is that I recently had a power outage due to cat (not the command but the curious clawed type) that was causing reiserf warnings. I tried to use the suse installation disk 1 to fix this and when it was doing its thing it I thought it said something about missing a package that was part of the minimum packages that you need. I think that it might have been susehelp but it wouldn't fix it. Of course it wouldnt fix the reiserf warnings either so I learned a lot about holding my breath and # fschk --rebuild that day.

Thanx all for the help. I always try to help myself bfore consulting others so I hope it justifies this lengthy post

dasbooter 03-28-2005 08:04 PM

I thought I would also mention that those who decided to rebuild arts 1.4.0-8 from a rpm.src as a fix for the lack of system notifications will need to set the sliders to 100% in control center> system notifications > player settings to in order to hear .ogg files play for sys. notifications. If set to less than that they wont play at all for some reason.

alsamixer shows all levels good so I dont know why the weird behavior

I have edited startkde according to this thread and I still have this weird behaviour but I do have sys notification sounds as long as the slider is set to 100%

Hope this helps :)

greenthing 03-30-2005 06:44 AM

This looks like its a general kde 3.4 problem thread if its not please tell me so and i will delete this post.
I upgraded to kde 3.4 but now i cant login. If i enter username+pass and try to login the screen goes black for two seconds then im back at the login prompt anybody know why.

PS loging into fvwm2 works fine.

abisko00 03-30-2005 06:56 AM

Quote:

Originally posted by greenthing
This looks like its a general kde 3.4 problem thread if its not please tell me so and i will delete this post.
I upgraded to kde 3.4 but now i cant login. If i enter username+pass and try to login the screen goes black for two seconds then im back at the login prompt anybody know why.

PS loging into fvwm2 works fine.

I noticed a similar strange behaviour when I updated KDE from KDE and restarted without reboot. Did you try to reboot?

greenthing 03-30-2005 07:53 AM

Yes.

abisko00 03-30-2005 08:37 AM

I'd say, delete the users .kde folder and try again. It may be worth checking ~/.xsession-errors and /var/log/kdm.log first.

greenthing 03-30-2005 11:19 AM

I tried to delete the .kde flder but it didnt work but i for some reason tried an apt update thinking it might hav been broken packages and it showed dependencies that YaST did not. I solved the dependencies and the problem was solved.

piscikeeper 03-30-2005 08:05 PM

setting login screen wallpaper
 
it seems now as if KDE will no longer use wallpaper not in the correct file as login screen backgrounds.
the answer is to simply add your choice to /opt/kde3/share/wallpapers ,then select it from the drop-down menu in login screen setup.:D

galliar 03-30-2005 09:57 PM

VNC not working
 
Hello,

I upgraded per the instructions in this forum and almost everything works. When I connect from any computer using a web browser by typing in for the address: http://xxx.xxxx.xxxx.xxxx:5801, I get a VNC login screen. When I login, I just get a very low res blank screen with an X for the mouse pointer. Has anybody ran into this? I re-installed the old Tight-vnc package and I still get the same problem. Using the VNC client is key to me, since I use my machine from wherever I am.

If anybody has resolved this, please let us know!!

Regards,

Randy.

piscikeeper 04-01-2005 07:28 AM

kmenu icon size
 
just a fix for those huge new menu icons:
/home/<user>/.kde/share/config/kickerrc
under [menus] change "MenuEntryHeight=32" to something you like better (22 works well @1280x1024) ,then restart kde.

YellowFin 04-02-2005 10:35 PM

i upgrade from 3.3 to 3.4, i had some of the problems listed above got them all straighten out ((thanks))
but i have one issue... when i move my mouse tio the edge of the screen it switchs to another window, i tried to disable it but no luck sereching in control panel any suggestions?

thanks , kevin

piscikeeper 04-02-2005 11:42 PM

control center>desktop>window behavior
un-check "Traverse windows on all desktops"
might have to re-start kde.

YellowFin 04-03-2005 11:18 AM

i tried to do that several times, but it seems to be "stuck" there


well i serached around more, and its in desktop>>window behavior>>advanced tab>>active desktop borders

thanks

piscikeeper 04-04-2005 09:27 PM

partial fix for cursor theme
 
the problem is somewhere in the kdebase3-suse package,the package that customizes kde for suse,the kmenu icon being the most noticable.by removing the package on another machine,i now have the cursor themes working.

YellowFin 04-05-2005 05:55 AM

when i removed the kdebase3-suse package all my settings were reset, and it also seemed likeyast was working slower, what is actually in the package??

abisko00 04-05-2005 06:01 AM

Quote:

what is actually in the package??
Try to find out with:

Code:

rpm -ql kdebase3-SuSE
Many configuration files are contained here!

piscikeeper 04-05-2005 05:24 PM

working :cursor themes
 
by removing the kdebase-suse package the cursor themes work again.......by re-installing kdebase-suse,the suse customizations return + the cursor themes work again.
the package also includes suse wallpapers,so this may also fix the login screen wallpaper issue :D .

i_s 04-11-2005 08:49 PM

Issues with OpenOffice,

when I try to open a document with open office using File--> open, the file dialg crashes and I am unable to see the files to be opened, moreover, when I right-click on the file and pick actions-->open with e.g. spreadsheet, it tells me that the file is password protected. Below is a copy of the output of backtrace in KDE crash handler

Code:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1098321248 (LWP 10721)]
[New Thread 1106357168 (LWP 10724)]
[Thread debugging using libthread_db enabled]
[New Thread 1098321248 (LWP 10721)]
[New Thread 1106357168 (LWP 10724)]
[Thread debugging using libthread_db enabled]
[New Thread 1098321248 (LWP 10721)]
[New Thread 1106357168 (LWP 10724)]
[KCrash handler]
#7  0x409a3d2d in __dynamic_cast () from /usr/lib/libstdc++.so.5
#8  0x40c478a3 in KAcceleratorManagerPrivate::manage ()
  from /opt/kde3/lib/libkdecore.so.4
#9  0x40c47a2e in KAcceleratorManager::manage ()
  from /opt/kde3/lib/libkdecore.so.4
#10 0x40c47a63 in KAcceleratorManager::manage ()
  from /opt/kde3/lib/libkdecore.so.4
#11 0x40c47ab2 in KCheckAccelerators::checkAccelerators ()
  from /opt/kde3/lib/libkdecore.so.4
#12 0x40c4819b in KCheckAccelerators::autoCheckSlot ()
  from /opt/kde3/lib/libkdecore.so.4
#13 0x40c4824c in KCheckAccelerators::qt_invoke ()
  from /opt/kde3/lib/libkdecore.so.4
#14 0x40fa431e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#15 0x40fa4ac6 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0x412f8359 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#17 0x40fc954f in QTimer::event () from /usr/lib/libqt-mt.so.3
#18 0x40f41baf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#19 0x40f43773 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#20 0x40c8c6d1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#21 0x40f3635c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#22 0x40eef156 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#23 0x40f59b41 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#24 0x40f435af in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3
#25 0x4113af72 in QDialog::exec () from /usr/lib/libqt-mt.so.3
#26 0x0805351e in FileDialog::customEvent ()
#27 0x40fa4cde in QObject::event () from /usr/lib/libqt-mt.so.3
#28 0x40fda3df in QWidget::event () from /usr/lib/libqt-mt.so.3
#29 0x40f41baf in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#30 0x40f43773 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#31 0x40c8c6d1 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#32 0x40f429f0 in QApplication::sendPostedEvents ()
  from /usr/lib/libqt-mt.so.3
#33 0x40f42a74 in QApplication::sendPostedEvents ()
  from /usr/lib/libqt-mt.so.3
#34 0x40eeea90 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#35 0x40f59b41 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#36 0x40f59986 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#37 0x40f4363f in QApplication::exec () from /usr/lib/libqt-mt.so.3
#38 0x08056e84 in main ()

Thanks


All times are GMT -5. The time now is 01:27 PM.