kde 4.1 from /testing issues - Slackware

This is a discussion on kde 4.1 from /testing issues - Slackware ; I managed to upgrade to the kde 4.1 packages from /testing. I'm running -current Prior to this, I ran the remove-kde4.sh script (to get rid of any residual packages from previous attempts), as well as the remove-kde3.sh script. Then I ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: kde 4.1 from /testing issues

  1. kde 4.1 from /testing issues

    I managed to upgrade to the kde 4.1 packages from /testing. I'm
    running -current Prior to this, I ran the remove-kde4.sh script (to get rid
    of any residual packages from previous attempts), as well as the
    remove-kde3.sh script. Then I ran upgrade-pkg --install-new for all the
    packages in the testing/kde group. Here's what I've noticed so far:

    1) It is really, really slow with my nvidia car, somewhat mitigated if I
    turn off the fancy compositing settings from within kde. Lots of hanging
    for several seconds at a time. Apparently this is a driver bug, not a
    problem with KDE, so I'll have to wait for a new binary from nvidia.

    2) After KDE 4.1 has been running, it has the habit of crashing out to the
    terminal periodically (within 30-45 minutes usually). I get no error
    messages on the screen, just X dies and I'm stuck at a tty screen with a
    flashing "_". I am unable to switch to any other virtual consoles, ctrl-C
    out of it, or anything. I can however do the sysrq key combo to reboot the
    system, or ssh into the box and clean things up. This occurs both when
    actively using the desktop and when it's sitting idle. By starting kde via
    ssh, I was able to get the following error messages:
    http://pastebin.com/m4a66b637

    3) After the above issue occuring several times, firefox stopped working
    completely from within KDE. I could launch it from the menu, and the
    feedback cursor would bounce up and down, but nothing happened. running
    from konsole just had the command sit there with no output, and no cpu
    usage. This happens with the stock firefox package, a nightly I
    downloaded, and also if I try to run seamonkey, leading me to believe it's
    not just a residual process ruining things. If I switch to XFCE, firefox
    runs as expected.

    Items 2 and 3 are really bugging me. The first issue is avoidable if you
    don't mess with the panels or do anything really complicated with kwin, but
    the others are show-stoppers. Anyone have any ideas as to what could be
    wrong? Slackware-specific, or a general KDE bug?

  2. Re: kde 4.1 from /testing issues

    Well, I "solved" the firssefox issues. After KDE crashes from issue #2, I
    fixed things up by ssh'ing in, and running startx from the ssh console,
    which would bring up X on the ssh server. However, this broke ALSA apps,
    along with firefox. My workaround is, following a crash, restart X through
    ssh, exit from X, then the virtual consoles begin to work correctly. Then
    you can rerun X from the actual terminal, and firefox and alsa work fine.

    Still no luck on the crashing issue, though.

  3. Re: kde 4.1 from /testing issues

    On Sat, 16 Aug 2008 11:31:30 -0500, JD wrote:

    > 1) It is really, really slow with my nvidia car, somewhat mitigated if I
    > turn off the fancy compositing settings from within kde. Lots of hanging
    > for several seconds at a time. Apparently this is a driver bug, not a
    > problem with KDE, so I'll have to wait for a new binary from nvidia.
    >


    In last release (nvidia driver) this bag fixed.

    --
    Murat D. Kadirov

  4. Re: kde 4.1 from /testing issues


    "MD" wrote in message
    news:48a70cd6$0$2647$a726171b@news.hal-pc.org...
    > Well, I "solved" the firssefox issues. After KDE crashes from issue #2, I
    > fixed things up by ssh'ing in, and running startx from the ssh console,
    > which would bring up X on the ssh server. However, this broke ALSA apps,
    > along with firefox. My workaround is, following a crash, restart X
    > through
    > ssh, exit from X, then the virtual consoles begin to work correctly. Then
    > you can rerun X from the actual terminal, and firefox and alsa work fine.
    >
    > Still no luck on the crashing issue, though.



    Just curious, what would happen if you started in telinit 3 and ran startx?
    If X still crashed, you'd at least have local console access instead of
    having to ssh in.

    Tim



+ Reply to Thread