After KDE3.1 upgrade File Manager SU does not run
I tried the suggestion to uncheck 'file' in configuring the Previews. That did
not work.
If I log in as root and start it, it will come up for a short second or two
and shutdown with a signal 11 (SIGSEGV).
However, I can click on a user folder and File Mgr will come up as non-SU
and stay up.
The Backtrace from the Crash Handler gives me:
(no debugging symbols found)...(no debugging symbols found)...
0x411d98c9 in wait4 () from /lib/libc.so.6
#0 0x411d98c9 in wait4 () from /lib/libc.so.6
#1 0x41254c90 in __DTOR_END__ () from /lib/libc.so.6
#2 0x41034a93 in waitpid () from /lib/libpthread.so.0
#3 0x40743b0d in KCrash::defaultCrashHandler(int) ()
from /opt/kde3/lib/libkdecore.so.4
#4 0x4103212b in pthread_sighandler () from /lib/libpthread.so.0
#5 <signal handler called>
#6 0x00002522 in ?? ()
#7 0x40759240 in KLibrary::factory() () from /opt/kde3/lib/libkdecore.so.4
#8 0x4075b1a4 in KLibLoader::factory(char const*) ()
from /opt/kde3/lib/libkdecore.so.4
#9 0x400ff4f1 in KonqIconViewWidget::startImagePreview(QStringList const&,
bool) () from /opt/kde3/lib/libkonq.so.4
#10 0x460ca66e in KonqKfmIconView::mimeTypeDeterminationFinished() ()
from /opt/kde3/lib/kde3/konq_iconview.so
#11 0x460cdb8e in KMimeTypeResolver
* On Thursday 30 January 2003 05:18 am, Richard wrote:
I tried the suggestion to uncheck 'file' in configuring the Previews. That did not work.
If I log in as root and start it, it will come up for a short second or two and shutdown with a signal 11 (SIGSEGV). However, I can click on a user folder and File Mgr will come up as non-SU and stay up.
The Backtrace from the Crash Handler gives me: (snip) Other than this one glitch everything else seems to be working ok. Anyone have any kind suggestions for me? TIA Richard
--********************** Richard, I had about the same problem with Krusader (sig11) and Konqueror (using kdesu). Konq came up and quickly shutdown. What I did was remove the /tmp/mcop-(user) folder and Konq was pleased with that. It created a new one on startup and it works great now as root file manager while logged in as user. Krusader required a bit more, but it is working great also! I had to compile the newest version 1.12_beta1, but it was pretty painless. I also created a rpm file for 8.1 & KDE3.1 if anyone wants that. Just mail me off the list. You will need to remove the old version SuSE 8.1 installed though as these two don't really agree with each other! :o) Patrick --- KMail v1.5 --- SuSE Linux Pro v8.1 --- Registered Linux User #225206 On any other day, that might seem strange...
On Thursday 30 January 2003 10:48 am, PL O'Smith wrote:
Richard, I had about the same problem with Krusader (sig11) and Konqueror (using kdesu). Konq came up and quickly shutdown. What I did was remove the /tmp/mcop-(user) folder and Konq was pleased with that. It created a new one on startup and it works great now as root file manager while logged in as user.
Patrick, I tried your suggestion but it did not do the trick. I tried all kinds of combinations such as delete, REBOOT, and simply relogin as root and other users to no avail. Konq fires up as root but as soon as the icons are painted it closes with the same error message. Any other ideas? I wonder if deleting the contents of /tmp would 1. fix the problem, 2. screw up something else??? I see lots of stuff in there. Thanks, Richard
Op donderdag 30 januari 2003 20:19, schreef Richard:
I tried your suggestion but it did not do the trick. I tried all kinds of combinations such as delete, REBOOT, and simply relogin as root and other users to no avail. Konq fires up as root but as soon as the icons are painted it closes with the same error message.
Any other ideas? I wonder if deleting the contents of /tmp would 1. fix the problem, 2. screw up something else??? I see lots of stuff in there.
launch konqueror from a console, look at the error messages. -- Richard Bos Without a home the journey is endless
On Thursday 30 January 2003 1:21 pm, Richard Bos wrote:
I tried all kinds of
combinations such as delete, REBOOT, and simply relogin as root and other users to no avail. Konq fires up as root but as soon as the icons are painted it closes with the same error message.
Any other ideas? I wonder if deleting the contents of /tmp would 1. fix the problem, 2. screw up something else??? I see lots of stuff in there.
Well sports fans, Konqueror has been conquered! The fix was all in the Arts!! arts and arts-devel had not gone in as required. The old arts/ arts-devel rpms had not been replaced. i used kpackage to uninstall the old and install the new and now Konqueror work fine in Super User mode. Can someone tell me what the Modular software synthesizer has to do with preventing Konqi from running in SU mode??? I'm still gonna get some chicken bones for this computer room. ra
<snip>
Well sports fans, Konqueror has been conquered! The fix was all in the Arts!! arts and arts-devel had not gone in as required. The old arts/ arts-devel rpms had not been replaced. i used kpackage to uninstall the old and install the new and now Konqueror work fine in Super User mode.
I have checked to see if the new version was installed in mine and it is but Konqueror still refuses to stay running
Can someone tell me what the Modular software synthesizer has to do with preventing Konqi from running in SU mode???
Not sure
I'm still gonna get some chicken bones for this computer room.
Well I'm about ready to perform a Voodoo ritual on this thing. I do not use the su filemanager all that offen but I do want it to work. Glad that worked for you. -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
On 02/01/2003 08:44 PM, Marshall Heartley wrote:
Well I'm about ready to perform a Voodoo ritual on this thing. I do not use the su filemanager all that offen but I do want it to work. Glad that worked for you.
I got the answer to this problem (or workaround) on the suse-kde list. Try this: from a konsole, sux - to root, then run konqueror. It will start. Then go to Settings>Configure Konqueror>Previews, and turn off file (and you might want to turn off a few more, IIRC all my preview types for root were enabled). Then, close it, and start it from the icon. It worked for me. Thanks Graham for the tip. Also, as an aside, another problem I had (and saw also here) was with the printing manager in Kcontrol center. It appears the printmgr.desktop file is missing in the kdebase package. I used mc to copy just this file from the latest kdebase I had (3.0.4-38), copied it to the correct locations in /opt/kde3 and /etc/opt/kde3, and it works again too. :-) HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Unfortunately, I am also having this problem and this does not help. I tried running it after "suxing" to root. The konqueror window comes up for about 2 seconds and then vanishes. The following message appears in the konsole: mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-rick is not owned by user So, still trying to figure it out. Rick On Sat, 2003-02-01 at 08:38, Joe Morris (NTM) wrote:
I got the answer to this problem (or workaround) on the suse-kde list. Try this: from a konsole, sux - to root, then run konqueror. It will start. Then go to Settings>Configure Konqueror>Previews, and turn off file (and you might want to turn off a few more, IIRC all my preview types for root were enabled). Then, close it, and start it from the icon. It worked for me. Thanks Graham for the tip.
On Sun, 2 Feb 2003 03:45, Rick Friedman wrote:
Unfortunately, I am also having this problem and this does not help. I tried running it after "suxing" to root. The konqueror window comes up for about 2 seconds and then vanishes. The following message appears in the konsole:
mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-rick is not owned by user
So, still trying to figure it out.
Have you removed all the /tmp/mcop-* directories and the ~/.mcop directories for each user (including root) and let KDE rebuild them? If not exit KDE and switch over to virtual terminal (ALT F2) and log in as root and remove the above directories. This is best done under "init 3". The other causes I have seen attributable to this problem is the arts programs not being updated. The other solution I found was to disable previews of the File. Although I suppect that this is hiding a library problem. -- Regards, Graham Smith ---------------------------------------------------------
Alle 18:26, sabato 1 febbraio 2003, Graham Smith ha scritto:
Have you removed all the /tmp/mcop-* directories and the ~/.mcop directories for each user (including root) and let KDE rebuild them?
This was the right solution for me, thanks Alessandro -- ICQ#194726326 -- ** Festina Lente **
On Saturday 01 February 2003 2:43 pm, Alessandro Casale wrote:
Alle 18:26, sabato 1 febbraio 2003, Graham Smith ha scritto:
Have you removed all the /tmp/mcop-* directories and the ~/.mcop directories for each user (including root) and let KDE rebuild them?
For me, All of the Above is the answer! After installing the arts stuff I had to go back and delete all the /tmp stuff Graham mentions, then it all came together. I did it by installing mc and using it as root to make all the changes. Luckily it worked doing it in init 5 so I got by without doing finger magic. My one remaining problem is the Print Manager dying and telling me I have some artifact left from the previous install. So far I havent found the cause. I'm going to try Joe's suggestions next. Thanks to all for the help. Richard
Graham,
I have solved my problem. I tried removing all the /tmp/mcop-*
direcotries and the ~/.mcop directories for each user (including root)
but the problem persisted.
I then checked the installation of the various arts rpms (arts,
arts-devel & arts-gmcop). They were all the new rpms which were installed
with the other KDE 3.1 rpms.
Once I disabled the preview of Files for root, I found that solved the
problem. Obviously, there is something going on but, what it is exactly,
I haven't the slightest idea.
Rick
On Sun, 2 Feb 2003 04:26:38 +1100, "Graham Smith"
Have you removed all the /tmp/mcop-* directories and the ~/.mcop directories for each user (including root) and let KDE rebuild them?
If not exit KDE and switch over to virtual terminal (ALT F2) and log in as root and remove the above directories. This is best done under "init 3".
The other causes I have seen attributable to this problem is the arts programs not being updated. The other solution I found was to disable previews of the File. Although I suppect that this is hiding a library problem. -- Rick Friedman rickfriedman@myfastmail.com Registered Linux user: #269579
Einstein: "God does not play dice." Bohr: "Stop telling God what to do." -- http://fastmail.fm - I mean, what is it about a decent email service?
On Sun, 2 Feb 2003 12:47, Rick Friedman wrote:
Graham,
I have solved my problem. I tried removing all the /tmp/mcop-* direcotries and the ~/.mcop directories for each user (including root) but the problem persisted.
I then checked the installation of the various arts rpms (arts, arts-devel & arts-gmcop). They were all the new rpms which were installed with the other KDE 3.1 rpms.
Once I disabled the preview of Files for root, I found that solved the problem. Obviously, there is something going on but, what it is exactly, I haven't the slightest idea.
Well this is weird, if I start Kong from a terminal using sux - it works with the preview of Files. Now if I use File Manager su mode the thing falls over. There is no error messages issued when using konqueror from the command line so I really don't know where the problem is. -- Regards, Graham Smith ---------------------------------------------------------
On Sun, 2 Feb 2003 15:02, Graham Smith wrote:
On Sun, 2 Feb 2003 12:47, Rick Friedman wrote:
Graham,
I have solved my problem. I tried removing all the /tmp/mcop-* direcotries and the ~/.mcop directories for each user (including root) but the problem persisted.
I then checked the installation of the various arts rpms (arts, arts-devel & arts-gmcop). They were all the new rpms which were installed with the other KDE 3.1 rpms.
Once I disabled the preview of Files for root, I found that solved the problem. Obviously, there is something going on but, what it is exactly, I haven't the slightest idea.
Well this is weird, if I start Kong from a terminal using sux - it works with the preview of Files. Now if I use File Manager su mode the thing falls over.
There is no error messages issued when using konqueror from the command line so I really don't know where the problem is.
Well I can duplicate the problem from the command line. If I use "sux" instead of "sux -" and run /opt/kde3/bin/konqueror it will crash if I have the preview mode for File turned on. The error message given is:- /tmp/mcop-graham is not owned by user So I suppect that when you use the File Manager Super User, kongueror is not using root's environmental variables. I have no idea how to alter this behaviour, so for now the preview mode stays off in the root KDE config. -- Regards, Graham Smith ---------------------------------------------------------
On Saturday 01 February 2003 14:38, Joe Morris (NTM) wrote:
On 02/01/2003 08:44 PM, Marshall Heartley wrote:
Well I'm about ready to perform a Voodoo ritual on this thing. I do not use the su filemanager all that offen but I do want it to work. Glad that worked for you.
I got the answer to this problem (or workaround) on the suse-kde list. Try this: from a konsole, sux - to root, then run konqueror. It will start. Then go to Settings>Configure Konqueror>Previews, and turn off file (and you might want to turn off a few more, IIRC all my preview types for root were enabled). Then, close it, and start it from the icon. It worked for me. Thanks Graham for the tip.
that worked for me as well, but does somone know why should previwes crash konqui this way? not that i need previews when being root, just curious on another issue: i had kdm being messed up again. I fixed through control centre and now it is back to normal, but i get an "unrecognized section in kdm_config" error message when looging in. Any clues? TIA fred
* Richard (ratcheson@earthlink.net) [030130 11:18]: ->On Thursday 30 January 2003 10:48 am, PL O'Smith wrote: ->> Richard, ->> I had about the same problem with Krusader (sig11) and Konqueror (using ->> kdesu). Konq came up and quickly shutdown. What I did was remove the ->> /tmp/mcop-(user) folder and Konq was pleased with that. It created a ->> new one on startup and it works great now as root file manager while ->> logged in as user. -> ->Patrick, ->I tried your suggestion but it did not do the trick. I tried all kinds of ->combinations such as delete, REBOOT, and simply relogin as root and other ->users to no avail. Konq fires up as root but as soon as the icons are ->painted it closes with the same error message. -> ->Any other ideas? I wonder if deleting the contents of /tmp would 1. fix the ->problem, 2. screw up something else??? I see lots of stuff in there. Deleting the following files/directories from /tmp will not harm anything... kde* ksocket* mcop* In your home directory delete the following.. .mcop* ~/.kde/socket-<machine name> ~/.kde/tmp-<machine name> I delete all of the above when I upgrade KDE. You don't want tmp files hanging around..specifically those created by another version of KDE. -- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
On Thursday 30 January 2003 2:27 pm, Ben Rosenberg wrote:
Deleting the following files/directories from /tmp will not harm anything...
kde* ksocket* mcop*
In your home directory delete the following..
.mcop*
~/.kde/socket-<machine name> ~/.kde/tmp-<machine name>
I delete all of the above when I upgrade KDE. You don't want tmp files hanging around..specifically those created by another version of KDE.
Oh boy, this is a toughie! I deleted all as you and others have suggested. Still no joy! I start konq from a console and it fails but no error messages! So I reinstall kdeaddons- konq and still have the same problem. Konqueror starts, the window is displayed then the icons are displayed in the window and pooof, it is all gone! If I login to root konq will not work at all. So now what?? This is frustrating! But thanks for the help. ra
Op donderdag 30 januari 2003 22:50, schreef Richard:
If I login to root konq will not work at all.
So now what?? This is frustrating! But thanks for the help.
rpm -qa | grep ^k are all kde packages kde-3.1 packages? -- Richard Bos Without a home the journey is endless
On Thursday 30 January 2003 3:50 pm, Richard Bos wrote:
rpm -qa | grep ^k are all kde packages kde-3.1 packages?
-- I only see one that is for sure not 3.1 and that is the kdeutility3-printing-3.0.4-5
I dont see it in the list of new KDE rpms. Just for grins here's the result of the grep. Can you see anything that is missing or maybe shouldn't be there??? I followed Anders howto and deleted everything in tmp and that didnt do any good. Guess I need to get some chicken bones to hang over machine. Richard grep output: richard:/home/richard # rpm -qa | grep ^k kdegraphics3-devel-3.1-62 ksymoops-2.4.5-58 kdegraphics3-fax-3.1-62 krpmbuilder-0.2.6-163 kdeartwork3-sound-3.1-62 kdeaddons3-kicker-3.1-46 kdoc-2.0a54-122 kdenetwork3-query-3.1-61 kbd-1.06-133 kdebase3-samba-3.1-51 kdegraphics3-kamera-3.1-62 kdebase3-devel-3.1-51 kdebase3-ksysguardd-3.1-51 kinternet-0.45-118 k3b-0.7.5-2 kdelibs3-devel-3.1-46 karchiver-3.0.1-99 kdebase3-nsplugin-3.1-51 kdegames3-card-3.1-62 kdelibs3-cups-3.1-46 kdenetwork3-3.1-61 kdegraphics3-tex-3.1-62 kdeutils3-printing-3.0.4-5 kssh-0.7-135 kdebindings3-java-3.1-33 kbear-2.0beta2-26 kdegames3-tactic-3.1-62 kdegraphics3-3.1-62 kdegraphics3-extra-3.1-62 kdegraphics3-postscript-3.1-62 kdenetwork3-chat-3.1-61 kdenetwork3-devel-3.1-61 kdenetwork3-lan-3.1-61 kdenetwork3-news-3.1-61 kdepim3-sync-3.1-62 kdeutils3-devel-3.1-58 kdeaddons3-games-3.1-10 kdenetwork3-lisa-3.1-61 kdebase3-SuSE-8.1-56 kdemultimedia3-video-3.1-46 korelib-1.0-2_tkc_suse81 kdebase3-kdm-3.1-51 kdebindings3-c-3.1-33 kdeaddons3-sound-3.1-46 kdebindings3-mozilla-3.1-33 kdeartwork3-xscreensaver-3.1-62 kdegames3-board-3.1-62 kdegraphics3-viewer-3.1-62 kdemultimedia3-devel-3.1-62 kdepim3-time-management-3.1-62 kdesdk3-devel-3.1-65 kdeutils3-3.1-58 kdemultimedia3-midi-3.1-46 kdemultimedia3-sound-3.1-46 kdebase3-extra-3.1-51 kdenetwork3-mail-3.1-61 kdenetwork3-dialup-3.1-61 kde2-compat-2.2.2-348 kalsatools-1.2.8-22 k_athlon-2.4.19-199 kapital-1.0-2_tkc_suse81 kdeaddons3-kate-3.1-46 kdeaddons3-konqueror-3.1-46 kdeadmin3-3.1-51 kdeartwork3-3.1-62 kdebase3-3.1-51 kdeedu3-3.1-63 kdegames3-3.1-62 kdegames3-arcade-3.1-62 kdelibs3-3.1-46 kdelibs3-devel-doc-3.1-46 kdepim3-3.1-62 kdepim3-organizer-3.1-62 kdesdk3-3.1-65 kdesdk3-translate-3.1-65 kdetoys3-3.1-61 kdeutils3-extra-3.1-58 kdeutils3-laptop-3.1-58
I only see one that is for sure not 3.1 and that is the kdeutility3-printing-3.0.4-5
The plot thickens! If I try to use the Print Manager I get an error message saying there was an error loading the module. and the details indicate there is an orphan module laying around. My printer works so will I screw it up by removing the old kde . . -printing module???? It appears that this module may be having some effect on root Konqi. I have looked around the kde site and cant find the new printing module. Am using CUPS. Is anyone else having the same trouble? ra
<snip>
Deleting the following files/directories from /tmp will not harm anything...
kde* ksocket* mcop*
In your home directory delete the following..
.mcop*
~/.kde/socket-<machine name> ~/.kde/tmp-<machine name>
I delete all of the above when I upgrade KDE. You don't want tmp files hanging around..specifically those created by another version of KDE.
-- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see. I have the same issue. I deleted the above files but it still dies. I was able to get a message the last time it died. It is printed below.
mcop warning: user defined signal handler found for SIG_PIPE, overriding /tmp/mcop-marshall is not owned by user. Amy clues? Thanks, -- Marshall "Nothing is impossible, We just do not have all the anwsers to make the impossible, possible."
participants (10)
-
Alessandro Casale -
Ben Rosenberg -
Federico Damonte -
Graham Smith -
Joe Morris (NTM) -
Marshall Heartley -
PL O'Smith -
Richard -
Richard Bos -
Rick Friedman