SegFault in libgdk-3

Bug #1392367 reported by Rui Lapa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LightDM GTK Greeter
New
Unknown

Bug Description

I'm using Trusty XFCE with lightdm-gtk-greeter 201411130631~ubuntu14.04.1 on 470x Asus VivoPC i5 (intel graphic).

Using "201411130631" because I need conky to help Helpdesk diagnose network info.
On trusty's version 1.8.5-1ubuntu2, conky steals focus.

Its been randomly normal users locking sessions and when they "wake up" they get a black screen.

The issue seams to be this segfault.

Nov 13 11:17:20 VP0329 kernel: [ 8128.980526] lightdm-gtk-gre[8780]: segfault at 18 ip 00007f0efd547ca0 sp 00007fffe4f1a488 error 4 in libgdk-3.so.0.1000.8[7f0efd50f000+a0000]
Nov 13 09:04:37 VP0329 console-kit-daemon[1785]: GLib-CRITICAL: Source ID 11 was not found when attempting to remove it
Nov 13 11:17:20 VP0329 console-kit-daemon[1785]: GLib-CRITICAL: Source ID 36 was not found when attempting to remove it

Issue is not easily reproducible.

If there's a way to get network indicator I would gladly be back on "stable".

Tags: trusty
Revision history for this message
Simon Steinbeiß (ochosi) wrote :

Obviously you can't have a network indicator in the greeter because the network settings are *within* the session and the greeter sits outside of it. (Unless you have a single-user system with global network settings, then it would make sense to show it.)

So you're diagnosing network information on the greeter/lock screen..?

Anyway, that segfault we'll have to look into I guess.

Revision history for this message
Rui Lapa (rui-lapa) wrote : Re: [Bug 1392367] Re: SegFault in libgdk-3

Yes, normally, network indicator is used inside the session.
We need the Ethernet IP address so that "field support" can check basic
network connection, initial checkup/provision and remote authentication.

A basic IP info would be enough, but I could not find a way to use a
network indicator, nor make one.
Even a red/green led based on /sys/class/net/eth0/operstate would do it.
Have any ideas to share another way of getting same info without conky
would be appreciated.

On Wed, Nov 19, 2014 at 1:30 PM, Simon Steinbeiß <email address hidden>
wrote:

> Obviously you can't have a network indicator in the greeter because the
> network settings are *within* the session and the greeter sits outside
> of it. (Unless you have a single-user system with global network
> settings, then it would make sense to show it.)
>
> So you're diagnosing network information on the greeter/lock screen..?
>
> Anyway, that segfault we'll have to look into I guess.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1392367
>
> Title:
> SegFault in libgdk-3
>
> Status in LightDM GTK+ Greeter:
> New
>
> Bug description:
> I'm using Trusty XFCE with lightdm-gtk-greeter
> 201411130631~ubuntu14.04.1 on 470x Asus VivoPC i5 (intel graphic).
>
> Using "201411130631" because I need conky to help Helpdesk diagnose
> network info.
> On trusty's version 1.8.5-1ubuntu2, conky steals focus.
>
> Its been randomly normal users locking sessions and when they "wake
> up" they get a black screen.
>
> The issue seams to be this segfault.
>
> Nov 13 11:17:20 VP0329 kernel: [ 8128.980526] lightdm-gtk-gre[8780]:
> segfault at 18 ip 00007f0efd547ca0 sp 00007fffe4f1a488 error 4 in
> libgdk-3.so.0.1000.8[7f0efd50f000+a0000]
> Nov 13 09:04:37 VP0329 console-kit-daemon[1785]: GLib-CRITICAL: Source
> ID 11 was not found when attempting to remove it
> Nov 13 11:17:20 VP0329 console-kit-daemon[1785]: GLib-CRITICAL: Source
> ID 36 was not found when attempting to remove it
>
> Issue is not easily reproducible.
>
> If there's a way to get network indicator I would gladly be back on
> "stable".
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1392367/+subscriptions
>

Sean Davis (bluesabre)
Changed in lightdm-gtk-greeter:
importance: Undecided → Unknown
status: New → Unknown
Changed in lightdm-gtk-greeter:
status: Unknown → New
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.