[Desktop-packages] [Bug 1050358] Re: emesene crashed with SIGSEGV in tupledealloc.24592()

2012-12-07 Thread Tiago Neiva
this bug is being tracked here:
https://github.com/emesene/emesene/issues/1537

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358

Title:
  emesene crashed with SIGSEGV in tupledealloc.24592()

Status in “emesene” package in Ubuntu:
  Confirmed
Status in “pygobject” package in Ubuntu:
  Confirmed
Status in “pygobject-2” package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my msn account emesene crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: emesene 2.12.5+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 13 13:12:08 2012
  ExecutablePath: /usr/share/emesene/emesene/emesene
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/emesene -s
  SegvAnalysis:
   Segfault happened at: 0x4b6058:  mov0x98(%r13),%eax
   PC (0x004b6058) ok
   source "0x98(%r13)" (0x0098) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: emesene
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1021410] Re: Gnome-System-Log fails to launch when started from the dash

2012-10-24 Thread Tiago Neiva
*** This bug is a duplicate of bug 957641 ***
https://bugs.launchpad.net/bugs/957641

I found this in debian bug reports:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690337

it may be of interest

** Bug watch added: Debian Bug tracker #690337
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690337

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1021410

Title:
  Gnome-System-Log fails to launch when started from the dash

Status in “gnome-system-log” package in Ubuntu:
  Confirmed
Status in “policykit-1” package in Ubuntu:
  Confirmed

Bug description:
  Gnome-System-Log fails to launch when started from the dash. Checking
  the .desktop file reveals it's launching with pkexec. I don't believe
  escalated privileges are needed to view logs, so I would argue to
  change the .desktop file to remove this.

  Executing 'pkexec gnome-system-log' from the command line works
  properly. Launching it via the dash fails silently. This appears to
  affect any application that launches via pkexec, which is potentially
  a larger bug.

  NOTE: gparted appears to work-around the pkexec issue by running a
  wrapper script instead of pkexec gparted directly. See below.

  --
  #!/bin/sh
  pkexec "/usr/sbin/gparted" "$@"
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-system-log 3.4.1-1
  ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
  Uname: Linux 3.5.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.2.5-0ubuntu2
  Architecture: amd64
  Date: Thu Jul  5 13:44:03 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-system-log
  UpgradeStatus: Upgraded to quantal on 2012-06-08 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1021410/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1067649] Re: Cannot access gnome-system-log from unity

2012-10-24 Thread Tiago Neiva
*** This bug is a duplicate of bug 957641 ***
https://bugs.launchpad.net/bugs/957641

** This bug is no longer a duplicate of bug 1021410
   Gnome-System-Log fails to launch when started from the dash
** This bug has been marked a duplicate of bug 957641
   unity does not display authentication window for pkexec

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1067649

Title:
  Cannot access gnome-system-log from unity

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I have problems with accessing gnome-system-log from Unity:

  1) searching in the home lens or application lens for "log", or even
  "gnome-system-log" does not bring the item. Searching in my language
  works ("journeaux"). I think searching on the program name should
  work.

  2) once I get the item, left clicking on it does nothing. Right
  clicking gives the preview, but in the preview, the launch button does
  nothing.

  3) notice that typing "gnome-system-log" in a terminal works
  perfectly, and gives no error, nor warning in the console

  I have purge / reinstalled gnome-system-log, but the problem
  persists

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CheckboxSubmission: cba860c6453f7c09f91c40eab660deed
  CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Wed Oct 17 10:27:38 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-09-14 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1067649/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 957641] Re: unity does not display authentication window for pkexec

2012-10-24 Thread Tiago Neiva
I found this in debian bug reports:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690337

it may be of interest


** Bug watch added: Debian Bug tracker #690337
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690337

** Changed in: unity (Ubuntu)
   Status: Invalid => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/957641

Title:
  unity does not display authentication window for pkexec

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  The /usr/share/applications/gnome-system-log.desktop file recently
  changed to have "EXEC=pkexec gnome-system-log", and now it is not
  possible to run it from the unity launcher icon or from the 'matching
  applications' list in the dash (note that it matches 'log file viewer'
  and not 'gnome-system-log'). No error is displayed anywhere that I can
  see (eg in ~.xsession-errors).

  Running 'pkexec gnome-system-log' from gnome-terminal prompts the user
  for authentication to get sudo privileges, so it appears likely that
  either unity tries to run the command and it fails, or runs it but
  doesn't display the authentication window.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.6.0-0ubuntu4
  Uname: Linux 3.3.0-rc7-git-20120316.1313 x86_64
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,decor,mousepoll,gnomecompat,imgpng,snap,grid,wall,move,place,vpswitch,session,compiztoolbox,extrawm,resize,regex,animation,workarounds,unitymtgrabhandles,expo,fade,scale,ezoom,unityshell]
  Date: Sat Mar 17 10:27:11 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: Upgraded to precise on 2012-03-13 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/957641/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1021410] Re: Gnome-System-Log fails to launch when started from the dash

2012-10-24 Thread Tiago Neiva
*** This bug is a duplicate of bug 957641 ***
https://bugs.launchpad.net/bugs/957641

This was described in
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/957641


** This bug has been marked a duplicate of bug 957641
   unity does not display authentication window for pkexec

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/1021410

Title:
  Gnome-System-Log fails to launch when started from the dash

Status in “gnome-system-log” package in Ubuntu:
  Confirmed
Status in “policykit-1” package in Ubuntu:
  Confirmed

