Bug 198108 - systemsettings > Display, seg fault
Summary: systemsettings > Display, seg fault
Status: RESOLVED DUPLICATE of bug 192129
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_randr (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-28 03:09 UTC by Martin Rieger
Modified: 2009-08-08 14:21 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Rieger 2009-06-28 03:09:30 UTC
Version:            (using KDE 4.2.2)
OS:                Linux
Installed from:    Mandriva RPMs

System settings > double click display. (why double click? nothing else under similar situations requires double click)

System settings will always seg fault and not always report the crash, if it does, back trace is of no use.

nvidia-settings was used to configure the screens and disable dri has been commented out in xorg.conf due to parsing error it causes with nvidia-settings not allowing it to continue. DynamicTwinView is also enabled manually to allow nvidia-settings to configure the two screens.

Seems to be a configuration problem caused by the above settings. I have seen display working, but not with both screens operational.

No alteration to power saving settings are possible. Choosing an OpenGL screen saver can result in jerky behavior of the screen saver and eventual lock up.

Systemsettings > Desktop >Desktop Effects reports: "Compositing is not supported on your system.
Required X extensions (XComposite and XDamage) are not available." These are installed and available and Compiz can be enabled under Configure 3D Desktop effects.

Seems to be a problem two screens causing the disconnection. The two screens could possibly be beyond the range of the standard desktop. Screen 1 is 1920 x 1200 and screen 2 is 2560 x 1600. together the desktop is 4480 x 1600. If there is a 4096 limitation then this will exceed it. The Quadro 4500 can handle the resolution but the software may not.

Compiz is selectable and will start the system but no rendering effects. It is the same as normal but the system tries to implement the cube desktop space as all windows end up in desktop 1. Matisse is a disaster and can trash the user configuration so that you cannot log in with any graphical interface thereafter.

Computer is hp xw9300 with Opteron 275s and 8 GB RAM.
Comment 1 Martin Rieger 2009-06-28 03:56:17 UTC
Further the standard desktop has problems. A cursor always remains on a
screen, two screens, two cursors pointers. The cursor pointer (or whatever it
is) remains "parked" at the edge where it exited until the cursor position
returns to the screen then it will jump to the correct position.
Comment 2 Dario Andres 2009-06-28 16:04:40 UTC
Just a tip: for further bug reports try to use one report per issue (to avoid mixing different issues in the same report, even when they could be related)
The current report is about multiple things, crash on a configuration module, problems regarding compositing and window management (Kwin), hardware/driver issues, and the cursor one.

As for the crash: (which I'm going to take as the main subject of this report): you can install the "kdebase4-workspace-debuginfo" and "kdelibs5-debuginfo" packages in order to get an useful backtrace to paste here later.
Also, you may want to read: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

You can report the compositing/hardware/compiz thing in a new report against the "kwin" product.

Thanks!
Regards
Comment 3 Christoph Feck 2009-06-30 08:31:51 UTC
NVidia, KDE 4.2.2 -> probably a duplicate of bug 192129.

Please install KDE 4.2.4, the crash is fixed there.
Comment 4 Dhiraj Kumar Hazra 2009-06-30 08:39:23 UTC
yes ,I am using opensuse 11.1 kde 4.2.4 and having nvidia geforce 9200 .I am having no crash there.
Comment 5 Martin Rieger 2009-06-30 14:57:11 UTC
I added the additional information as I thought it relevant to the crash problem, didn't realise it was another one.

Mandriva appears not to have "kdebase4-workspace-debuginfo" or "kdelibs5-debuginfo" packages to install.

Dhiraj Kumar Hazra, what size is your desktop? Display will not crash with one screen configured with two and Xinerama mode my desktop is 4480 x 1600 and this causes problems. Prevents display from working at all. Most people will not have a desktop this big so will not experience the problem.

"Please install KDE 4.2.4, the crash is fixed there." Has someone tested this with a desktop bigger than 4480 x 1600?
Comment 6 Dhiraj Kumar Hazra 2009-06-30 15:53:43 UTC
(In reply to comment #5)

> 
> Dhiraj Kumar Hazra, what size is your desktop? Display will not crash with one
> screen configured with two and Xinerama mode my desktop is 4480 x 1600 and this
> causes problems. Prevents display from working at all. Most people will not
> have a desktop this big so will not experience the problem.


sorry I missed the size part.Mine is too small compared to that.:)
Comment 7 Martin Rieger 2009-07-04 04:18:57 UTC
"Please install KDE 4.2.4, the crash is fixed there." 

Installed as part of Mandriva updates to KDE 4.2.4, Display now is not crashing. Next thing not working is randr. Again this works with one monitor, xrandr 1.3 is installed.

Display claims your X server does not support resize and rotate with two screens.There should be four option to allow each monitor to be rotated.

Seems to be a whole range of problems with over sized and multiple monitor desktops.

Open GL screen savers present as still images at 15 second ish intervals and are unstable.

Compositing is not working either, although it appears it should.

Which bug should I post next?
Comment 8 Aaron J. Seigo 2009-07-04 06:50:40 UTC
those all sound like bugs in your x.org driver and/or hitting the limits of your hardware
Comment 9 Martin Rieger 2009-07-04 12:03:01 UTC
Not helping, "all sound like" is not good enough, what are the limitations? I need to know what is and are the limitations so I can work out what is wrong and get it fixed.

Not hardware limits, KDE 4 limits, maybe x.org driver limits. Displays are working, I suspect something is working even though reported to be not working, displays are fast and very little CPU usage. Quadro 4500 does not have a 4096 pixel desktop limitation. Everything worked well under KDE 3.5 although there were some limitations and similar compiz problems. Open GL worked, X didn't crash, and it was configurable. Most likely is hardware is beyond the scope of the software model.

No need for compiz, I do not like the desktop layout and prefer standard mode, even Matisse is a little odd in desktop behavior. Other functions I like.

I still like KDE 3.5 better than KDE 4.2 (KDE 4.1 was useless). Raw SPDIF output worked, Open GL worked. The old Konqueror is far better than the Dolphin of today,it's all the little things, like saving the layout, size view, file size in bytes, tool tips that show a video frame, in line file name editing that works, fast response, restoring with all tabs, file transfer pop up panel that shows more information and does not crash indicators, sub folder size in tool tip, and I can go on.

I know this is not the right place to put this up but is an indication that what was, is better than what currently is, and the evolution process was broken in the change from KDE3 to KDE4. Lots of breakages along the way.
Comment 10 Christoph Feck 2009-08-08 14:21:00 UTC
Reporter indicated upgrading did fix the crash, marking as resolved.

Martin, for the other regressions, please file bug reports or enhancement requests separately, if they are still valid for KDE 4.3. While we appreciate any reports, it is impossible for developers to track multiple bugs for multiple applications/components with a single bug number. Thanks for your understanding.

*** This bug has been marked as a duplicate of bug 192129 ***