nvidia drivers on ubuntu 13.04 causes skype to crash

Bug #1163384 reported by graingert
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Nvidia
New
Undecided
Unassigned
nvidia-graphics-drivers-313-updates (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

See the discussion here: https://jira.skype.com/browse/SCL-970

$ valgrind `which skype`
==25354== Memcheck, a memory error detector
==25354== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==25354== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==25354== Command: /usr/bin/skype
==25354==
vex x86->IR: unhandled instruction bytes: 0xF1 0xE 0x2B 0x2B
==25354== Invalid read of size 1
==25354== at 0x8075F40: ??? (in /usr/bin/skype)
==25354== by 0x7F44118: ??? (in /usr/lib32/nvidia-313-updates/libGL.so.313.26)
==25354== Address 0xd is not stack'd, malloc'd or (recently) free'd
==25354==
==25354==
==25354== Process terminating with default action of signal 11 (SIGSEGV)
==25354== Access not within mapped region at address 0xD
==25354== at 0x8075F40: ??? (in /usr/bin/skype)
==25354== by 0x7F44118: ??? (in /usr/lib32/nvidia-313-updates/libGL.so.313.26)
==25354== If you believe this happened as a result of a stack
==25354== overflow in your program's main thread (unlikely but
==25354== possible), you can try to increase the size of the
==25354== main thread stack using the --main-stacksize= flag.
==25354== The main thread stack size used in this run was 8388608.
==25354== Invalid free() / delete / delete[] / realloc()
==25354== at 0x402B1CC: free (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==25354== by 0x76D47D4: __libc_freeres (in /lib/i386-linux-gnu/libc-2.17.so)
==25354== by 0x7F44118: ??? (in /usr/lib32/nvidia-313-updates/libGL.so.313.26)
==25354== Address 0xffffffff is not stack'd, malloc'd or (recently) free'd
==25354==
==25354==
==25354== HEAP SUMMARY:
==25354== in use at exit: 26 bytes in 2 blocks
==25354== total heap usage: 5 allocs, 4 frees, 342 bytes allocated
==25354==
==25354== LEAK SUMMARY:
==25354== definitely lost: 0 bytes in 0 blocks
==25354== indirectly lost: 0 bytes in 0 blocks
==25354== possibly lost: 0 bytes in 0 blocks
==25354== still reachable: 26 bytes in 2 blocks
==25354== suppressed: 0 bytes in 0 blocks
==25354== Rerun with --leak-check=full to see details of leaked memory
==25354==
==25354== For counts of detected and suppressed errors, rerun with: -v
==25354== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: nvidia-313-updates 313.26-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
Uname: Linux 3.8.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 2 15:56:53 2013
InstallationDate: Installed on 2011-04-23 (709 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
MarkForUpload: True
SourcePackage: nvidia-graphics-drivers-313-updates
UpgradeStatus: Upgraded to raring on 2013-03-26 (6 days ago)

Revision history for this message
graingert (tagrain) wrote :
Revision history for this message
graingert (tagrain) wrote :

$ LD_LIBRARY_PATH=/usr/lib/i386-linux-gnu/mesa skype

works as a workaround, seemingly proving it's an nvidia issue

graingert (tagrain)
summary: - nvidia 13.04 causes skype to crash
+ nvidia drivers on ubuntu 13.04 causes skype to crash
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nvidia-graphics-drivers-313-updates (Ubuntu):
status: New → Confirmed
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Well, we know that

  Skype + Nvidia + qtwebkit-2.3 => Problems

There are other theories about what the root problem is. Some say it's qtwebkit-2.3, because downgrading to the Quantal version of libqtwebkit4 solves the problem too. Other say that Skype needs to be rebuilt against qtwebkit-2.3.

A workaround is about to be uploaded to the archive; see bug 1155327.

Revision history for this message
goodidea (kostya-goodidea) wrote :

Please provide any update or workaround on this issue...

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.