For the first month I had openSUSE 11.2 on this computer, there was no problem with dolphin. This is a recent thing. So I’m thinking it’s either some recent update that caused it or something else, but not the system itself.
Is there any way to have some logger going in terminal that keeps track of all the calls made when I do anything (like click to open dolphin) and that’ll also show errors? Or something that gets logged to a file? That way when it happens, I can look there and find an error.
>
>caf4926;2104318 Wrote:
>> Open a terminal and type
>>
>> >
>Code:
>--------------------
> > > dolphin
>--------------------
>> >
>
>It just hangs forever when I do that.
If you are still having trouble please try
dolphin > dol_log1 2>&1 &
wait 10 seconds and do it again like this
dolphin > dol_log2 2>&1 &
note the change in filename.
then ps -ef to see if it is running and kill it if it is.
then try to view the files (presuming that they exist).
>
>JosephKK;2108972 Wrote:
>> On Fri, 15 Jan 2010 22:46:01 GMT, 6tr6tr
>> <6tr6tr@no-mx.forums.opensuse.org> wrote:
>>
>> >
>> >caf4926;2104318 Wrote:
>> >> Open a terminal and type
>> >>
>> >> >
>> >Code:
>> >--------------------
>> > > > dolphin
>> >--------------------
>> >> >
>> >
>> >It just hangs forever when I do that.
>>
>> If you are still having trouble please try
>> -------------------
>> dolphin > dol_log1 2>&1 &
>> -------------------
>> wait 10 seconds and do it again like this
>> -------------------
>> dolphin > dol_log2 2>&1 &
>> -------------------
>>
>> note the change in filename.
>>
>> then ps -ef to see if it is running and kill it if it is.
>>
>> then try to view the files (presuming that they exist).
>
>Just to be sure I’m entering the proper commands, you’re saying at the
>command line type this:
>
>dolphin > dol_log1 2>&1 &
>
>
>In other words, type:
>
>dolphin
>space
>greater than symbol
>space
>dol_log1
>space
>number two
>greater than
>ampersand
>number one
>space
>ampersand
>
>Is that correct?
>Thanks!
>
>Yes
>
>Here is a hint you can copy and past complex lines like that into the
>console window just use the menu to paste until you get the hang of it.
> On Tue, 26 Jan 2010 18:06:01 GMT, 6tr6tr
> <6tr6tr@no-mx.forums.opensuse.org> wrote:
>
>>
>>JosephKK;2108972 Wrote:
>>> On Fri, 15 Jan 2010 22:46:01 GMT, 6tr6tr
>>> <6tr6tr@no-mx.forums.opensuse.org> wrote:
>>>
>>> >
>>> >caf4926;2104318 Wrote:
>>> >> Open a terminal and type
>>> >>
>>> >> >
>>> >Code:
>>> >--------------------
>>> > > > dolphin
>>> >--------------------
>>> >> >
>>> >
>>> >It just hangs forever when I do that.
>>>
>>> If you are still having trouble please try
>>> -------------------
>>> dolphin > dol_log1 2>&1 &
>>> -------------------
>>> wait 10 seconds and do it again like this
>>> -------------------
>>> dolphin > dol_log2 2>&1 &
>>> -------------------
>>>
>>> note the change in filename.
>>>
>>> then ps -ef to see if it is running and kill it if it is.
>>>
>>> then try to view the files (presuming that they exist).
>>
>>Just to be sure I’m entering the proper commands, you’re saying at the
>>command line type this:
>>
>>dolphin > dol_log1 2>&1 &
>>
>>
>>In other words, type:
>>
>>dolphin
>>space
>>greater than symbol
>>space
>>dol_log1
>>space
>>number two
>>greater than
>>ampersand
>>number one
>>space
>>ampersand
>>
>>Is that correct?
>>Thanks!
>
> Yes, that is the intent.
No help for you, but this has begun to be a problem here as well - whether
dolphin opens or not has become a crap shoot. Mine will generally open on
the 2nd or 3rd try. I also have frequent crashes with dolphin reported as
“seg fault”, if that may also be a symptom for you.
No time to read the entire thread. Did you try to remove/rename the dolphinrc from ~/.kde4/share/config, and the dolphin folder from ~/.kde4/share/apps ? Mind, do that while not being logged in on KDE4.
Or, open a terminal window and start dolphin from there, by typing “dolphin”. It’s output will be in the terminal, so the last info after a crash is about the crash itself.
>
> No time to read the entire thread. Did you try to remove/rename the
> dolphinrc from ~/.kde4/share/config, and the dolphin folder from
> ~/.kde4/share/apps ? Mind, do that while not being logged in on KDE4.
>
> Or, open a terminal window and start dolphin from there, by typing
> “dolphin”. It’s output will be in the terminal, so the last info after a
> crash is about the crash itself.
No, it’s just erratic enough to be a PITA, not a show stopper. I’m mainly
testing 11.2/KDE4 before deploying it - 11.1 is still the production code
and looks to stay that way for a while. The situation has been described
and I’ll try the fixes as they show up. Right now, updating the whole KDE4
package sounds like the best path rather than fighting the glitches in 4.3.1
default install. That just isn’t ready for prime time yet and I don’t have
the time to fight it on multiple installations.
>
>Knurpht;2111265 Wrote:
>> No time to read the entire thread.
>
>You remind me of ‘xkcd - A webcomic of romance, sarcasm, math, and
>language - By Randall Munroe’ (http://xkcd.com/208/)
It is unclear how you would like me to apply that here.
Dolphin did not open when I clicked the icon on the task bar. This had gone away for a while (after I deleted .kde4) but now it’s back. That’s the same thing as the first time this appeared when I first installed opensuse 11.2, this did not occur, but after a while it started happening.
I assume this is in openSUSE-11.2 with KDE-4.3.5 ? A silly question - but I assume this is not your mouse acting up ? I assume you checked for an error by typing “dolphin” in a konsole and saw nothing?
Unfortunately with KDE-4.3.5 I can’t reproduce the error, so I can’t be of much help.
That’s correct. The “App Feedback” shows when starting from the icon (so I know I clicked it) and when doing from command line I was unable to get an error. And yes, it’s KDE 4.3.5 with openSUSE 11.2.
This is weird because it doesn’t occur for a number of days after deleting .kde4 and then starts happening again and then everything gets slower. I’m afraid I’m just going to have to keep deleting that folder and then copying back in needed audio configs.
Well…the thing is it sometimes works, sometimes doesn’t. So I doubt re-adding it will solve this issue. Usually when it doesn’t work, trying it again a few seconds later will work. And deleteing .kde4 makes the problem go away for about 2-3 weeks. So something else has to be causing this.