*** This bug is a duplicate of bug 91545 ***
https://bugs.launchpad.net/bugs/91545
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/7237032/CoreDump.gz
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately
*** This bug is a duplicate of bug 91545 ***
https://bugs.launchpad.net/bugs/91545
** This bug has been marked a duplicate of bug 91545
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
--
After enableing second monitor guidance crashes on every startup
Uh, oops, forgot to mention that while the screen works as expected
with the virtual statement addition, the display control still
crashes,, prolly broke something during all the fumbling in the dark,
sigh!
--
After enableing second monitor guidance crashes on every startup and graphical
I may have a workaround.
Try modifying /etc/X11/xorg.conf thusly:
Add virtual x_dim y_dim to SubSection Display in Section
screen
Match x_dim, y_dim to your screen size.
man xorg.conf tells you that without the virtual statement, the virtual
screen size is set to the maximum available under
This looks like duplicate of bug 91545.
I have prepared test packages (i386 only) with fix from KDE SVN. You can
install and test them:
http://muse.19inch.net/~lure/feisty/kde-guidance_0.8.0-0ubuntu6~lure1_i386.deb
I found this thread searching for info on crashes I experience with every kde
start (powermanager) or whenever I try to open the displayconfig control. It
behaves just like Laur Motus described it.
This is kubuntu 7.04 on a ASUS A8N-SLI-Premium Bios Rev 1009 with an ASUS
EN7600GT grasphic card
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/7237032/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/7237033/Dependencies.txt
** Attachment added: Disassembly.txt
http://librarian.launchpad.net/7237034/Disassembly.txt
** Attachment
Computer is HP's laptop nx6125
using open ati driver
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
https://bugs.launchpad.net/bugs/105125
You received this bug notification because you are a member of Ubuntu
Can you run displayconfig from the commandline and post the output?
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
https://bugs.launchpad.net/bugs/105125
You received this bug notification because you are a
KCrash: Application 'displayconfig' crashing...
attached is the backtrace, but i didn't find the debugging package for
that in the repos
** Attachment added: backtrace
http://librarian.launchpad.net/7237276/out.txt
--
After enableing second monitor guidance crashes on every startup and
Is this really the commandline output from displayconfig? I'm especially
interested in a python backtrace, everything else is essentially
useless.
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
Yes, it really is that short.
Where could i find the bebugging package?
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
https://bugs.launchpad.net/bugs/105125
You received this bug notification because you are a
There is no debugging package.
So it crashes without a trace? I cannot do anything about this, I'm
afraid.
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
https://bugs.launchpad.net/bugs/105125
You received
Could someone make the debugging package?
Is this
http://librarian.launchpad.net/7237276/out.txt
backtrace useless?
And is python backtrace somewhat different?
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when
There is no 'debugging mode' for guidance, so I suppose it's not easily
possible to create something like a debugging package.
Your backtrace is useless, yes. I'd expect a python backtrace showing up
on the commandline.
By the way, does running kcmshell displayconfig show something in the
[EMAIL PROTECTED]:~$ kcmshell displayconfig
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
Not useful, I'm afraid. :/
** Changed in: kde-guidance (Ubuntu)
Status: Unconfirmed = Needs Info
--
After enableing second monitor guidance crashes on every startup and graphical
display manager crashes immidiately when launched
https://bugs.launchpad.net/bugs/105125
You received this
17 matches
Mail list logo
