Slackware :: CLI Apps Crash Over Ssh (and Locally)?
Dec 11, 2010
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.
After a fresh install of Ubuntu 10.10 (and all updates applied) any(?) KDE app causes Ubuntu to crash. (X restarts and the login screen is presented.)This happens immediately when opening kolourpaint, after clicking add file in krename, and after clicking "ok" to set up krusader for the first time.
Qt apps like vlc, kolourpaint, qbittorrent are missing the windows controls like menus. Smplayer crash on opening a video(any format). I'm using mate with marco wm, I also tried openbox but is the same.
I was wondering what is happening to my computer. It runs perfectly fine, until out of nowhere my CPU load goes up to 100% for no reason, and in the System Monitor, the process that I think is responsible is the "uninterruptible process". It's so far been chrome, firefox-bin, and now gnome-netstatus-applet.
Is this a hardware problem or buggy software? Because I honestly don't know what it is. I've even reinstalled the programs and rebooted several times, most of the reboots were because of my computer crashing every time!
I'm running Debian Lenny with GNOME on a ThinkPad T43. Some OpenGL apps like the game Trigger run great, while others like Stellarium crash my system beyond recovery. I get a black screen, I can see the mouse cursor and move it at a very slow speed, but nothing else. I can't switch to a different terminal or restart X with ctrl-alt-bksp.
I assume that the problematic apps do not like the laptop's integrated graphics chip? Is there a way to know ahead of time what apps might be troublesome, before actually running them? I hate hard resets.
I've installed wmii as window manager (slackware 13.1) locally, i.e. not system wide. I use a german keyboard and this works fine until I start my window manager. within wmii the german layout is not present (neither in xterm nor in emacs or ooo3 etc). I changed the file /etc/X11/xorg-conf already accordingly but without any effect. Hence I suspect that the local installation of the wmii requires a change of another config-file?!
I'm interested in seeing what others are doing w.r.t. fonts in a standard Slack install. The 2 main apps I use are Firefox and Thunderbird and both look fairly poor out of the box. Previously I've used a combination of gtk-qt-engine and gnome-appearance-properties ( with a gsb install ) but this doesn't always do the 'right thing'.
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 installed Slackware64 13.1 two days ago for the first time ever on my Dell Inspiron 1525 after using linux for about a year (Debian and Fedora, though I've installed a few others in VMs). I've really enjoyed Slackware so far, it's been comparatively trouble free. However, I decided to follow AlienBOB's instructions to make it multilib, and though I thought I'd done everything right - I can't seem to compile any 32-bit 13.1 slackbuilds; I've tried with sbopkg as well as the normal method, but it simply won't work. I must have done something wrong, but I've re-read the instructions on getting mutilib working several times and I can't work out what it is.
KDE 3.5.4Kernel 2.6.17.13Slack 11A few weeks ago, my system locked up and I had to do a hard reboot (hold down power button). When I powered back on, the programs (KDE System Guard, Konsole window, MythFrontEnd) that were running at the time of the lockup appeared again. I exited System Guard and the Konsole window and then restarted normally. However, they keep appearing in the same spot when I log in to KDE. I looked through some logs in /var/log, but I don't see anything I haven't seen before.I deleted the /home/myuser/.kde/cache-hostname folder and its contents while in single-user mode, but that had no impact
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
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.
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:
I installed Slackware 12.1 as I dont like KDE4 much yet. Any way For Some reason I find I can only use the internet by using apps with root privileges. Does anyone know what I may need to edit by any chance & what.?
I like working with light text on black bg in Fluxbox however I need to use Kate editor which has bright white background and dark text. How can I change the background to black?(and the side panel of file list, too)? I presume I need to change the kde theme under Fluxbox. Does anyone know where the config file is and what to change in there if it's not obvious?
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.
Is there any Slackware-current or Slackware64-current users in the LQ Slackware forum experiencing lags or slowdown on Dolphin file manager on KDE 4.5.1? I experienced this first on KDE 4.5.0, after the current update KDE to 4.5.1 I still have this problem.
Hovering mouse on a file can take a while, opening a text file with kwrite took several seconds and dolphin window will appear blank (like hang). Sometimes Dolphin crashed when opening file, changing directory or hovering mouse on a file.
Quick googling points to this discussion at http://dot.kde.org/2010/08/31/kde-releases-451 which suggest a bug in libdbus.
Until the latest update to php, claws-mail was running fine. Since updating php through slackpkg, Claws will start but as soon as a message is selected it crashes with the following message (caught in terminal)
root[/]# claws-mail Newmail plugin loaded Message header summaries written to /home/pat/Mail/NewLog Segmentation fault root[/]#
When I open a gtk app from the command line this error pops up:
Code:
Gtk: Unable to locate theme engine in module_path: "clearlooks", and I can not find clearlooks theme engine anywhere as it is supposed to be part of gtk by default?
Adobe Reader 9.3.3 on Slackware 13.1 (32 bit). This is the stand-alone reader, not the browser plugin. The Reader crashes the second time I open the print dialog. Even if I cancel, and do not actually print. For example: Open a PDF, File=>Print, Cancel, File=>Print. Then the Reader window is gone, with no message anywhere I can find.
Well, that's about it - the firefox and thunderbird packages included on the first batch of official 13.1 updates keep crashing when I try to print a web page or an e-mail. Seamonkey, updated as well, can print as usual.
I'm having a problem building some applications (e.g. Qsynth and FreeCAD) with sbopkg relating to an unfound library named "jscore". I've been keeping my system up to date with slackware64-current.Google searches have turned up very little about this library. There is a sourceforge page that has no files and seems to be related to a google hosted script jsCore.js... but I don't think that's what's missing here. I've come across some vague references to this jscore library being part of webkit. Can anyone verify this? I updated my webkit library itself and found no apparent results. Perhaps jscore was removed in an update to Qt (both of the example applications mentioned above link to Qt) as it seems to have it's own webkit library, libQtWebKit.
I have been using slackware for a few years now and just made a jump from 12.1 to 13.0 recently on my Dell Inspiron 6400 laptop. Everything seems to be working great except for the video players. When I try to start xine I get the following error:
X Error of failed request: BadAlloc (insufficient resources for operation) Major opcode of failed request: 135 (XVideo) Minor opcode of failed request: 19 () Serial number of failed request: 1977
I'm running Slackware current. After the recent glibc change, ImageMagick display is exhibiting bad behaviour. I open an image with display, left-click on it to get the menus, move the mouse down so I can click on Transform, but before I get there, it crashes and displays this message code... Has anyone else seen this? Is there a fix for it?
I switched today to slackware-current on one of my desktops to play with it and ran directly into a problem.
Since ages my lilo.conf has two entries for slackware. One for runlevel 3 and one for runlevel 4.
Code:
Since the upgrade this is no more possible because I get a kernel panic as soon as udevadm trigger is called. The stack says something about an unknown boot option. Because that i removed the append lines from my lilo.conf and i was able to boot the system. The crash happens when udev is called from within the ramdisk and afterwards. I tried both.
My question is now. Is this a bug in udev or expected? I have this setup since at least 5 years and had never problems with that. What do I have to do to be able to select the runlevel at boot time?
Some minimized apps no longer appear in the top menu and by that are no longer accessible.For example firefox with the minimize addon or Jungel Disk backup service.How can I reach apps that minimized them self and are not shown in the top menu?
