compiz crashes when run in vnc4server. unity 2D works ok.

Bug #1216201 reported by Ilya
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When trying to connect to vnc4server (started using xinetd), after login vnc client shows a grey screen and syslog has these messages:

Aug 23 19:35:50 fs1 kernel: [82654.744000] compiz[6959]: segfault at 60 ip 00007fe74a54eb80 sp 00007ff
f6e15d978 error 4 in libcomposite.so[7fe74a541000+23000]
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: Child process 6959 was already dead.
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: Application 'compiz.desktop' killed by signal 11
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: App 'compiz.desktop' respawning too quickly
Aug 23 19:35:50 fs1 gnome-session[6881]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 23 19:35:50 fs1 kernel: [82655.356000] compiz[7023]: segfault at 60 ip 00007f8532476b80 sp 00007ff
f9ac3fa68 error 4 in libcomposite.so[7f8532469000+23000]
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: App 'compiz.desktop' respawning too quickly
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: Application 'compiz.desktop' killed by signal 11
Aug 23 19:35:50 fs1 gnome-session[6881]: WARNING: App 'compiz.desktop' respawning too quickly

xinetd service configuration:
service Xvnc
{
  type = UNLISTED
  disable = no
  socket_type = stream
  protocol = tcp
  wait = yes
  user = root
  server = /usr/bin/Xvnc
  server_args = :1 -inetd -once -geometry 1800x1000 -depth 24 -query localhost -DisconnectClients=0 -NeverShared -auth /root/.Xauthority -rfbauth /root/vncpasswd -rfbport 5901 -pn -SecurityTypes VncAuth -fp /usr/share/fonts/X11/misc/ -co /usr/share/X11/rgb
  port = 5901
  log_type = SYSLOG daemon info
  log_on_failure = HOST
  log_on_success = PID HOST EXIT
}

selecting "Ubuntu 2D" session on the login screen works ok.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: compiz 1:0.9.7.12-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
Uname: Linux 3.2.0-49-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.0.1-0ubuntu17.4
Architecture: amd64
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]
CompositorRunning: compiz
Date: Fri Aug 23 21:14:28 2013
DistUpgraded: 2013-07-20 13:21:12,205 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 4.1.12, 3.2.0-49-generic, x86_64: installed
 virtualbox, 4.1.12, 3.2.0-51-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
MachineType: System manufacturer System Product Name
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
ProcKernelCmdLine: root=UUID=28bc8a03-fd03-4b80-a5aa-0e6caa6549d9 ro notsc splash vga=0x317
SourcePackage: compiz
UpgradeStatus: Upgraded to precise on 2013-07-20 (34 days ago)
dmi.bios.date: 05/07/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO GEN3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3402:bd05/07/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPROGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.7.12-0ubuntu2
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.2
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.13
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

Revision history for this message
Ilya (iva2k) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Ilya, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
gksudo gedit /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please follow https://wiki.ubuntu.com/DebuggingCompiz when you file this crash report so the necessary information is provided.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in compiz (Ubuntu):
status: New → Invalid
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.