Slackware :: KDE Crash After Upgrade / Solution For This?
Nov 24, 2010
So I did an update to my slackware current and as many people here found that KDE crashes... Mine I am unable to find a fix for it.... I get the following error as I log in...
Warning Can not Open ConsoleKit Session Unable To Open Session: Failed To Connect to Socket: /var/run/dbus/system_bus_socket: No Such File or Directory.
Whenever i try to download anything from chromium, first downloading time just goes on increasing and after few seconds it crashes. This problem is not there in firefox..
I am running matlab 2010b on centOS5.6. Matlab opened without any error either in the computer terminal or in VNCSERVER. While running bench (of matlab) the session or the vncserver are crashing. In some cases the bench run for the first time without any problems, however it will crash the session or the vncserver on the 2-3 runs of the same code. Any idea how to solve this issue?
I run Slackware 13.1 x64. Problem is when I run eclipse, it works couple minuts and then crash. I run from shell and this is message what I got. code...
I have spent 20 minutes looking and can't find the solution. I just installed 10.10 and want 11.04 now. Don't ask me why I didn't just install Natty Narwhal, but I didn't. Now, when I run the update manager, it does not mention the update to 11.04. So I run check, nothing. I open the settings, check every option I can because what the heck, and nothing.
I ran the upgrade from 9 to 10.04. So far I have everything but wifi. There is no wifi access even through a menu bar icon. Any others with this problem who've found a solution?
After upgrading Centos 5.4 cluster nodes to 5.5 all virtual services failed to start. All virtual services are marked as 'failed'. The reason: new /usr/share/cluster/vm.sh requires 'which', but this is not reflected in rgmanager-2.0.52-6.el5.centos.
Solution: run 'yum -y install which' on all nodes, and reboot cluster. Hope that will save somebody hours of downtime.
Every time I start my computer, from the power button, it crash after 6 minutes. It only could be recovered from the reset button, not CTRL + ALT + DEL nor REISUB.
I think it only happens if I don't touch anything in that 6 minutes.
syslog show this during crash:
Code: Jun 10 07:46:21 antonio-desktop kernel: imklog 4.2.0, log source = /proc/kmsg started. Jun 10 07:46:21 antonio-desktop rsyslogd: [origin software="rsyslogd" swVersion="4.2.0" x-pid="725" x-info="http://www.rsyslog.com"] (re)start Jun 10 07:46:21 antonio-desktop rsyslogd: rsyslogd's groupid changed to 102
My exercise below is to check if glxgears crashes xorg of CentOS5.4 with Intel GM965 Chipset. Apparently I don't have luck in this case. Since the exercise failed, it means I will still stick to CentOS 5.2 (residing on a different partition) for a while, even though CentOS5.2 crashes glxgears too. After "yum upgrade" (done after moving all repos in /etc/yum.repos.d to elsewhere except CentOS-Base.repo and CentOS-Media.repo), I ran glxgears that consistently crashes CentOS5.2 xorg, an issue that upset me quite a bit.
During upgrade, I saw a line "grubby fatal error : unable to find a suitable template". I guess the my grub.conf is too confusing for the installer, but that is not big deal, I just used the kernel number 2.6.18-164 where it is applicable. Even this this new update, glxgears still crash the xorg (the screen froze and then a new login screen reappears). With this I am sure the 3D application might still crash the xorg from time to time. (I can still revert to CentOS5.2 with a tar file, but I am still thinking to just upgrade to Centos5.3 but I don't know how.)
I have just upgraded KDE to 4.5 but after reboot and login i can't see my desktop. Only cursor, blank screen, and a window says:
Plasma Workspaces - The KDE Crash Handler We are sorry, Plasma Workspaces closed unexpectedly. You can help us improve KDE software by reporting this error
Details: Executable: KDEinit4 PID:3787 Signal: 8 (Floating Point Exception)
My PC: AMD Athlon(tm) 64 X2 Dual Core Processor 4000+ GeForce 6100 nForce 405 openSUSE 11.3 32-bit Using nVidia driver.
I've been using Ubuntu since Feisty Fawn, so I've been around the block when it comes to upgrades. From 9.10 to 10.04 I did a clean install, but I decided to try my luck with a web upgrade to 10.10. Well, so far it looks like that was a bad idea. I can't stay in gdm for more than about 1.5 mins before it crashes and drops me back to the greeter. Honestly, I'm not sure exactly what's crashing, but I'll append what logs I think will give some info.
Just tried to upgrade my mythbuntu box from lucid to maverick.
It crashed during the upgrade. On re-boot it now stops at a dialog telling me its running in low graphics mode because it cannot load/find the nvidia drivers. I am unable to close the dialog. No mouse, no keyboard.
ESC will not let me interrupt the boot to get to a recovery console.
Both programs were working just fine yesterday before the upgrade to Ubuntu 11.04.
Opening Gimp results in many error pop-ups on being unable to locate module gimp and module gimpfu. I tried to uninstall and reinstall, and the installation fails with this message:
The following packages have unmet dependencies:
gimp : Depends: libgimp2.0 (<= 2.6.11-z) but 2.7.3-2010072701~ll is to be installed Depends: gimp-data (<= 2.6.11-z) but 2.7.3-2010072701~ll is to be installed
This may be because of times in the past where I tried to compile Gimp. Do I need to clean up my repositories list? (in that case, any way to get a fresh one?)
Inkscape doesn't open at all, instead the terminal message says this:
inkscape: error while loading shared libraries: libwpg-0.1.so.1: cannot open shared object file: No such file or directory
I'm not sure what's wrong in the case of Inkscape though, although I did compile a few versions long ago I was using the "normal" version from the Ubuntu repositories afterwards.
I often connect to my main box via ssh and then run 'screen.' The client machine is running Slackware64 13.1, the box I connect to is running Slackware64-currentSome time ago I noticed the following phenomenon:1. Sometimes (relatively often) cli apps just freeze usually at the very beginning (when they start) and I have to either use Ctrl+C or kill a screen window. It happens both with screen an without it. I've noticed it with vim (never with emacs -nw, or nano), "slackpkg upgrade-all", sbopkg).2. Sometimes/some CLI programs display 'weird' characters. For example, sbopkg's border. It does not happen when I run the same app locally.Is it something to do with encoding? It happens both with and without 'screen'.Both 1 and 2 happen with sakura (my main terminal emulator), terminal, konsole and xterm.
I was trying to run record it now, and switched from recordmydesktop to ffmpeg and it kept crashing. I tried it with the command line
Code: ffmpeg -r 30 -s 1680x1050 -f x11grab -i :0.0 -vcodec msmpg2v2 -qscale 2 filename.avi I have the following installed, but it's wanting libx264 which I don't see at slackbuilds.org:
[Code]....
Where should I start looking for missing things or...?
I also looked for xvidcap and kazam at slackbuilds.org but didn't see them there. Are those available?
After a recent update to Slack64 current, GL xscreensavers cause KDE to crash every single time they are run. The crash actually happens as the screensaver exits (ie it runs fine until a mouse or keyboard event, then crashes).
Here's the relevant Xorg output: Code: (EE) intel(0): [DRI2] DRI2SwapComplete: bad drawable
I have a new installation of Slackware 13.37 on an old Dell Optiplex P4. Right after installation (when I only had a root account) I found that X (regardless of window manager) would develop video problems after a few minutes (horizontal lines, slowdown -- though without crashing). A message board informed me that that there was a bug in my onboard Intel video chip that would require me to enable shadow buffering (which amounts to disabling 2D acceleration). I made the change in the Xorg.conf, and the issue disappeared.
However, once I finally got around to adding a new user, X began acting up again, though I have no idea whether it's related to the earlier problem. Now, after a few minutes, it actually crashes -- though only when started under the new user. Root still works fine. I'm new to Linux, and still trying to sort through all the different logging tools, so I'm not sure what I ought to be posting. Here's the relevant bit from Xorg.0.log:
After upgrade KDE to 4.7, I restarted system, when login, the klasma-desktop always crash. can't start.See, below picture:https://picasaweb.google.com/lh/phot...eat=directlinkAnd got below info:
Was running the upgrade through the manager this morning and the download got about 3/4 of the way and froze up making the system unresponsive I left this for an hour to see if it would resolve its self but no luck so as the installation hadn't begun I hit the power button. BIG mistake now when I try boot to 9.10 it hits a black screen with white ubuntu logo much like 9.10 but no loading bar. it just hangs at this now. I am currently posting this from a live usb I made from an ISO of 10.4 i downloaded on my girl friends windows machine. Is it possible to either fix the 9.10 installation or update the files on the 9.10 installation to 10.4 from the live disk(I have the option to make a 9.10 live disk if needed)?
Today I was prompted to upgrade to Ubuntu 9.1, and then again to 10.04
Doing these upgrades wreaked havoc on my system. I have been able to fix most of the problems that were caused but I am having trouble finding information on the following:
When I boot up the system and after passing the GRUB loader, the system freezes up at the login screen and I have to power down.
If I hit ESC at the GRUB screen and choose Kernel 2.6.32-25-generic (recovery mode) and then choose "failsafe graphic mode", then I am able to log in to GNOME as normal.
I just tried to upgrade my server to the latest version of Bind9 and the process fails gets frozen.First note that I have Bind in a chroot jail.When I try the upgrade, or the recommended "dpkg --configure -a", it displays this then hangs:Quote:
Setting up bind9 (1:9.7.0.dfsg.P1-1ubuntu0.1) ... * Stopping domain name service... bind9 rndc: connection to remote host closed
I have a Dell studio running ubuntu for two years now. I had ubuntu 10.04, but a few days ago, the update manager started to bug me that some stuff don't work properly and that I need to to a partial upgrade. I postponed that for a while, and all worked fine, but I finally had sometime and clicked "yes", all began collapsing:
1) the update manager crashed while updating.
2) I rebooted and ran it again. same crash at the same stage.
3) I decided, god knows why, to do a full upgrade to 10.10, which also crasehd.
Now it won't even boot. It always get stuck at a line saying "no IPv6 routers present" or something of that sort. when I switch off manually the wireless switch on the laptop, the boot gets stuck a bit earlier, on a line that says: "laptop login:"
EDIT: I just remembered something which might be important: I had a hibernation problem on the upgrade to 10.04, so I played around a bit with that. now it uses libgcrypt, and I remember I set up something manually then, but I can't remember what.
I was upgrading my laptop from 10.10 to 11.04. The laptop crashed part way through the upgrade (fairly far in, at least an hour after downloads completed, a few minutes after grub installer asked some questions). The crash was from another issue besides the update
Now when the computer boots it immediately goes into kernal panic (black screen, flashing caps lock light). when selecting recovery mode, it boots for about a 5 seconds then hangs.
I can however at grub select Previous versions of ubuntu > 2.6.35-28 and it will boot succesffully and run without error. Currently running like this to post this message. For the most part everything looks as if it has upgraded. To things worth mentioning.
Code:
$ sudo do-release-upgrade Checking for a new ubuntu release No new release found
[code]....
I backed up my home folder just in case but didn't do a system backup. Wasn't worried if I broke it and had to reinstall, but this doesn't look in my (possibly incorrect) to bad.
Yesterday, while upgrading from Ubuntu 10.04 to 11.04, the computer crashed. For this reason, when I reboot, Ubuntu doesn't recognize any longer the root folder and so on... and halts execution in a blank screen (well before the login screen).I'm currently running LiveCD and I can see the Filesystem with the root folder, the bin folder, home folder and so on....My question is How can I access the files I had in my desktop from LiveCD? I know the user and password so how can I access it?
I don't understand why, but my Slackware is totally crash after ~10min work. My guess is Nvidia is fault. Which logs I could see where the problem is? X (startx) work fine. My video card is: geforce 240. installed slackware 13.37 64 bit.