Bug description:
  Gnome-System-Log fails to launch when started from the dash. Checking
  the .desktop file reveals it's launching with pkexec. I don't believe
  escalated privileges are needed to view logs, so I would argue to
  change the .desktop file to remove this.

  Executing 'pkexec gnome-system-log' from the command line works
  properly. Launching it via the dash fails silently. This appears to
  affect any application that launches via pkexec, which is potentially
  a larger bug.

  NOTE: gparted appears to work-around the pkexec issue by running a
  wrapper script instead of pkexec gparted directly. See below.

  --
  #!/bin/sh
  pkexec "/usr/sbin/gparted" "$@"
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-system-log 3.4.1-1
  ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5
  Uname: Linux 3.5.0-3-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.2.5-0ubuntu2
  Architecture: amd64
  Date: Thu Jul  5 13:44:03 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: gnome-system-log
  UpgradeStatus: Upgraded to quantal on 2012-06-08 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1021410/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1041674] Re: gnome-system-log fails to run from dash or launcher

2012-10-24 Thread Tiago Neiva
*** This bug is a duplicate of bug 957641 ***
https://bugs.launchpad.net/bugs/957641

** This bug is no longer a duplicate of bug 1021410
   Gnome-System-Log fails to launch when started from the dash
** This bug has been marked a duplicate of bug 957641
   unity does not display authentication window for pkexec

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1041674

Title:
  gnome-system-log fails to run from dash or launcher

Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  gnome-system-log runs fine from the command line in Quantal, but
  nothing happens if you click on the gnome-system-log icon in the
  launcher or in the dash.

  The desktop file has 'Exec=pkexec gnome-system-log', and removing
  pkexec makes it run again from dash/launcher. (However, gparted has a
  similar line, and in its case pkexec correctly asks for
  authentication.)

  But should gnome-system-log even need sudo privileges? I seem to
  recall a similar problem with gnome-system-log happening in Precise
  until pkexec was removed from the command line.

  ubuntu 12.10
  gnome-system-log 3.5.90-0ubuntu2
  unity 6.2.0-0ubuntu3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1041674/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1050358] Dependencies.txt

2012-10-22 Thread Tiago Neiva
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1050358/+attachment/3409450/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358

Title:
  emesene crashed with SIGSEGV in tupledealloc.24592()

Status in “emesene” package in Ubuntu:
  Confirmed
Status in “pygobject” package in Ubuntu:
  Confirmed
Status in “pygobject-2” package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my msn account emesene crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: emesene 2.12.5+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 13 13:12:08 2012
  ExecutablePath: /usr/share/emesene/emesene/emesene
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/emesene -s
  SegvAnalysis:
   Segfault happened at: 0x4b6058:  mov0x98(%r13),%eax
   PC (0x004b6058) ok
   source "0x98(%r13)" (0x0098) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: emesene
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1050358] ProcEnviron.txt

2012-10-22 Thread Tiago Neiva
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1050358/+attachment/3409451/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358

Title:
  emesene crashed with SIGSEGV in tupledealloc.24592()

Status in “emesene” package in Ubuntu:
  Confirmed
Status in “pygobject” package in Ubuntu:
  Confirmed
Status in “pygobject-2” package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my msn account emesene crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: emesene 2.12.5+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 13 13:12:08 2012
  ExecutablePath: /usr/share/emesene/emesene/emesene
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/emesene -s
  SegvAnalysis:
   Segfault happened at: 0x4b6058:  mov0x98(%r13),%eax
   PC (0x004b6058) ok
   source "0x98(%r13)" (0x0098) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: emesene
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1050358] Re: emesene crashed with SIGSEGV in tupledealloc.24592()

2012-10-22 Thread Tiago Neiva
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
Package: pygobject-2
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Tags:  quantal running-unity
Uname: Linux 3.5.0-17-generic i686
UpgradeStatus: Upgraded to quantal on 2012-10-20 (2 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo


** Tags added: apport-collected

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358

Title:
  emesene crashed with SIGSEGV in tupledealloc.24592()

Status in “emesene” package in Ubuntu:
  Confirmed
Status in “pygobject” package in Ubuntu:
  Confirmed
Status in “pygobject-2” package in Ubuntu:
  Confirmed

Bug description:
  When I try to connect to my msn account emesene crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: emesene 2.12.5+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 13 13:12:08 2012
  ExecutablePath: /usr/share/emesene/emesene/emesene
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/emesene -s
  SegvAnalysis:
   Segfault happened at: 0x4b6058:  mov0x98(%r13),%eax
   PC (0x004b6058) ok
   source "0x98(%r13)" (0x0098) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: emesene
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 696281] Re: Log File viewer shows incorrect day of week

2011-10-15 Thread Tiago Neiva
come new year eve's I'll report back

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-utils in Ubuntu.
https://bugs.launchpad.net/bugs/696281

Title:
  Log File viewer shows incorrect day of week

Status in “gnome-utils” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: gnome-utils

  This is a strange bug, not an important one.
  Today I was trying to find something in the logs and got confused when the 
entry was "Sunday, 1 Jan".
  As shown in the attachment older entries have wrong weekdays.
  This behaviour also happens on another computer which has 10.10 installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-utils 2.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11
  Uname: Linux 2.6.32-26-generic x86_64
  NonfreeKernelModules: fglrx
  Architecture: amd64
  Date: Sat Jan  1 17:07:01 2011
  ExecutablePath: /usr/bin/gnome-system-log
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/696281/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp