LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 01-10-2013, 04:59 AM   #1
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,290

Rep: Reputation: 50
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 05:01 AM.
 
Old 01-11-2013, 02:00 AM   #2
STDOUBT
Member
 
Registered: May 2010
Location: Stumptown
Distribution: Slackware 14.0/32bit + Xmonad
Posts: 283

Rep: Reputation: 76
"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.
Old 01-11-2013, 02:28 AM   #3
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,290

Original Poster
Rep: Reputation: 50
Thanks. About CUPS, /etc/rc.d/rc.cups is not executable. About bluetooth, I have to investigate. Thanks again, STDOUBT.
 
Old 01-13-2013, 08:23 AM   #4
mudangel
Member
 
Registered: May 2008
Location: Ohio
Distribution: Slackware
Posts: 267

Rep: Reputation: 48
Code:
warning: No hp: or hpfax: devices found in any installed CUPS queue. Exiting.
Maybe hplip is trying to find a CUPS printer?
 
Old 01-13-2013, 08:48 AM   #5
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,290

Original Poster
Rep: Reputation: 50
Quote:
Originally Posted by mudangel View Post
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?
 
Old 01-13-2013, 08:56 AM   #6
Snark1994
Senior Member
 
Registered: Sep 2010
Location: Wales, UK
Distribution: Arch
Posts: 1,632
Blog Entries: 3

Rep: Reputation: 345Reputation: 345Reputation: 345Reputation: 345
Quote:
Originally Posted by stf92 View Post
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.
 
Old 01-13-2013, 09:32 AM   #7
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 3,290

Original Poster
Rep: Reputation: 50
Of course I did. When getting back from another console the buffer is lost.
 
Old 01-13-2013, 04:46 PM   #8
mudangel
Member
 
Registered: May 2008
Location: Ohio
Distribution: Slackware
Posts: 267

Rep: Reputation: 48
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 04:47 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



All times are GMT -5. The time now is 02:50 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration