[SRU] kscreen 0.0.92

Bug #1177333 reported by Rohan Garg
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kscreen
Fix Released
High
kscreen (Ubuntu)
Fix Released
Undecided
Unassigned
Raring
Fix Released
Undecided
Unassigned
Saucy
Fix Released
Undecided
Unassigned
libkscreen (Ubuntu)
Fix Released
Undecided
Unassigned
Raring
Fix Released
Undecided
Unassigned
Saucy
Fix Released
Undecided
Unassigned

Bug Description

Upstream has requested kscreen be updated to 0.0.92 as it contains fixes for some critical bugs.

[Impact]
* Trying to login into KDE on computers with nVidia cards crashes the kded module

[Test Case]
* Plugin second monitor
* After updating to the package, logout and login into KDE
* The kded should not crash

Revision history for this message
In , gp (gpebug) wrote :

After update from kubuntu 12.10 to 13.04 kdeinit4 crashes on every start when when plasma appears.
On 12.10 I was using kde 4.10.2 from the backports.

Reproducible: Always

Steps to Reproduce:
1. Update to kubuntu 13.04
2. Reboot

Actual Results:
kdeinit4 crashes.

Expected Results:
kdeinit4 wont crash

I was not able to use the crash reporting assistant as I was not able to login.
(Failed to communicate with kded. Make sure it is running.)
Qt: 4.8.4
KDE Development Platform: 4.10.2
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
DISTRIB_CODENAME=raring
DISTRIB_DESCRIPTION="Ubuntu 13.04"

Revision history for this message
In , gp (gpebug) wrote :

Created attachment 79455
Crash report

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

Reassigning to kscreen developers, because of the crash KScreen::Output::id.

There is, however, some wiredness going on with "kded_colord.so", most certainly using synchronous D-Bus calls.

I thought we were pretty clear that synchronous D-Bus call are a no-go in a kded module. Adding colord maintainer.

Revision history for this message
In , Dvratil (dvratil) wrote :

Are you running a laptop, or a workstation? Could you please provide output from "kscreen-console bug" ?

Revision history for this message
In , gp (gpebug) wrote :

Created attachment 79465
Output of kscreen-console bug

I am running laptop with nvidia driver (304.88). Please find the kscreen-console bug output attached.

Revision history for this message
In , Dvratil (dvratil) wrote :

Git commit ffe2de800c74b4a927f194568511c813f9c5ffc7 by Dan Vrátil.
Committed on 26/04/2013 at 18:54.
Pushed by dvratil into branch 'master'.

Fix crash when embeddedOutput() fails to detect embedded output

Some laptops (probably older models) use 'VGA-*' to identify embedded
outputs, so embeddedOutput() will fail, because it only looks for
modern 'LVDS', 'EDP', etc. In such case, just try to use the output
with lowest ID. It's highly probably that it will be the right one.

We should also try to come up with some really reliable method, instead
of name-based guessing.
FIXED-IN: 1.0

M +11 -2 kded/generator.cpp

http://commits.kde.org/kscreen/ffe2de800c74b4a927f194568511c813f9c5ffc7

Revision history for this message
In , Cliff Ingham (inghamn) wrote :
Download full text (10.5 KiB)

Waking the computer up from idle causes a segfault. The screensaver is just set to show a blank screen. This is on a dual-monitor setup, using NVidia driver.

Application: KDE Daemon (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdf85ee17c0 (LWP 5181))]

Thread 5 (Thread 0x7fdf5b654700 (LWP 5197)):
#0 0x00007fdf8374bb0d in read () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007fdf7423716c in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#2 0x00007fdf73072b27 in ?? () from /usr/lib/nvidia-313-updates/tls/libnvidia-tls.so.313.30
#3 0x00007fdf808d36cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007fdf80894d3c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007fdf80895175 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007fdf808956ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x00007fdf5b9444f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8 0x00007fdf808b8eb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x00007fdf742381b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#10 0x00007fdf80f69f8e in start_thread (arg=0x7fdf5b654700) at pthread_create.c:311
#11 0x00007fdf83759e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7fdf5ac47700 (LWP 5198)):
#0 0x00007fdf8374bb0d in read () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007fdf7423716c in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#2 0x00007fdf73072b27 in ?? () from /usr/lib/nvidia-313-updates/tls/libnvidia-tls.so.313.30
#3 0x00007fdf808d36cf in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007fdf80894d3c in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007fdf80895175 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007fdf80895304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7 0x00007fdf84b7f036 in QEventDispatcherGlib::processEvents (this=0x7fdf400008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#8 0x00007fdf84b4f38f in QEventLoop::processEvents (this=this@entry=0x7fdf5ac46cc0, flags=...) at kernel/qeventloop.cpp:149
#9 0x00007fdf84b4f618 in QEventLoop::exec (this=this@entry=0x7fdf5ac46cc0, flags=...) at kernel/qeventloop.cpp:204
#10 0x00007fdf84a51410 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#11 0x00007fdf66aa46e5 in KCupsConnection::run() () from /usr/lib/libkcupslib.so
#12 0x00007fdf84a53bec in QThreadPrivate::start (arg=0x154de90) at thread/qthread_unix.cpp:338
#13 0x00007fdf742381b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#14 0x00007fdf80f69f8e in start_thread (arg=0x7fdf5ac47700) at pthread_create.c:311
#15 0x00007fdf83759e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fdf5a446700 (LWP 5199)):
#0 __lll_unlock_wake () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:371
#1 0x00007fdf80f6d119 in _L_unlock_571 () from /lib/x86_64-linux-gnu/libpthread.so.0
#2 0x00007fdf80f6d085 in __pthread_mutex_unlock_usercnt (mutex=0x7fdf74496e20, dec...

Revision history for this message
In , Christian Bayer (christian-bay) wrote :

Same here. Exact same stacktrace. This is really a bummer because without KDED, *NOTHING* works. Also a laptop setup with proprietary nvidia-driver, KDED runs fine until I dock the laptop (and thus add an external monitor).

Revision history for this message
In , Christian Bayer (christian-bay) wrote :

Created attachment 79471
KCrash report

Oh, and this also happened after update to Ubuntu 13.04.

Revision history for this message
In , Dvratil (dvratil) wrote :

*** Bug 319005 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

Can you provide the following feedback:

-execute kdebugdialog and enable "kded" and "KSRandr".
-Execute kded4 in a terminal (you will have to kill the previous kded)
-Reproduce the bug

Thanks !

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

You can disable the "KScreen 2" kded from systemsettings-->startup and shutdown -->Services

Will try to fix asap.

Revision history for this message
In , Christian Bayer (christian-bay) wrote :

@Alex Fiestas: Thank you, I'll try that, but I think this will work for me. Thanks!

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

Got the solution figured out, will implement and try to release tomorrow.

Thanks and sorry for the mess :(

Revision history for this message
In , Dvratil (dvratil) wrote :

*** Bug 319051 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Cliff Ingham (inghamn) wrote :
Download full text (6.9 KiB)

Here is the output from the terminal from starting kded4 up to the crash:

inghamn@aoi:~$ kded4
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "networkstatus"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "colord"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "dnssdwatcher"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "powerdevil"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "ktimezoned"
kded(4572)/KSRandr XRandRX11Helper::XRandRX11Helper: Detected XRandR 1.4
kded(4572)/KSRandr XRandRX11Helper::XRandRX11Helper: Event Base: 90
kded(4572)/KSRandr XRandRX11Helper::XRandRX11Helper: Event Error: 147
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "kscreen"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "statusnotifierwatcher"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "solidautoeject"
QDBusObjectPath: invalid path ""
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "obexftpdaemon"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "khotkeys"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "wacomtablet"
QDBusObjectPath: invalid path "/modules/muon-notifier"
kded(4572): The kded module name ' "muon-notifier" ' is invalid!
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "muon-notifier"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "printmanager"
QDBusConnection for control created "/Mixers/PulseAudio__Playback_Devices_1/alsa_output_pci_0000_00_1b_0_analog_stereo"
QDBusConnection for control created "/Mixers/PulseAudio__Capture_Devices_1/alsa_input_pci_0000_00_1b_0_analog_stereo"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "kmixd"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "notificationhelper"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "kwrited"
QObject::connect: Cannot connect (null)::deviceFound(Device*) to BlueDevilDaemon::deviceFound(Device*)
QObject::connect: Cannot connect QTimer::timeout() to (null)::stopDiscovery()
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "bluedevil"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "freespacenotifier"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "keyboard"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "device_automounter"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "remotedirnotify"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "nepomuksearchmodule"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "appmenu"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "networkmanagement"
kded(4572)/kded4 Kded::loadModule: Successfully loaded module "ktouchpadenabler"
inghamn@aoi:~$ Traceback (most recent call l...

Read more...

Revision history for this message
In , Cliff Ingham (inghamn) wrote :
Download full text (9.1 KiB)

Here's the backtrace from the segfault that occurred while running the terminal above:

Application: KDE Daemon (kded4), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8b443ef7c0 (LWP 4572))]

Thread 5 (Thread 0x7f8b251be700 (LWP 4575)):
#0 0x00007f8b3f1e235c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f8b3f1e25b9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f8b3f1a32f0 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f8b41b8c036 in QEventDispatcherGlib::processEvents (this=0x7f8b200008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4 0x00007f8b41b5c38f in QEventLoop::processEvents (this=this@entry=0x7f8b251bdcd0, flags=...) at kernel/qeventloop.cpp:149
#5 0x00007f8b41b5c618 in QEventLoop::exec (this=this@entry=0x7f8b251bdcd0, flags=...) at kernel/qeventloop.cpp:204
#6 0x00007f8b41a5e410 in QThread::exec (this=this@entry=0x24426a0) at thread/qthread.cpp:542
#7 0x00007f8b41b3dedf in QInotifyFileSystemWatcherEngine::run (this=0x24426a0) at io/qfilesystemwatcher_inotify.cpp:256
#8 0x00007f8b41a60bec in QThreadPrivate::start (arg=0x24426a0) at thread/qthread_unix.cpp:338
#9 0x00007f8b2b8411b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#10 0x00007f8b3f675f8e in start_thread (arg=0x7f8b251be700) at pthread_create.c:311
#11 0x00007f8b43d1de1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 4 (Thread 0x7f8b0d6b6700 (LWP 4582)):
#0 0x00007f8b3f67907f in __pthread_mutex_unlock_usercnt (mutex=0x258d010, decr=<optimized out>) at pthread_mutex_unlock.c:52
#1 0x00007f8b3f1e25f1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f8b3f1a31d1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f8b3f1a36ba in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f8b0d9a64f6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5 0x00007f8b3f1c6eb5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007f8b2b8411b4 in ?? () from /usr/lib/nvidia-313-updates/libGL.so.1
#7 0x00007f8b3f675f8e in start_thread (arg=0x7f8b0d6b6700) at pthread_create.c:311
#8 0x00007f8b43d1de1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7f8b0cca9700 (LWP 4583)):
#0 0x00007f8b3f1e2359 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007f8b3f1e25e9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007f8b3f1a28f3 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007f8b3f1a30fe in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007f8b3f1a3304 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007f8b41b8c036 in QEventDispatcherGlib::processEvents (this=0x7f8af00008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6 0x00007f8b41b5c38f in QEventLoop::processEvents (this=this@entry=0x7f8b0cca8cc0, flags=...) at kernel/qeventloop.cpp:149
#7 0x00007f8b41b5c618 in QEventLoop::exec (this=this@entry=0x7f8b0cca8cc0, flags=...) at kernel/qeventloop.cpp:204
#8 ...

Read more...

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

This is not a laptop machine isn't it?

can you provide the output of "kscreen-console bug" ?

thanks !

Revision history for this message
In , Dvratil (dvratil) wrote :

*** Bug 319108 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Cliff Ingham (inghamn) wrote :
Download full text (13.6 KiB)

No this is a desktop machine. A Dell Precision T1500 with a dual-head NVidia card.
The monitors are identical ViewSonic VA2226w

Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading configurations from ~/.fonts.conf is deprecated.
START
Config::current() took 206 milliseconds

========================xrandr --verbose==========================

Screen 0: minimum 8 x 8, current 3360 x 1050, maximum 8192 x 8192
DP-0 connected 1680x1050+1680+0 (0x249) normal (normal left inverted right x axis y axis) 495mm x 291mm
 Identifier: 0x248
 Timestamp: 29476
 Subpixel: unknown
 Gamma: 1.0:1.0:1.0
 Brightness: 1.0
 Clones:
 CRTC: 0
 CRTCs: 0 1
 Transform: 1.000000 0.000000 0.000000
             0.000000 1.000000 0.000000
             0.000000 0.000000 1.000000
            filter:
 EDID:
  00ffffffffffff005a63512001010101
  2a11010380311d782ee525a65444a125
  145054bfef80b300a94081808140714f
  01010101010121399030621a274068b0
  3600ef231100001c000000ff00515453
  3037343230313634350a000000fd0032
  4b1e5211000a202020202020000000fc
  00564132323236772d330a202020004c
 SignalFormat: TMDS
  supported: TMDS
 ConnectorType: DisplayPort
 ConnectorNumber: 0 (0x00000000)
 _ConnectorLocation: 0 (0x00000000)
  1680x1050 (0x249) 146.2MHz -HSync +VSync *current +preferred
        h: width 1680 start 1784 end 1960 total 2240 skew 0 clock 65.3KHz
        v: height 1050 start 1053 end 1059 total 1089 clock 60.0Hz
  1600x1200 (0x24a) 162.0MHz +HSync +VSync
        h: width 1600 start 1664 end 1856 total 2160 skew 0 clock 75.0KHz
        v: height 1200 start 1201 end 1204 total 1250 clock 60.0Hz
  1280x1024 (0x24b) 135.0MHz +HSync +VSync
        h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 80.0KHz
        v: height 1024 start 1025 end 1028 total 1066 clock 75.0Hz
  1280x1024 (0x24c) 108.0MHz +HSync +VSync
        h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 64.0KHz
        v: height 1024 start 1025 end 1028 total 1066 clock 60.0Hz
  1280x960 (0x24d) 108.0MHz +HSync +VSync
        h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.0KHz
        v: height 960 start 961 end 964 total 1000 clock 60.0Hz
  1152x864 (0x24e) 108.0MHz +HSync +VSync
        h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
        v: height 864 start 865 end 868 total 900 clock 75.0Hz
  1024x768 (0x24f) 78.8MHz +HSync +VSync
        h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.0KHz
        v: height 768 start 769 end 772 total 800 clock 75.0Hz
  1024x768 (0x250) 75.0MHz -HSync -VSync
        h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.5KHz
        v: height 768 start 771 end 777 total 806 clock 70.1Hz
  1024x768 (0x251) 65.0MHz -HSync -VSync
        h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
        v: height 768 start 771 end 777 total 806 clock 60.0Hz
  800x600 (0x252) 49.5MHz +HSync +VSync
        h: width 800 start 816 end 896 total 1056 skew ...

Revision history for this message
In , Cliff Ingham (inghamn) wrote :

Additional note, now that I understand a little more.

The segfault occurs when turning the monitors back on after they were switched off by the Energy Saving system.

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

*** Bug 319080 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

Forgot to close the bug, this has been fix in 0.0.92 (RC2)

Thanks for reporting !

Revision history for this message
In , gp (gpebug) wrote :

(In reply to comment #14)
> Forgot to close the bug, this has been fix in 0.0.92 (RC2)
>
> Thanks for reporting !

Thanks for fixing it :)

Revision history for this message
In , Dvratil (dvratil) wrote :

*** Bug 319191 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Dvratil (dvratil) wrote :

*** Bug 319358 has been marked as a duplicate of this bug. ***

Revision history for this message
In , mazugrin (mazugrin) wrote :

I noticed that the status is NEEDSINFO WAITINGFORINFO, but I wasn't able to find out what that status meant (it's not listed in the list of statuses that are described here: https://bugs.kde.org/page.cgi?id=fields.html#status).

But, if it means that any additional information is required for this bug to be actionable, I'd be happy to help. Does anyone know if that's what this status means?

Thanks!

Revision history for this message
In , Alex Fiestas (afiestas) wrote :

Sorry, the information was provided but we forgot to change the status.

This should be fixed with 0.0.92, is that so?

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

Alex, could you set the status correctly? We get several duplicates from 13.04.

Revision history for this message
In , Christoph-maxiom (christoph-maxiom) wrote :

*** Bug 319422 has been marked as a duplicate of this bug. ***

Rohan Garg (rohangarg)
Changed in kscreen (Ubuntu):
milestone: none → raring-updates
Changed in kscreen (Ubuntu Saucy):
milestone: raring-updates → none
Revision history for this message
Rohan Garg (rohangarg) wrote :

Uploaded to Saucy and Raring

description: updated
description: updated
Changed in kscreen:
importance: Unknown → High
status: Unknown → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kscreen - 0.0.92-0ubuntu1

---------------
kscreen (0.0.92-0ubuntu1) saucy; urgency=low

  * New upstream release (LP: #1177333)
    - Drop upstream_l10n.patch, included upstream
    - Bump libkscreen-dev Build Depend to 0.0.92
 -- Rohan Garg <email address hidden> Tue, 07 May 2013 00:17:04 +0100

Changed in kscreen (Ubuntu Saucy):
status: New → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote :

This is a fairly invasive set of changes. What testing on Kubuntu of these changes has been done?

Changed in libkscreen (Ubuntu Saucy):
status: New → Fix Released
Changed in kscreen (Ubuntu Raring):
status: New → Incomplete
Changed in libkscreen (Ubuntu Raring):
status: New → Incomplete
Revision history for this message
Alex Fiestas (afiestas) wrote :

The changes are not invasive at all.

Revision history for this message
Jonathan Riddell (jr) wrote :

Here's the testing programme the kscreen developers do:

connect a device
check settings are configured
change settings, unplug, plug in again, check settings remain
press hardware button and check it works and is saved
in system settings kcm make various changes and ensure they are applied correctly

I'll do this now with this update with my computer (intel) and with an nvidia computer

Revision history for this message
Jonathan Riddell (jr) wrote :

works good here on intel graphics

Revision history for this message
In , Rohan Garg (rohangarg) wrote :

Hi
As part of the SRU process in Ubuntu we require testing of our packages before the package is released into Ubuntu.

The kscreen packages to be tested can be found here https://launchpad.net/~kubuntu-ppa/+archive/experimental

The SRU bug can be found here : https://bugs.launchpad.net/ubuntu/+source/kscreen/+bug/1177333

Revision history for this message
In , Rohan Garg (rohangarg) wrote :

Steps to add the PPA on raring:

sudo add-apt-repository ppa:kubuntu-ppa/experimental
sudo apt-get update
sudo apt-get install kscreen

Once done, please logout and login, and check if plasma still crashes.

Rohan Garg (rohangarg)
description: updated
Revision history for this message
In , Kde-stratic (kde-stratic) wrote :

@Rohan: There is no more crash at startup with the experimental package. But kscreen did not works anymore with it...

In the system settings, the display configuration panel reports the following error:

   "No supported X Window system extension found"

kscreen-console reports the following:

START
kscreen-console(9742) BackendLoader::init: No KScreen backend set!
Config::current() took 0 milliseconds
Config is invalid, probably backend couldn't load

Revision history for this message
In , Rohan Garg (rohangarg) wrote :

@stratic
Could you paste the output of the command : apt-cache policy libkscreen0 kscreen

Revision history for this message
In , Rohan Garg (rohangarg) wrote :

I believe this is caused by having a older libkscreen0 , so please update libkscreen0 as well and then check if it still causes the issue.

Revision history for this message
In , Kde-stratic (kde-stratic) wrote :

@Rohan

 libkscreen0 was not updated automatically after a simple : "sudo apt-get install kscreen".

Now, after an explicit libkscreen0 update request, kscreen works properly.

Thank's you

Revision history for this message
In , Rohan Garg (rohangarg) wrote :

Ack. Minor packaging issue, will be uploading a fixed package to Ubuntu shortly :)

Revision history for this message
In , Jonathan Riddell (jr) wrote :

stratic: can you also sudo apt-get install libkscreen0 and test again?

Revision history for this message
In , Jonathan Riddell (jr) wrote :

Ignore my last comment, I see you've done it already thanks :)

Revision history for this message
Jonathan Riddell (jr) wrote :

comment from https://bugs.kde.org/show_bug.cgi?id=318907
@Rohan: There is no more crash at startup with the experimental package.

Revision history for this message
Jonathan Riddell (jr) wrote :

Most of the diff is the .po files changing from a patch to in the tar

Rohan's new update also adds symbols to libkscreen0 so kscreen depends on the correct version of libkscreen0

Rohan Garg (rohangarg)
Changed in kscreen:
importance: High → Unknown
status: Incomplete → Unknown
Changed in kscreen:
importance: Unknown → High
status: Unknown → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote : Please test proposed package

Hello Rohan, or anyone else affected,

Accepted into raring-proposed. The package will build now and be available in a few hours in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in kscreen (Ubuntu Raring):
status: Incomplete → Fix Committed
Changed in libkscreen (Ubuntu Raring):
status: Incomplete → Fix Committed
tags: added: verification-needed
Revision history for this message
spettmeis (spettmeis) wrote :

I've tested this in 13.04, by enabling -proposed and doing an update. Since then I have not had any crashes, so the problem seems to be solved.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libkscreen - 0.0.92-0ubuntu0.1

---------------
libkscreen (0.0.92-0ubuntu0.1) raring; urgency=low

  * No change backport (LP: #1177333)
 -- Rohan Garg <email address hidden> Wed, 08 May 2013 16:48:10 +0100

Changed in libkscreen (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
Scott Kitterman (kitterman) wrote : Update Released

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kscreen - 0.0.92-0ubuntu0.2

---------------
kscreen (0.0.92-0ubuntu0.2) raring; urgency=low

  * Fix Build-Depend on libkscreen-dev

kscreen (0.0.92-0ubuntu0.1) raring; urgency=low

  * No change backport (LP: #1177333)
 -- Rohan Garg <email address hidden> Fri, 10 May 2013 15:30:52 +0100

Changed in kscreen (Ubuntu Raring):
status: Fix Committed → Fix Released
Revision history for this message
David Newman (drdrnewman) wrote :

Not fixed. I am running kscreen 0.0.92-0ubuntu0.2 and I get multiple segfaults per day on a single monitor nvidia system (see all the bug reports on bugs.kde.org). Every time I switch off the monitor, then switch it on later, I get a kded crash "error 4 in libkscreen.so.0.0.92"

Revision history for this message
menthurae (menthurae) wrote :
Download full text (6.3 KiB)

Thank you to all the guys that responded to this very quickly.

I just want to say that I am also experiencing the same issue - my monitor is connected via DisplayPort. It's a Dell U3011 - connecting to an NVidia GeForce GTX680.

When I turn it off via the power button, and then switch it back on. I must switch to a different TTY (CTRL+ALT+F#) and then back to TTY7 (CTRL+ALT+F7) - whereupon I am greeted by a bug/crash handler window saying kdeinit4 has crashed.

For information, here is some data on my setup. If you want any more info or logs or anything, just ask please! =)

---------------------
menthurae@raptor:~$ apt-cache policy libkscreen0 kscreen

libkscreen0:
  Installed: 0.0.92-0ubuntu1~ppa1
  Candidate: 0.0.92-0ubuntu1~ppa1
  Version table:
 *** 0.0.92-0ubuntu1~ppa1 0
        500 http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status
     0.0.92-0ubuntu0.1 0
        500 http://ftp.iinet.net.au/pub/ubuntu/ raring-updates/universe amd64 Packages
     0.0.81-0ubuntu2 0
        500 http://ftp.iinet.net.au/pub/ubuntu/ raring/universe amd64 Packages
kscreen:
  Installed: 0.0.92-0ubuntu1~ppa2
  Candidate: 0.0.92-0ubuntu1~ppa2
  Version table:
 *** 0.0.92-0ubuntu1~ppa2 0
        500 http://ppa.launchpad.net/kubuntu-ppa/experimental/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status
     0.0.92-0ubuntu0.2 0
        500 http://ftp.iinet.net.au/pub/ubuntu/ raring-updates/universe amd64 Packages
     0.0.81-0ubuntu2 0
        500 http://ftp.iinet.net.au/pub/ubuntu/ raring/universe amd64 Packages

---------------------
menthurae@raptor:~$ apt-cache policy nvidia-313-updates

nvidia-313-updates:
  Installed: 313.30-0ubuntu1
  Candidate: 313.30-0ubuntu1
  Version table:
 *** 313.30-0ubuntu1 0
        500 http://ftp.iinet.net.au/pub/ubuntu/ raring/restricted amd64 Packages
        100 /var/lib/dpkg/status

---------------------

// Not sure if the output from the command below is helpful or not...!

menthurae@raptor:~$ cat /var/log/* | grep kdeinit4

cat: /var/log/apt: Is a directory
Jun 23 20:09:58 raptor dbus[833]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.5" (uid=110 pid=1075 comm="/usr/lib/colord/colord ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.19" (uid=1000 pid=2215 comm="kdeinit4: kded4 [kdeinit] ")
Jun 23 20:32:24 raptor dbus[833]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.5" (uid=110 pid=1075 comm="/usr/lib/colord/colord ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.90" (uid=1000 pid=4495 comm="kdeinit4: kded4 [kdeinit]")
Jun 24 06:22:30 raptor dbus[833]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.5" (uid=110 pid=1075 comm="/usr/lib/colord/colord ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.109" (uid=1000 pid=4956 comm="kdeinit4: kded4 [kdeinit]")
Jun 24 17:19:08 raptor dbus[841]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.5" (uid...

Read more...

Revision history for this message
menthurae (menthurae) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.