[Lucid Netbook Alpha 3] env crashed with SIGSEGV in setlocale()

Bug #527447 reported by Paolo Sammicheli
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
coreutils (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Binary package hint: coreutils

While Testing Netbook Edition Alpha3

MD5Sum : 6fd2abc1a8a263f66ff0ff9099743572
/cdimage/ubuntu-netbook/daily-live/20100224.3/lucid-netbook-i386.iso

I was just clicking on the menu.

Hardware: Laptop Dell Inspiron 1520, Graphic card: nVidia Corporation G84 [GeForce 8600M GT]

ProblemType: Crash
Architecture: i386
Date: Wed Feb 24 22:57:12 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/env
LiveMediaBuild: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100224.3)
Package: coreutils 7.4-2ubuntu1
ProcCmdline: /usr/bin/env python /usr/lib/cups/backend/hpfax
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x74d657: mov (%edx),%edx
 PC (0x0074d657) ok
 source "(%edx)" (0xffffffff) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: coreutils
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 setlocale () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: env crashed with SIGSEGV in setlocale()
Uname: Linux 2.6.32-14-generic i686
UserGroups:

Revision history for this message
Paolo Sammicheli (xdatap1) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _nl_intern_locale_data (category=0, data=0xffffffff,
 _nl_load_locale (file=0x9621b30,
 _nl_find_locale (locale_path=<value optimized out>,
 *__GI_setlocale (category=0, locale=0x804dc56 "")
 main (argc=3, argv=0xbf8a34d4) at env.c:141

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in coreutils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
tags: added: iso-testing
Revision history for this message
Anzenketh (anzenketh) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

When reporting bugs in the future please use apport, either via the appropriate application's "Help -> Report a Problem" menu or using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in coreutils (Ubuntu):
status: New → Incomplete
Revision history for this message
Paolo Sammicheli (xdatap1) wrote :

1. the specific steps or actions you took that caused you to encounter the problem,

During Alpha3 Testing, Case ID: nls-001 (http://testcases.qa.ubuntu.com/Install/UNR-Live)

2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).

A component crashed and apport detected this crash. All configuration files and traces were attached to this bug, what do you need more? We are talking about a live session so there isn't any user data.

Hardware configuration, as reported above is a Laptop Dell Inspiron 1520, Graphic card: nVidia Corporation G84 [GeForce 8600M GT]

Changed in coreutils (Ubuntu):
status: Incomplete → New
Anzenketh (anzenketh)
tags: added: hw-specifc
Revision history for this message
Anzenketh (anzenketh) wrote :

Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in coreutils (Ubuntu):
status: New → Incomplete
Revision history for this message
C de-Avillez (hggdh2) wrote :

No, this is not easily reproducible. I am still trying to find a common ground here (there are other similar bugs opened).

Revision history for this message
Paolo Sammicheli (xdatap1) wrote :

I can confirm what Carlos said. There's no way to reproduce it because it's not related with the user activity.

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.