Fwd: Re: [suse-kde] ROOT: Konqueror problem
---------- Forwarded Message ----------
Subject: Re: [suse-kde] ROOT: Konqueror problem
Date: Saturday 19 June 2004 13:20
From: Stephen Boddy
Hi there! I have a problem with Konqueror (File Browser) when logged in as root: when I click on an directory Icon to enter that directory, I get the error message: "There appears to be a configuration error. You have associated Konqueror with inode/directoy, but it can't handle this file type." But filling in the directory path in the adress bar does not give any error??
Got to the status bar at the bottom of the file area, right click and, if checked, uncheck "Lock to current location" -> Is already unchecked. It was 'unavailable' until the navigation panel was shown, after that, "Lock to current location" was not checked.
At the same time, when I access the "/" directory by filling in the adress bar, Konqueror locks up fir about 15 secs before showing the content.
The above may fix this. What if you start a console and "ls" the / folder? Does that take 15 secs too? -> No, it doesn't. It took about 0.5 s.
Is it a bug or an installation error or a configuration error? Using Konqueror as user, there is no problem at all....
No, because they store user settings separately. -- Steve Boddy -- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e ------------------------------------------------------- -- Linux is like an indian tent: no Windows, no Gates and an Apache inside
On Saturday 19 June 2004 12:39, Laurent wrote:
---------- Forwarded Message ----------
Subject: Re: [suse-kde] ROOT: Konqueror problem Date: Saturday 19 June 2004 13:20 From: Stephen Boddy
To: suse-kde@suse.com On Saturday 19 June 2004 10:59, Laurent wrote:
Hi there! I have a problem with Konqueror (File Browser) when logged in as root: when I click on an directory Icon to enter that directory, I get the error message: "There appears to be a configuration error. You have associated Konqueror with inode/directoy, but it can't handle this file type." But filling in the directory path in the adress bar does not give any error??
Got to the status bar at the bottom of the file area, right click and, if checked, uncheck "Lock to current location"
-> Is already unchecked. It was 'unavailable' until the navigation panel was shown, after that, "Lock to current location" was not checked.
At the same time, when I access the "/" directory by filling in the adress bar, Konqueror locks up fir about 15 secs before showing the content.
The above may fix this. What if you start a console and "ls" the / folder? Does that take 15 secs too?
-> No, it doesn't. It took about 0.5 s.
Is it a bug or an installation error or a configuration error? Using Konqueror as user, there is no problem at all....
No, because they store user settings separately.
Sounds rather b*ggered I'm afraid. You could as an experiment copy roots .kde folder i.e. log out as root, log in to a virtual terminal, and in the /root folder enter: cp -pr .kde .kde_bak Go back to KDE and log back in as root and see if that cures the problem, though ideally you shouldn't log into KDE as root. If this works you could selectively copy back configs from the backup. -- Steve Boddy
On Saturday 19 June 2004 16:30, Stephen Boddy wrote:
Sounds rather b*ggered I'm afraid. You could as an experiment copy roots .kde folder i.e. log out as root, log in to a virtual terminal, and in the /root folder enter: cp -pr .kde .kde_bak
What does that command do? I'm still quite new to linux...¨Laurent
Go back to KDE and log back in as root and see if that cures the problem, though ideally you shouldn't log into KDE as root. If this works you could selectively copy back configs from the backup.
-- Steve Boddy
-- Linux is like an indian tent: no Windows, no Gates and an Apache inside
On Monday 21 June 2004 10:53, Laurent wrote:
On Saturday 19 June 2004 16:30, Stephen Boddy wrote:
Sounds rather b*ggered I'm afraid. You could as an experiment copy roots .kde folder i.e. log out as root, log in to a virtual terminal, and in the /root folder enter: cp -pr .kde .kde_bak
What does that command do? I'm still quite new to linux...¨Laurent
The commands cp --help and man cp will explain. Cheers, Leen
On Monday 21 June 2004 09:53, Laurent wrote:
On Saturday 19 June 2004 16:30, Stephen Boddy wrote:
Sounds rather b*ggered I'm afraid. You could as an experiment copy roots .kde folder i.e. log out as root, log in to a virtual terminal, and in the /root folder enter: cp -pr .kde .kde_bak
What does that command do? I'm still quite new to linux...¨Laurent
It copies the directory recursively (i.e. everything under it) and preserves permissions and timestamps.
Go back to KDE and log back in as root and see if that cures the problem, though ideally you shouldn't log into KDE as root. If this works you could selectively copy back configs from the backup.
-- Steve Boddy
-- Linux is like an indian tent: no Windows, no Gates and an Apache inside
-- Steve Boddy
On Wednesday 23 June 2004 00:07, Stephen Boddy wrote:
cp -pr .kde .kde_bak
Go back to KDE and log back in as root and see if that cures the problem, though ideally you shouldn't log into KDE as root. If this works you could selectively copy back configs from the backup.
It doesn't change a thing, the error message does still appear and accessing the "/" directory still takes about 15 secs. When I try to access the "/" dir., I have the following kernel messages in /var/log/messages: Jun 23 11:31:12 dhcppc0 kernel: cdrom: open failed. Jun 23 11:31:12 dhcppc0 submountd: mount failure, No medium found Jun 23 11:31:12 dhcppc0 kernel: subfs: unsuccessful attempt to mount media (256) Jun 23 11:31:12 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 submountd: mount failure, No such device or address Jun 23 11:31:13 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 kernel: subfs: unsuccessful attempt to mount media (256) Jun 23 11:31:13 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 submountd: mount failure, No such device or address Jun 23 11:31:13 dhcppc0 kernel: end_request: I/O error, dev fd0, sector 0 Jun 23 11:31:13 dhcppc0 kernel: subfs: unsuccessful attempt to mount media (256) Jun 23 11:31:16 dhcppc0 kernel: ISO 9660 Extensions: Microsoft Joliet Level 1 Jun 23 11:31:16 dhcppc0 kernel: ISOFS: changing to secondary root Jun 23 11:31:41 dhcppc0 kernel: cdrom: open failed. Jun 23 11:31:45 dhcppc0 kernel: cdrom: open failed. Jun 23 11:31:45 dhcppc0 submountd: mount failure, No medium found Jun 23 11:31:45 dhcppc0 kernel: subfs: unsuccessful attempt to mount media (256) Jun 23 11:31:49 dhcppc0 kernel: cdrom: open failed. Jun 23 11:31:54 dhcppc0 kernel: cdrom: open failed. Jun 23 11:31:54 dhcppc0 submountd: mount failure, No medium found Jun 23 11:31:54 dhcppc0 kernel: subfs: unsuccessful attempt to mount media (256) Jun 23 11:31:58 dhcppc0 kernel: cdrom: open failed. The clue might might be in these? Laurent Asorne -- Linux is like an indian tent: no Windows, no Gates and an Apache inside
participants (3)
-
Laurent
-
Leendert Meyer
-
Stephen Boddy