Announcement

Collapse
No announcement yet.

kicker problem after sept 5th system update

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    kicker problem after sept 5th system update

    after an apt-get update && upgrade on sept 5th that upgraded some kde packages, though i can't remember exactly what,

    my kicker doesn't work anymore.

    It doesn't start when i boot up the machine, although the rest of kde does. It shows up as a process, though with a '?' and crashes if i try to restart it manually, although it comes up for a couple of seconds.

    here's what i tried to do to get it restarted, i've also tried messing around with it in kcontrol, but nothing makes it come back up. this is a fairly new fiesty fawn install. any ideas? thanks, ryan

    Code:
    ryan@FIZZ:~/Desktop$ ps -e | grep kicker
     5595 ?    00:00:01 kicker
    ryan@FIZZ:~/Desktop$ kill -9 5595
    ryan@FIZZ:~/Desktop$ kicker &
    [1] 6298
    ryan@FIZZ:~/Desktop$ X Error: BadDevice, invalid or uninitialized input device 169
     Major opcode: 145
     Minor opcode: 3
     Resource id: 0x0
    Failed to open device
    X Error: BadDevice, invalid or uninitialized input device 169
     Major opcode: 145
     Minor opcode: 3
     Resource id: 0x0
    Failed to open device
    *** attempt to put segment in horiz list twice
    
    [1]+ Done          kicker

    #2
    Re: kicker problem after sept 5th system update

    A quick Google search for "+kicker attempt to put segment in horiz list twice" came up with this... Do you have any special add-ons?
    For external use only.

    Comment


      #3
      Re: kicker problem after sept 5th system update

      i deleted the ~/.kde*/kicker* files, went back to kcontrol and set panels to default, and then my kicker popped back up. i then set me options again and everything seems to be working.

      Thanks.

      Comment

      Working...
      X