Announcement

Collapse
No announcement yet.

[Solved] Programs Crash and KDE Spontaneously Restarts!

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [Solved] Programs Crash and KDE Spontaneously Restarts!

    It seems to me that there are a lot of users on this forum with this problem. I too am now suffering the same. I really need some help with this issue because my system is unusable as it is now.

    Here's my latest syslog:

    Code:
    Aug 5 02:50:02 AMD-Phenom-II rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="894" x-info="[url]http://www.rsyslog.com"][/url] rsyslogd was HUPed, type 'lightweight'.
    Aug 5 02:50:07 AMD-Phenom-II anacron[1100]: Job `cron.daily' terminated
    Aug 5 02:50:07 AMD-Phenom-II anacron[1100]: Normal exit (1 job run)
    Aug 5 03:17:01 AMD-Phenom-II CRON[2512]: (root) CMD (  cd / && run-parts --report /etc/cron.hourly)
    Aug 5 03:25:02 AMD-Phenom-II kdm[910]: X server for display :0 terminated unexpectedly
    Aug 5 03:25:02 AMD-Phenom-II acpid: client 954[0:0] has disconnected
    Aug 5 03:25:02 AMD-Phenom-II acpid: client connected from 2638[0:0]
    Aug 5 03:25:02 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:25:02 AMD-Phenom-II acpid: client connected from 2638[0:0]
    Aug 5 03:25:02 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:27:07 AMD-Phenom-II kdm[910]: X server for display :0 terminated unexpectedly
    Aug 5 03:27:08 AMD-Phenom-II acpid: client 2638[0:0] has disconnected
    Aug 5 03:27:08 AMD-Phenom-II acpid: client 2638[0:0] has disconnected
    Aug 5 03:27:08 AMD-Phenom-II acpid: client connected from 3009[0:0]
    Aug 5 03:27:08 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:27:08 AMD-Phenom-II acpid: client connected from 3009[0:0]
    Aug 5 03:27:08 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:31:45 AMD-Phenom-II kdm[910]: X server for display :0 terminated unexpectedly
    Aug 5 03:31:45 AMD-Phenom-II acpid: client 3009[0:0] has disconnected
    Aug 5 03:31:45 AMD-Phenom-II acpid: client 3009[0:0] has disconnected
    Aug 5 03:31:45 AMD-Phenom-II acpid: client connected from 3394[0:0]
    Aug 5 03:31:45 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:31:45 AMD-Phenom-II kernel: [ 3448.977939] NVRM: Xid (0004:00): 28, CCMDs 00000001 00007476 ffffffff ffffffff 00000000
    Aug 5 03:31:50 AMD-Phenom-II acpid: client connected from 3394[0:0]
    Aug 5 03:31:50 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:50:16 AMD-Phenom-II kdm[910]: X server for display :0 terminated unexpectedly
    Aug 5 03:50:16 AMD-Phenom-II acpid: client 3394[0:0] has disconnected
    Aug 5 03:50:16 AMD-Phenom-II acpid: client 3394[0:0] has disconnected
    Aug 5 03:50:16 AMD-Phenom-II acpid: client connected from 4347[0:0]
    Aug 5 03:50:16 AMD-Phenom-II acpid: 1 client rule loaded
    Aug 5 03:50:17 AMD-Phenom-II acpid: client connected from 4347[0:0]
    Aug 5 03:50:17 AMD-Phenom-II acpid: 1 client rule loaded
    "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

    #2
    Re: Lucid Lynx Reboots!

    I just finished building my new system and 10.04 LL is the first OS installed. I'm seriously considering replacing LL with 9.04 KK to verify or eliminate that the OS as the problem. My temps are good and my voltages are good, but I keep rebooting and always at the most inopportune times of course.

    I've read others' reboot problems which is why I uninstalled nepomuck and its associated db. I thought that was the problem, but apparently not. Please advise!!!
    "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

    Comment


      #3
      Re: Lucid Lynx Reboots!

      Originally posted by mhumm2

      I thought that was the problem, but apparently not. Please advise!!!
      I'm having a hard time believing that the cause of rebooting is the OS, but funny things happen sometimes. By all means, install a different OS and test it. Start with Kubuntu 9.10 if you wish -- you could also try Ubuntu 10.04, which would isolate KDE from Gnome, in case that is where the issue lies.

      Comment


        #4
        Re: Lucid Lynx Reboots!

        I don't see any reboots in your log. I do see several X restarts. So is your computer actually rebooting (usually beeps, then the bios screen comes up) or is X crashing and restarting (screen goes black and returns you in a minute or less to the log-in screen)?

        If it's actually rebooting and it's not logged, it's not likely your OS - because it would log the reason for the reboot.

        Please Read Me

        Comment


          #5
          Re: Lucid Lynx Reboots!

          Two great replies!!! Thank you.

          1. dibl -- I really thought nepomuk was causing the problem, but it's happening AFTER I uninstalled the program. That's what I meant. And, yes, 9.10 probably would be a good choice as well as Ubuntu 10.04 since it does appear now to be a KDE issue (see #2) and not the OS.

          2. oshunluvr -- Good catch; You're correct, my system is not rebooting, but KDE is.

          What do you guys need from me (log files, sys files, etc) to fix this?
          "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

          Comment


            #6
            Re: [Modified to be more accurate] KDE Spontaneously Restarts!

            Start by noting the exact time your next X restart occurs. Then open up /var/log/messages and post the 20-30 lines that occur just before and just after the restart...

            Please Read Me

            Comment


              #7
              Re: [Modified to be more accurate] KDE Spontaneously Restarts!

              Okay. I was burning a Kubuntu CDR and all of a sudden kb3 crashes and I have a half-burned drink coaster!

              Syslog prior to crash:

              Code:
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.239476] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.239480] end_request: I/O error, dev sr0, sector 0
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.241431] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.241434] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.241436] sr 3:0:0:0: [sr0] Add. Sense: Illegal mode for this track
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.241439] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.241444] end_request: I/O error, dev sr0, sector 0
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.243739] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.243741] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.243744] sr 3:0:0:0: [sr0] Add. Sense: Illegal mode for this track
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.243746] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.243751] end_request: I/O error, dev sr0, sector 0
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.245115] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.245117] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.245120] sr 3:0:0:0: [sr0] Add. Sense: Illegal mode for this track
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.245122] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.245127] end_request: I/O error, dev sr0, sector 0
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.246755] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.246758] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.246760] sr 3:0:0:0: [sr0] Add. Sense: Illegal mode for this track
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.246762] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.246766] end_request: I/O error, dev sr0, sector 0
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.248301] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.248303] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.248305] sr 3:0:0:0: [sr0] Add. Sense: Illegal mode for this track
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.248308] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 01 00
              Aug 6 22:24:45 AMD-Phenom-II kernel: [ 4603.248312] end_request: I/O error, dev sr0, sector 0
              I'd say I have a problem with my DVD/CDR combo drive. Now what?
              "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

              Comment


                #8
                Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                I just tried to play a DVD and it does not! It did a few weeks ago when I installed 10.04. So what's changed? I'm using Dragon Video Player.

                After I umounted and ejected the DVD, I tried to find the make and model numbers for you in dmesg. Have you ever seen a dmesg like this:

                Code:
                [ 6614.038908] Buffer I/O error on device sr0, logical block 3910426
                [ 6614.038915] Buffer I/O error on device sr0, logical block 3910427
                [ 6614.078596] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                [ 6614.078606] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
                [ 6614.078615] sr 3:0:0:0: [sr0] Add. Sense: Read of scrambled sector without authentication
                [ 6614.078627] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 3b ab 1a 00 00 02 00
                [ 6614.078644] end_request: I/O error, dev sr0, sector 15641704
                [ 6614.078652] Buffer I/O error on device sr0, logical block 3910426
                [ 6614.078659] Buffer I/O error on device sr0, logical block 3910427
                [ 6614.150393] sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
                [ 6614.150404] sr 3:0:0:0: [sr0] Sense Key : Illegal Request [current] 
                [ 6614.150414] sr 3:0:0:0: [sr0] Add. Sense: Read of scrambled sector without authentication
                [ 6614.150427] sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 3b ab 1a 00 00 02 00
                [ 6614.150446] end_request: I/O error, dev sr0, sector 15641704
                [ 6614.150455] Buffer I/O error on device sr0, logical block 3910426
                [ 6614.150463] Buffer I/O error on device sr0, logical block 3910427
                [ 6695.174434] UDF-fs: Partition marked readonly; forcing readonly mount
                [ 6695.208833] UDF-fs INFO UDF: Mounting volume 'RIO_BRAVO', timestamp 2001/01/24 20:10 (1ed4)
                This looks like my syslog instead of my dmesg file.

                "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                Comment


                  #9
                  Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                  After a reboot, I have my dmesg back. I must have messed something up with a bad grep command. Anyway, here's my optical drive as it is in dmesg:

                  Code:
                  [  1.777866] ata2.00: ATAPI: ATAPI  iHAS424  Y, ZL1U, max UDMA/100
                  .
                  [  1.779733] ata2.00: configured for UDMA/100
                  [  1.781498] scsi 1:0:0:0: CD-ROM      ATAPI  iHAS424  Y   ZL1U PQ: 0 ANSI: 5
                  [  1.785776] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
                  [  1.785779] Uniform CD-ROM driver Revision: 3.20
                  [  1.785839] sr 1:0:0:0: Attached scsi CD-ROM sr0
                  [  1.785867] sr 1:0:0:0: Attached scsi generic sg1 type 5
                  Nothing suspicious that I can see. I do though have some lines that I don't like. Here they are as excerpts:

                  Code:
                  [  0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it.
                  .
                  .
                  .
                  [  0.388224] Scanning for low memory corruption every 60 seconds
                  I have no idea about this.


                  Code:
                  [  0.248674] ACPI Warning: Incorrect checksum in table [OEMB] - 70, should be 6F (20090903/tbutils-314)
                  [  0.248919] ACPI: No dock devices found.
                  [  0.249244] ACPI: PCI Root Bridge [PCI0] (0000:00)
                  Do I have an ACPI issue?


                  Code:
                  [  10.469238] i2c i2c-0: nForce2 SMBus adapter at 0x600
                  [  10.469242] ACPI: resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f]
                  [  10.469244] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
                  [  10.469245] nForce2_smbus 0000:00:01.1: Error probing SMB2.
                  Hmmm, nForce2 is my NorthBridge chip set and video card.


                  Code:
                  [  10.606710] nvidia: module license 'NVIDIA' taints kernel.
                  [  10.606712] Disabling lock debugging due to kernel taint
                  This doesn't look good to me. Do I have a video driver conflict?


                  Code:
                  [  11.215479] EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
                  [  11.263225] EXT4-fs (sdb1): mounted filesystem with ordered data mode
                  Okay, I ran e2fsck on sdb1 which is my data HDD. It ran without a problem and displayed no problems. Doesn't Kubuntu run a check disk fs every 30 or so boot ups automatically or is that only on the boot drive (sda1)?

                  I realize that the dmesg can change with every system boot, but some of these items are constants and they don't look good to me. Do any of them indicate a problem that could account for the symptoms I have? Thanks.



                  "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                  Comment


                    #10
                    Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                    looking at the first log you posted - you didn't capture the restart point. You see a message about X signals or similar. Those dvd/cd errors are a known issue (not problem - just bad messages) and in theory wouldn't cause your issue anyway. Look in your Xorg.0.log and .1. file for errors too.

                    "nvidia taints kernel" is the correct message if you have the nvidia driver installed.

                    The bios, acpi and RAM erros are troubling - do some web searching on them. Make sure you have the latest bios for your mobo and do some web searching on your chipset vs. kernel version.


                    Please Read Me

                    Comment


                      #11
                      Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                      So far, during this boot-up, I've not had an X restart. In fact the only issue I had was Dolphin crashing as soon as I tried to run it. I closed the crash screen (opting not to report a bug) and tried it again. Dolphin came right up without a problem.

                      -- My Xorg.0.log file looks fine; no errors.

                      -- I running the latest AMI BIOS of 0603 (6 core support) (03/19/2010).

                      -- Firefox just crashed again, but in an unusual way. FF just disappears from my display with no crash screen at all. when I bring FF back up, it starts where I left off once it reloads all the open tabs (including this post btw). or it brings up a FF message that an embarrassing situation just occurred and FF had to reboot. Either way, I don't see any evidence of that in my log files.

                      What generates a syslog entry anyway? It's almost noon local and the last entry for syslog was made 2 hours ago. What log entry would capture a program crash if any? So far the only crashes I've experienced are: KWin (which is solved I think), FF, and Dolphin and only Dolphin provides a crash screen to report a bug.

                      I'm still researching the RAM and ACPI issues.

                      "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                      Comment


                        #12
                        Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                        do some searching on the dolphin thing - various causes for that. FF crashes on me once a week or so. I haven't bothered to try and track it down.

                        One way to see an application crash is to launch it from a terminal rather than the menu. Often there will be error output in your terminal after the crash.

                        Most logged errors will be mirrored to messages so typing "dmesg" in a terminal will show you the latest output.

                        Please Read Me

                        Comment


                          #13
                          Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                          That's some great information. Thanks.

                          gnubg (backgammon game) just crashed and here's the syslog output (last few lines):

                          Code:
                          Aug 7 22:37:04 AMD-Phenom-II kernel: [  32.180006] eth0: no IPv6 routers present
                          Aug 7 22:44:22 AMD-Phenom-II kernel: [ 471.041976] NVRM: Xid (0004:00): 6, PE0003 
                          Aug 7 22:53:20 AMD-Phenom-II kernel: [ 1008.461786] gnubg[2065]: segfault at 4009b719 ip 0012ce94 sp bfb1d9c0 error 4 in libgdk-x11-2.0.so.0.2000.1[110000+93000]
                          I suppose this could be a problem with gnubg, but it never crashed in 9.10 which was on my old computer system. Maybe a new OS version loaded on new computer hardware wasn't so smart after all. Again LL provided no notification that gnubg was misbehaving nor did I get the bug report window.
                          "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                          Comment


                            #14
                            Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                            Okay oshunluvr;

                            I needed to fix something else (something that I really can fix if you can believe that) and so I ran dolphin via a terminal as su. Once I got this output, I just shut dolphin back down again and decided to post the output.

                            Code:
                            mark@AMD-Phenom-II:~$ sudo dolphin
                            Error: "/var/tmp/kdecache-mark" is owned by uid 1000 instead of uid 0.
                            Error: "/tmp/kde-mark" is owned by uid 1000 instead of uid 0.
                            mark@AMD-Phenom-II:~$ Error: "/tmp/ksocket-mark" is owned by uid 1000 instead of uid 0.
                            QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
                            QFileSystemWatcher: failed to add paths: /home/mark/.config/ibus/bus
                            Bus::open: Can not get ibus-daemon's address. 
                            IBusInputContext::createInputContext: no connection to ibus-daemon 
                            dolphin(2672)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/usr/share/mime/magic"
                            dolphin(2672)/kdecore (services) KMimeTypeFactory::parseMagic: Now parsing "/home/mark/.local/share/mime/magic"
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            dolphin(2672)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
                            kDebugStream called after destruction (from void KDirWatchPrivate::removeEntry(KDirWatch*, KDirWatchPrivate::Entry*, KDirWatchPrivate::Entry*) file ../../kio/kio/kdirwatch.cpp line 950)
                            Cancelled INotify (fd 9, 1) for "/home/mark/.local/share//user-places.xbel"
                            Surely this can't be correct can it?
                            "If you're in a room with another person who sees the world exactly as you do, one of you is redundant." Dr. Steven Covey, The 7-Habits of Highly Effective People

                            Comment


                              #15
                              Re: [Modified] Programs Crash and KDE Spontaneously Restarts!

                              Bad boy: Sudo is for CLI programs only! The correct way to run dolphin (and any other GUI program) as root is kdesudo.

                              In this particular instance, another alternative is to install the root-actions service menu (available from Rog's ppa) then you can take root action from your normal dolphin session with a click and a password.

                              I suspect maybe this isn't the only time or program you may have run using sudo. You should check your /tmp and /home (including all hidden files) to see if you're being "blocked" because root owns a file meant for you.

                              My searching reveals you're not the only one with the gnubg crash. It seems related to libgtk2.0 package and video drivers/DRI.

                              Likely, if you don't use 3d the crash will go away. Of course, then you won't have 3d...

                              Please Read Me

                              Comment

                              Working...
                              X