Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: Official openSUSE-11.2 KDE-4.3.5 Update went well

  1. #11
    Join Date
    Jun 2008
    Location
    Phoenix, AZ, US
    Posts
    188

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    Quote Originally Posted by oldcpu View Post
    I've read some users have had major problems with dolphin crashing in KDE4. ... I'm wondering if the same is true in KDE-4.3.5. I have not noticed it thus far, but then I also note I have a rabbits foot when it comes to openSUSE hiccups, so my experiences are often very unrepresentative.


    I had the same problem when I first installed OS 11.2 with KDE (4.2?, or whatever it came with - I don't remember now. ) I still use the Midnight Commander in a terminal for roaming the file systems most of the time, but Krusader works well too.
    Go for it! You can always re-install...

    Registered Linux User #452291

    Windows Vista Boot Error: (S)hout, (P)arty, (D)ance, (L)inux? (L/L)?

  2. #12
    Join Date
    Jul 2008
    Location
    Nottingham, UK
    Posts
    37

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    Quote Originally Posted by oldcpu View Post
    I've read some users have had major problems with dolphin crashing in KDE4. ... I'm wondering if the same is true in KDE-4.3.5. I have not noticed it thus far, but then I also note I have a rabbits foot when it comes to openSUSE hiccups, so my experiences are often very unrepresentative.
    I think (although I can't be 100% sure) that Dolphin started crashing randomly in 4.3.1 only after I'd enabled nepomuk. Since the update to 4.3.5, I have not had a single issue. This has been the most stable KDE4 installation yet.

  3. #13
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,595
    Blog Entries
    38

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    Quote Originally Posted by colinpendred View Post
    I think (although I can't be 100% sure) that Dolphin started crashing randomly in 4.3.1 only after I'd enabled nepomuk. Since the update to 4.3.5, I have not had a single issue. This has been the most stable KDE4 installation yet.
    I've been reviewing hundreds of videos from my last vacation, using dolphin to launch them one at a time, review, and then close the video. Every now and then I have noticed dolphin closing after I close the video application (prior to opening the next video) and I have not figured out yet if it was a dolphin bug or an oldcpu faux-pas. I did catch myself once immediately closing dolphin after closing a video application, when that was not my intention. I closed dolphin so quickly, I was not even consciously aware of doing it until I paused for a second and asked myself - what am I doing ?? For some reason, I have an ingrained automatic reaction (that I need to fight) to close dolphin after I close an application !!

    ... but its possible there is still a bug in dolphin with un-expected closures. I just can't be certain yet, due to my own carelessness/bad habits.

  4. #14

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    Yes, my update(s) of KDE to 4.3.5 also went well but there still appears to be a couple of glitches in the software. I wonder if anybody can reproduce the following:

    (1) log on to an openSUSE 11.2, KDE4 desktop as an ordinary user.

    (2) open a Konsole as an ordinary user [so via the classic menu this is Green-button - System - Terminal - Konsole (Terminal)].

    (3) verify the ordinary Konsole is running by typing some garbage in at the command prompt.

    (4) open another Konsole as a super user [so via the classic menu this is Green-button - System - Terminal - Terminal - Super User Mode]

    (5) verify both the ordinary and super Konsoles are running by typing some garbage in their the command prompts.

    (6) shutdown the super Konsole by clicking on the 'x' at the top right of the window or using Ctrl-Shift-Q.

    (7) observe that the ordinary Konsole has now crashed since nothing can be typed into the command prompt and clicking on the 'x' at the top right of the windows has no effect.

    (8) Deduce bug.

    However, if the second Konsole is an ordinary Konsole, then clicking on the 'x' allows the first Konsole to continue working.

    Thinking that it might be something to do with permissions, I reran the test with two ordinary Konsoles and elevating the second to a super Konsole by typing 'su' and entering the root password. However, 'x'ing the second (now super) Konsole still allowed the first (ordinary) Konsole to continue running.

    If you go back to the first test and close the super Konsole, by typing 'exit' followed by [enter], then the ordinary Konsole survives.

    This bug occurs on both an x86 and an x86_64 version of openSuse 11.2, so it appears to be reproducible.

    Can anybody else confirm this? Thanks.

  5. #15
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,595
    Blog Entries
    38

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    Quote Originally Posted by plodder View Post
    Can anybody else confirm this? Thanks.
    I can reproduce that crash (on KDE-4.3.5) !! Good catch !

    I confess I would never open a konsole via those methods (I have a konsole on my desktop that I 'just click' on) but never the less, that bug should be squashed. Perhaps you could raise a bug report on it ? Submitting Bug Reports - openSUSE

  6. #16

    Default Re: Official openSUSE-11.2 KDE-4.3.5 Update went well

    OK, thanks a lot oldcpu for confirming that bug. I will get around to posting a report to Suse shortly.

    Actually the scenario for the crash, I outlined, was just to make sure any user could reproduce it with the standard Suse KDE setup. I do, in fact, launch my terminals from the 'Konsole Profiles' widget on the taskbar and that can also reproduce the same bug.

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •