gksu crashed with SIGSEGV in gdk_window_set_opacity()

Bug #482923 reported by Linda
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gksu (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: gksu

I don't have any idea what to say here.

ProblemType: Crash
Architecture: i386
Date: Sat Nov 14 09:47:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gksu
NonfreeKernelModules: nvidia
Package: gksu 2.0.2-2ubuntu1
ProcCmdline: /usr/bin/gksu --message <span\ weight="bold"\ size="larger">Please\ enter\ your\ password\ to\ access\ problem\ reports\ of\ system\ programs</span> /usr/share/apport/apport-gtk
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SegvAnalysis:
 Segfault happened at: 0x1738ac <gdk_window_set_opacity+44>: mov (%esi),%edx
 PC (0x001738ac) ok
 source "(%esi)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
 gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/libgksu2.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_window_set_opacity()
Uname: Linux 2.6.31-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Linda (bossnking) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__gdk_window_set_opacity (window=0x30, opacity=0.5)
fadeout_callback (fadeout=0x9d84448) at libgksu.c:322
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in gksu (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Linda (bossnking) wrote : Re: [Bug 482923] [NEW] gksu crashed with SIGSEGV in gdk_window_set_opacity()

what is this????????????
----- Original Message -----
From: "Linda" <email address hidden>
To: <email address hidden>
Sent: Saturday, November 14, 2009 9:28:41 PM GMT -06:00 US/Canada Central
Subject: [Bug 482923] [NEW] gksu crashed with SIGSEGV in gdk_window_set_opacity()

Private bug reported:

Binary package hint: gksu

I don't have any idea what to say here.

ProblemType: Crash
Architecture: i386
Date: Sat Nov 14 09:47:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gksu
NonfreeKernelModules: nvidia
Package: gksu 2.0.2-2ubuntu1
ProcCmdline: /usr/bin/gksu --message <span\ weight="bold"\ size="larger">Please\ enter\ your\ password\ to\ access\ problem\ reports\ of\ system\ programs</span> /usr/share/apport/apport-gtk
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SegvAnalysis:
Segfault happened at: 0x1738ac <gdk_window_set_opacity+44>: mov (%esi),%edx
PC (0x001738ac) ok
source "(%esi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0
?? () from /usr/lib/libgksu2.so.0
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_window_set_opacity()
Uname: Linux 2.6.31-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: gksu (Ubuntu)
Importance: Undecided
Status: New

** Tags: apport-crash i386 need-i386-retrace

--
gksu crashed with SIGSEGV in gdk_window_set_opacity()
https://bugs.launchpad.net/bugs/482923
You received this bug notification because you are a direct subscriber
of the bug.

Status in “gksu” package in Ubuntu: New

Bug description:
Binary package hint: gksu

I don't have any idea what to say here.

ProblemType: Crash
Architecture: i386
Date: Sat Nov 14 09:47:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gksu
NonfreeKernelModules: nvidia
Package: gksu 2.0.2-2ubuntu1
ProcCmdline: /usr/bin/gksu --message <span\ weight="bold"\ size="larger">Please\ enter\ your\ password\ to\ access\ problem\ reports\ of\ system\ programs</span> /usr/share/apport/apport-gtk
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SegvAnalysis:
Segfault happened at: 0x1738ac <gdk_window_set_opacity+44>: mov (%esi),%edx
PC (0x001738ac) ok
source "(%esi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gksu
StacktraceTop:
gdk_window_set_opacity () from /usr/lib/libgdk-x11-2.0.so.0
?? () from /usr/lib/libgksu2.so.0
?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0
Title: gksu crashed with SIGSEGV in gdk_window_set_opacity()
Uname: Linux 2.6.31-15-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

@Linda:
When you file a bug report, you normally receive email concerning any changes to that report. You do not have to answer that email, unless a specific question is asked in it. Sometimes we ask for more information, because there is not enough information to resolve the issue.

When the report is initially filed, the description box that is empty, that you typed in "I don't have any idea what to say here." is an area where you can tell us exactly what you were doing when the crash or failure happened. sometimes knowing what the user is doing is very helpful to resolving the issue.

visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 182629, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in gksu (Ubuntu):
status: New → Confirmed
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.