I have just checked the current package and both fixes are included in
current version: 0.8.0svn20070928-0ubuntu5
Marking as Fix released. Please open new bug if you still experience
similar problem with up-to-date gutsy.
** Changed in: kde-guidance (Ubuntu)
Status: Fix Committed = Fix
So, when the fix will be released ?
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Thanks for all you help.
xD.
2007/7/20, Petr Škoda (skodak) [EMAIL PROTECTED]:
hello,
the packages above fixed the problem for me in Feisty. (the problem
appeared originally when I started using 2 screen configuration - each
different size/nvidia).
the problem is still present in Gutsy
hello,
the packages above fixed the problem for me in Feisty. (the problem appeared
originally when I started using 2 screen configuration - each different
size/nvidia).
the problem is still present in Gutsy though. I managed to force downgrade to
these packages above and it sort of works
This happens to me too. Using the latest and greatest Gutsy at the
moment (don't know if this happened in Feisty for me since it's X was
too unstable for some weird reason so I quickly changed to Gutsy).
I'm using xinerama too with my Radeon 7500. On konsole the kcmshell
displayconfig crashes
Why is it marked fix committed when the duplicates are coming in all the
time ? This ain't fixed!
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
I appologise for my earlier comment.
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team, which is a bug assignee.
--
kubuntu-bugs mailing list
** Attachment removed: CoreDump.gz
http://launchpadlibrarian.net/6734138/CoreDump.gz
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team,
I have the same problem as in the original bug report, and I also can't launch
kcmshell displayconfig because it segfaults when I try to launch it. The stack
trace is attached.
Are the patched packages available for amd64 yet or are they available in
source form?
Thanks!
** Attachment added:
Can we have packages for 64bit systems please?
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team, which is a bug assignee.
--
kubuntu-bugs
I just committed a fix for that AttributeError about screenconfig.
(KDE SVN revision 661336)
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team,
Display module will not open from system settings or from kcmshell
displayconfig on the command line.
Rich
On 5/4/07, Luka Renko [EMAIL PROTECTED] wrote:
Mantan: can you run kcmshell displayconfig from command line and
attach output? Did it work before? I suspect this is different bug as it
Attached file is the output from running kcmshell displayconfig at the
command prompt.
On 5/4/07, Luka Renko [EMAIL PROTECTED] wrote:
Mantan: can you run kcmshell displayconfig from command line and
attach output? Did it work before? I suspect this is different bug as it
runs properly here.
I applied the patches and no longer have the power manager crash.
However, I can no longer change the display settings in kcmshell Here is
the output:
Pythonize constructor -- pid = 9796
Python interpreter initialized!
Pythonize constructor -- pid = 9796
Traceback (most recent call last):
I have prepared test packages (i386 only) with above 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
http://muse.19inch.net/~lure/feisty/kde-guidance-powermanager_0.8.0-0ubuntu6~lure1_i386.deb
Please report back if
I can only test on a dual head rig with AMD64. Will test that when one
is available.
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team, which
All is good on my 2 machines. Thanks for your efforts.
On 5/3/07, Luka Renko [EMAIL PROTECTED] wrote:
I have prepared test packages (i386 only) with above 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 tried the kde-guidance packasge it doesn't crash, but it won't
load the display module.
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team,
Mantan: can you run kcmshell displayconfig from command line and
attach output? Did it work before? I suspect this is different bug as it
runs properly here.
Rich S.: thanks for testing! Can you try Display module in system
settings to see if you have same problem as Mantan with new package?
--
Hi !
sorry for my bad english.
I can't open displayconfig too and I have this error message when KDE
start :
message d'erreur au démarrage de kde = l'application power management
(guidance-power-manager.py) s'est terminé anormalement et a provoqué un signal
11
(error message for kde
I reported a similar error, that was marked as a duplicate of this one.
But I didn't mention in my original report that I was running a dual screen
configuration.
Mine uses a dual-head Matrox G400 PCI board.
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
I just committed a fix in KDE's SVN for this. (rev 660160, on
trunk/extragear/utils/guidance)
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
https://bugs.launchpad.net/bugs/91545
You received this bug notification because you are a member of Kubuntu
Team,
I just committed a fix in KDE's SVN for this. (rev 660160, on
trunk/extragear/utils/guidance)
** Changed in: kde-guidance (Ubuntu)
Status: Confirmed = Fix Committed
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
Looking at all of these crash reports I'm getting the feeling that the
problem has to do with guidance not handling things when the xrandr X
extension is not available. In the past, calling XRRGetScreenInfo()
would just return null if the extensions was not available, maybe this
behaviour has been
** Summary changed:
- [apport] displayconfig-restore.py crashed with SIGSEGV in XRRGetScreenInfo()
+ MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
--
MASTER [apport] displayconfig-restore.py crashed with SIGSEGV in
XRRGetScreenInfo()
25 matches
Mail list logo
