Ubuntu
ubuntu-drivers-common package

gpu-manager crashed with SIGSEGV in _IO_vfprintf_internal()

Bug #1298693 reported by Kai Li
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-drivers-common (Ubuntu)
Fix Released
Medium
Alberto Milone
Trusty
Triaged
Medium
Alberto Milone

Bug Description

after installed nvidia-331,
 I'm try to use nvidia-switch in terminal, got a segment fault

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: ubuntu-drivers-common 1:0.2.91.1
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: KDE
Date: Thu Mar 27 23:49:44 2014
ExecutablePath: /usr/bin/gpu-manager
InstallationDate: Installed on 2014-03-18 (9 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140318)
ProcCmdline: /usr/bin/gpu-manager --log /var/log/gpu-manager.log
SegvAnalysis:
 Segfault happened at: 0x7fef36a38fcd <_IO_vfprintf_internal+45>: mov 0xc0(%rdi),%eax
 PC (0x7fef36a38fcd) ok
 source "0xc0(%rdi)" (0x000000c0) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: ubuntu-drivers-common
StacktraceTop:
 _IO_vfprintf_internal (s=0x0, format=0x4099b3 "log_file: %s\n", ap=ap@entry=0x7fff6fb6e928) at vfprintf.c:1295
 __fprintf (stream=<optimized out>, format=<optimized out>) at fprintf.c:32
 ?? ()
 __libc_start_main (main=0x40627e, argc=3, argv=0x7fff6fb6ec38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6fb6ec28) at libc-start.c:287
 ?? ()
Title: gpu-manager crashed with SIGSEGV in _IO_vfprintf_internal()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Kai Li (kai-li-jx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _IO_vfprintf_internal (s=0x0, format=0x4099b3 "log_file: %s\n", ap=ap@entry=0x7fff6fb6e928) at vfprintf.c:1295
 __fprintf (stream=<optimized out>, format=<optimized out>) at fprintf.c:32
 main (argc=3, argv=0x7fff6fb6ec38) at gpu-manager.c:2438

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in ubuntu-drivers-common (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Martin Pitt (pitti) wrote :

Looks like https://errors.ubuntu.com/problem/ca9e6b07dce04478d80f88a2ef3ae94b9def6bd1

information type: Private → Public
Revision history for this message
Martin Pitt (pitti) wrote :

It's crashing here, FTR:

    if (log_file)
        fprintf(log_handle, "log_file: %s\n", log_file);

Changed in ubuntu-drivers-common (Ubuntu):
status: New → Confirmed
Revision history for this message
Alberto Milone (albertomilone) wrote :

I've just managed to reproduce the error. It happens when gpu-manager tries to write to a log it doesn't have write access to. I'm surprised there's no check for that.

Changed in ubuntu-drivers-common (Ubuntu):
assignee: nobody → Alberto Milone (albertomilone)
status: Confirmed → In Progress
Alberto Milone (albertomilone)
Changed in ubuntu-drivers-common (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Alberto Milone (albertomilone)
Alberto Milone (albertomilone)
Changed in ubuntu-drivers-common (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-drivers-common - 1:0.4.10

---------------
ubuntu-drivers-common (1:0.4.10) wily; urgency=medium

  * debian/tests/system: Drop the nvidia package tests; they are now tested
    through autodep8 on every kernel and dkms change, so we don't have to rely
    on this hard to maintain autopkgtest any more. Also drop most other driver
    package tests for the same reason; just keep the "fglrx" test to get a
    full end-to-end test with "ubuntu-drivers".

 -- Martin Pitt <email address hidden> Thu, 03 Sep 2015 11:27:33 +0200

Changed in ubuntu-drivers-common (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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