minitube crashed with SIGSEGV in value()

Bug #966622 reported by lipstick
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
minitube (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: minitube 1.6-1
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
NonfreeKernelModules: wl
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Wed Mar 28 00:06:44 2012
ExecutablePath: /usr/bin/minitube
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120128)
ProcCmdline: minitube
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: minitube
Title: minitube crashed with SIGSEGV in QNetworkReply::header()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin netdev plugdev sambashare sudo

Revision history for this message
lipstick (sinanaykut-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 value (akey=<synthetic pointer>, this=0x9622c60) at ../../include/QtCore/../../src/corelib/tools/qhash.h:609
 QNetworkReply::header (this=0x0, header=QNetworkRequest::LocationHeader) at access/qnetworkreply.cpp:502
 ?? ()
 ?? ()
 metacall (argv=0xbfbb2c50, idx=17, cl=QMetaObject::InvokeMetaMethod, object=0x9664fb0) at kernel/qmetaobject.cpp:245

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 minitube (Ubuntu):
importance: Undecided → Medium
summary: - minitube crashed with SIGSEGV in QNetworkReply::header()
+ minitube crashed with SIGSEGV in value()
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in minitube (Ubuntu):
status: New → Confirmed
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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