[Bug 120940] Re: emacs-snapshot-gtk stopped working
luh
freakyveit at web.de
Tue Sep 4 14:36:18 BST 2007
I can reproduce the bug. When I start emacs with my usual settings.
("use my kde-style in my gtk applications") it crashes with these
messages:
vnh at fedora:~$ emacs &
[1] 7000
vnh at fedora:~$ X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 167
Major opcode: 144
Minor opcode: 3
Resource id: 0x0
Failed to open device
emacs: symbol lookup error: /usr/lib/gtk-2.0/2.10.0/engines/libqtengine.so: undefined symbol: setColors
If I change my settings to: "use another style: raleigh"
it works just fine. If i switch back, the problem is there again.
--
emacs-snapshot-gtk stopped working
https://bugs.launchpad.net/bugs/120940
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for Feisty Backports.
More information about the ubuntu-backports
mailing list