Things That Won't Run in -Current (21 April 2015).
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
removepkg / installpkg steamclient-1.0.0.49-i386-1alien.tgz leads also to the X crash.
Really, while running the removepkg or installpkg command your X session crashes?
The removepkg command does nothing to your X environment, it just removes the files from your filesysten. Unless you still had the steamclient running when you removed the package - but even that should not crash X.
And installpkg will run a couple of commands that should never crash X, they do nothing to your OpenGL configuration, libraries and do not start the steamclient itself:
No, no, sorry for the unclear post. By removepkg / installpkg I meant that I remove and after that install again the steamclient package. And the next start of steam crashes X.
X crashes only when steam is being launched. I haven't experienced X crash in other cases with other applications.
Hi, sorry for my bad English. There were some issues after mass upgrade and I've fixed most of them but unfortunately i didn't manage to fix the most annoying one: i can't see polish characters in UTF8 anymore in Thunar, shell and in terminal emulator.
I'm using 64bit -current with multilib and XFCE as a window manager. The problem has occured after -current and before multilib upgrade.
Before upgrade it worked, now it does not. I can't see polish characters in Thunar, in shell and in XFCE terminal emulator. I can type and see them when typing in all sorts of GUI text editors, web browsers and so on but when typing in shell or terminal emulator they aren't visible. However they are visible in XFCE menu items, settings manager and so on. Things are better when I'm using ISO-8859-2 encoding in XFCE terminal or I'm switching from zsh to bash: I can see typed characters then but they still aren't visible when I'm listening directory or using midnight commander. Strange thing is that after setting up LOCALE to LANG=C (so obviously non-polish locale) I'm able to see polish characters in Thunar (but, of course, I can't type them anymore).
Another weird thing is that I can type and see correct characters in shell before logging in - in login prompt.
Hi, I often do some work by mobile computing when on the train between the office and home.
At work I have an extra monitor attached to my laptop and after disconnecting that and putting the whole shebang to sleep some java programs (LibreOffice, JalView) appear to hang upon resume in absence of this extra monitor. I do not know whether it has to do with XFCE since these crashes seem to occur after the recent upgrade to 4.12 (and is not resolved by the recent current-upgrades).
Has anyone else seen this kind of behaviour? It is really forcing me not to use suspend/resume as I tend to lose work that way.
The java error files show similar errors (if that means anything):
Code:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f5a085ddbf4, pid=1281, tid=140024677439296
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libpthread.so.0+0x9bf4] pthread_mutex_lock+0x4
#
Code:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fee299e7bf4, pid=8492, tid=140660890482496
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b14) (build 1.8.0_45-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libpthread.so.0+0x9bf4] pthread_mutex_lock+0x4
If you see a library like libfam.so.0 is not found, a good thing to do is less slackware64/MANIFEST.bz2 and search for the file to see if it's in a (possibly missing) package.
If you see a library like libfam.so.0 is not found, a good thing to do is less slackware64/MANIFEST.bz2 and search for the file to see if it's in a (possibly missing) package.
It will be hard to help you if we can't reproduce that issue.
For that, the first thing would be to run a genuine Slackware-current as it is supposed to be, i.e. with zero customization: using a genuine Slackware kernel and typing "startx" as a regular user, etc.
It will be hard to help you if we can't reproduce that issue.
For that, the first thing would be to run a genuine Slackware-current as it is supposed to be, i.e. with zero customization: using a genuine Slackware kernel and typing "startx" as a regular user, etc.
Give more information first.
Like: post a complete Xorg.0.log instead of just the errors. Like Didier said, try this with a stock Slackware-current without your own kernel or other additions. Are you using nouveau or Nvidia binaries? Did you install all the recent NEW packages that were added to Slackware-current?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,087
Original Poster
Rep:
Pipelight-plugins
For the first time since the massive upgrades of 21 April 2015, I've installed wine-pipelight and pipelight, but Firefox cannot find two out of the three plugins I enabled.
They are in the correct dictionary, /usr/lib64/mozilla/plugins and I copied them to ~/.mozilla/plugins/, but, again, Firefox only sees the abode reader plugin, but not the silverlight or widevine plugins.
A 'pipelight-plugin --system-check' shows the system failed the libraries test for both 32 and 64-bit, as "libodbc.so" is missing, but everything else passed.
Solved.
Edit in: OK, found the answer in Alien Bob's troubling shooting tips
for wine-pipelight, and that was to delete the pluginreg.dat file.
Give more information first.
Like: post a complete Xorg.0.log instead of just the errors. Like Didier said, try this with a stock Slackware-current without your own kernel or other additions. Are you using nouveau or Nvidia binaries? Did you install all the recent NEW packages that were added to Slackware-current?
Ok, I found the problem.
I run a vncserver in background, and run xfce in it. the device file /dev/dri/card0 is opened by xfwm4 in vnc
When vnc/xfce4 is running, I can not start X-server in console.
After vnc stopped, then everything is fine, even I start two X-server in different console, they are all running ok.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.