Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
09-18-2013, 11:28 PM
|
#1
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Rep: 
|
Possible bug with today's glibc updates?
Hi all,
I've spent a few hours chasing this down to no avail.
I upgraded the glibc packages noted in today's changelog for Slackware 64_14 using slackpkg. After that, XFCE did not have a window manager.
The warning messages that I can see after exiting back to the console (I boot to runlevel 3) indicate some problem with glibc, but I know I'm not seeing all the messages.
I rolled back the changes to glibc by reinstalling those packages from the Slackware DVD. I also reinstalled XFCE 4, and I moved the ~/.config/xfce folder into another directory so XFCE would start with a brand new configuration.
Still no window manager.
Is anyone else having this issue?
Thanks,
|
|
|
09-18-2013, 11:36 PM
|
#2
|
Member
Registered: Sep 2012
Location: Bulgaria,Varna
Distribution: Slackware64
Posts: 249
Rep: 
|
This is not a problem with glibc.Try to open terminal and type
|
|
|
09-19-2013, 12:47 PM
|
#3
|
LQ Veteran
Registered: Jan 2011
Location: Abingdon, VA
Distribution: Catalina
Posts: 9,374
Rep: 
|
Did you reboot after rolling back the glibc installs?
|
|
|
09-19-2013, 03:28 PM
|
#4
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Original Poster
Rep: 
|
Hi folks and thanks for the responses.
I did reboot after the glibc updates and rollbacks.
I will try the xfwm4 --replace & command this evening after work.
Regards,
-Drew
|
|
|
09-19-2013, 06:57 PM
|
#5
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Original Poster
Rep: 
|
Quote:
Originally Posted by tuxbg
This is not a problem with glibc.Try to open terminal and type
|
Okay, that worked. Thanks!
Why did it work?
-Drew
|
|
|
09-19-2013, 07:33 PM
|
#6
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Original Poster
Rep: 
|
Update: it only works on the current session, and I can't log out. :-/
Here are the messages on the console (what I can capture anyway):
Code:
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Sep 19 20:27:38 2013
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
resize called 1024 768
/usr/bin/startxfce4: X server already running on display :0
HP Linux Imaging and Printing System (ver. 3.12.9)
System Tray Status Service ver. 2.0
Copyright (c) 2001-14 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Usage: hp-systray [MODE] [OPTIONS]
[MODE]
Run in graphical UI mode: -u or --gui (Default)
[OPTIONS]
Use Qt4: --qt4 (Default)
Set the logging level: -l<level> or --logging=<level>
<level>: none, info*, error, warn, debug (*default)
Run in debug mode: -g (same as option: -ldebug)
This help information: -h or --help
Startup even if no hplip CUPS queues are -x or --force-startup
present:
error: option -s not recognized
(xfdesktop:2865): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfdesktop:2865): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed
(xfce4-session:2845): Wnck-CRITICAL **: wnck_workspace_activate: assertion `WNCK_IS_WORKSPACE (space)' failed
HP Linux Imaging and Printing System (ver. 3.12.9)
System Tray Status Service ver. 2.0
Copyright (c) 2001-14 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
** (nm-applet:2896): CRITICAL **: dbus_set_g_error: assertion `gerror == NULL || *gerror == NULL' failed
/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK
set_interactive(1)
QGtkStyle was unable to detect the current GTK+ theme.
xfce4-panel: No window manager registered on screen 0. To start the panel without this check, run with --disable-wm-check.
xfsettingsd: No window manager registered on screen 0.
(xfsettingsd:2864): xfsettingsd-WARNING **: Failed to get the _NET_NUMBER_OF_DESKTOPS property.
Any thoughts?
Thanks,
|
|
|
09-19-2013, 08:15 PM
|
#7
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Quote:
QGtkStyle was unable to detect the current GTK+ theme.
|
Check your GTK+ 2.x and GTK+ 3.x packages.
|
|
|
09-21-2013, 01:31 PM
|
#8
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Original Poster
Rep: 
|
Hmm. I did that too. No effect.
I'm sort of stumped.
|
|
|
10-08-2013, 09:01 PM
|
#9
|
Senior Member
Registered: Aug 2006
Location: Harrisburg, PA
Distribution: Slackware 64 14.2
Posts: 1,180
Original Poster
Rep: 
|
This is solved now. The answer was clearing out the XFCE4-related directory and files in the .cache directory in my home folder.
I've reinstalled the glibc updates from late September and everything is fine.
Regards,
-Drew
|
|
|
All times are GMT -5. The time now is 04:16 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|