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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
01-10-2013, 03:59 AM
|
#1
|
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 2,487
Rep:
|
Exception: Failed to initialize killswitch manager (GUI).
OS: Slackware 14.0
Hi:
Code:
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.
warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Using file config backend
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/blueman/plugins/BasePlugin.py", line
65, in _load
self.on_load(parent)
File "/usr/lib64/python2.7/site-packages/blueman/plugins/applet/KillSwitch.py", line 52, in on_load
raise Exception("Failed to initialize killswitch manager")
Exception: Failed to initialize killswitch manager
Using file config backend
Using file config backend
Using file config backend
Deleting plugin instance <blueman.plugins.applet.KillSwitch.KillSwitch object at 0x29be810>
This is output produced by the GUI immediately upon entering it. CUPS I do not have it started at boot, so its a don't care. What I do care is the "killswitch manager" message. In the GUI exit menu, Switch User is disabled. Honestly, I do not even know where to start with fixing this problem. Any suggestion would be welcome.
Last edited by stf92; 01-10-2013 at 04:01 AM.
|
|
|
|
01-11-2013, 01:00 AM
|
#2
|
|
Member
Registered: May 2010
Location: Stumptown
Distribution: Slackware 13.37~14.0~xmonad
Posts: 129
Rep:
|
"killswitch manager" and Switch User in the logout menu are not related.
"blueman" is the bluetooth manager. Have a look at your devices. If your machine is equipped with a bluetooth device, make sure it's activated in BIOS. If it's not activated, and you want to keep it disabled, use your GUI (I assume KDE) to turn off the KDE bluetooth service.
To make the CUPS error go away, you might want to make sure the /etc/rc.d/rc.cups file is not executable.
|
|
|
1 members found this post helpful.
|
01-11-2013, 01:28 AM
|
#3
|
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 2,487
Original Poster
Rep:
|
Thanks. About CUPS, /etc/rc.d/rc.cups is not executable. About bluetooth, I have to investigate. Thanks again, STDOUBT.
|
|
|
|
01-13-2013, 07:23 AM
|
#4
|
|
Member
Registered: May 2008
Location: Ohio
Distribution: Slackware
Posts: 267
Rep:
|
Code:
warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Maybe hplip is trying to find a CUPS printer?
|
|
|
|
01-13-2013, 07:48 AM
|
#5
|
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 2,487
Original Poster
Rep:
|
Quote:
Originally Posted by mudangel
Code:
warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Maybe hplip is trying to find a CUPS printer?
|
I do not know. If I could get rid of only one of the error messages output by programs run in the GUI at startup, I could see further up in the F6 console, the console from where I start X. For the X messages, I have /var/log/Xorg.0.log. How do I know if lip is being run?
|
|
|
|
01-13-2013, 07:56 AM
|
#6
|
|
Senior Member
Registered: Sep 2010
Location: Wales, UK
Distribution: Arch
Posts: 1,624
|
Quote:
Originally Posted by stf92
I do not know. If I could get rid of only one of the error messages output by programs run in the GUI at startup, I could see further up in the F6 console, the console from where I start X.
|
Have you tried pressing Shift+Page Up? That normally scrolls the terminal upwards.
|
|
|
|
01-13-2013, 08:32 AM
|
#7
|
|
Senior Member
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 2,487
Original Poster
Rep:
|
Of course I did. When getting back from another console the buffer is lost.
|
|
|
|
01-13-2013, 03:46 PM
|
#8
|
|
Member
Registered: May 2008
Location: Ohio
Distribution: Slackware
Posts: 267
Rep:
|
Code:
startx > startx.log 2>&1
This will give you a file containing the output of startx
Last edited by mudangel; 01-13-2013 at 03:47 PM.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 12:58 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
|
|