Error 4 In Libx11.so.6.3.0
Get Kubuntu Get Xubuntu Get Lubuntu Get UbuntuStudio Get Mythbuntu Get Edubuntu Get Ubuntu-GNOME Get UbuntuKylin Ubuntu Code of Conduct Ubuntu Wiki Community Wiki Other Support Launchpad Answers Ubuntu IRC Support AskUbuntu Official Documentation User Documentation Social Media Facebook Twitter Useful Links Distrowatch Bugs: Ubuntu PPAs: Ubuntu Web Upd8: Ubuntu OMG! Ubuntu Ubuntu Insights Planet Ubuntu Activity Page Please read before SSO login Advanced Search Forum The Ubuntu Forum Community Ubuntu Official Flavours Support General Help [xubuntu] Segmentation fault errors Having an Issue With Posting ? Do you want to help us debug the posting issues ? < is the place to report it, thanks ! Results 1 to 9 of 9 Thread: Segmentation fault errors Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode May 3rd, 2009 #1 dantata View Profile View Forum Posts Private Message 5 Cups of Ubuntu Join Date Mar 2008 Beans 19 Segmentation fault errors I am having some strange segfault errors from time to time. Opera, Transmission and audacious all crashed with such errors within the last several hours. Audacious crashed on several occasions when I was adding songs to the playlist. Opera, on the other hand crashed when I was trying to close a tab. I thought I would ask for some help. I ran a memory test (Memtest86) to make sure that the issue is not due to faulty RAM. I also checked the system temperature just in case. Below is the excert of the log at /var/log/messages: Code: May 3 13:34:45 dn7 kernel: [30720.460656] opera[15405]: segfault at efd3b89e ip 08401529 sp bfcdd210 error 5 in opera[8048000+aa8000] May 3 14:06:04 dn7 kernel: [32599.180599] transmission[16328]: segfault at fffffffb ip 080b51ad sp b66d2230 error 4 in transmission[8048000+ac000] May 3 15:05:41 dn7 kernel: [36176.419690] audacious[19152]: segfault at 0 ip 08060230 sp bf9fa460 error 4 in audacious[8048000+cf000] May 3 17:50:26 dn7 kernel: [ 6743.786948] gsopcast[6664]: segfault at 0 ip b766f0f4 sp bfe45330 error 6 in libc-2.9.so[b75f8000+15c000] May 3 19:40:28 dn7 kernel: [ 5516.659993] vlc[4838]: segfault at 4 ip b226066f sp b1d55b60 error 4 in libQtGui.so.4.5.0[b20a9000+9c6000] May 3 19:49:50 dn7 kernel: [ 6078.820049] operapluginwrap[4081]: segfault at 2e746c75 ip 2e746c75 sp bf95f64c error 4 Any idea what do the numbers in the [] brackets stand for? For instance, in opera?[8048000+aa8000]? Any help would be appreciated. Last edited by dantata; May 3rd, 2009 at 06:49 P
Opened 4 years ago Last modified 3 years ago PC-BSD guest: Segfault in libX11.so.6.3.0 when choosing ACPI shutdown Reported by: KenSharp Owned by: Priority: major Component: other Version: VirtualBox 4.2.0 Keywords: Cc: Guest type: BSD Host type: Linux Description kernel: [67331.018664] VirtualBox[9804]: segfault at ffffffffc00c6b28 ip 00007f88119fec58 sp 00007fffabbfbe40 error 4 in libX11.so.6.3.0[7f88119cb000+12f000] When choosing ACPI shutdown (or Host+H) Vbox simply segfaults and exits. This happens every time. Not sure how to debug this but will, of course, do any debugging that is necessary. https://ubuntuforums.org/showthread.php?t=1147424 Running Ubuntu Precise amd64 with Unity 2D, updated. Change History comment:1 Changed 4 years ago by KenSharp This is actually 4.1.22-80657~Ubuntu~natty but I don't seem to be able to edit the details of this bug. comment:2 Changed 4 years ago by KenSharp I had no idea 4.2 was out until I opened this bug (Vbox https://www.virtualbox.org/ticket/11008 did not say there was an update). I have no idea why Vbox was choosing Natty over Precise updates <-- bug? 4.2/Precise fixes this. Please close as fixed. comment:3 Changed 4 years ago by KenSharp Scrub that previous comment, this happens all the time! Any guest. Pausing the VM then starting it again gives a black screen. The VM is still running and has to be ACPI shutdown and started again to get it working properly. This affects snapshots as they pause the machine to do so. [74356.327586] VirtualBox[24190]: segfault at 44086e18 ip 00007f2794ffac58 sp 00007fff8898b320 error 4 in libX11.so.6.3.0[7f2794fc7000+12f000] [77889.531736] VirtualBox[25640]: segfault at ffffffffa0086e18 ip 00007f41f1a60c58 sp 00007fff658780f0 error 5 in libX11.so.6.3.0[7f41f1a2d000+12f000] comment:4 Changed 4 years ago by frank Please attach a VBox.log file of such a VM session. Regarding the Natty/Precise package conflict: How did you install the package, did you download it manually or did your package manager update an older package automatically? In the latter case, check your /etc/
"Run PPAPI Flash in the renderer process" is disabled Starred by 3 users Project Member Reported by josephv@chromium.org, Apr 7 2011 https://bugs.chromium.org/p/chromium/issues/detail?id=197031 Back to list Status: Verified Owner: piman@chromium.org Closed: Apr 2011 Cc: josephv@chromium.org, davemoore@chromium.org, krisr@chromium.org, kmixter@chromium.org, zelidrag@chromium.org, brettw@chromium.org, mu...@chromium.org, rohi...@chromium.org, ihf@chromium.org Components: Blink Internals>Plugins>Flash OS: Chrome Pri: 0 Type: Bug ReleaseBlock-Nominate ReleaseBlock-Dev M-12 Sev-0 Sign in to add a comment Chrome OS Version : 0.12.374.0 Chrome Version : 12.0.729.0 Type of computer : cr48 error 4 Please specify Area- Flash What steps will reproduce the problem? 1. Go to http://www.vimeo.com/channels/hd and play a video 2. Open additional tab and go to http://www.vimeo.com/channels/hd and play a video 3. Repeat step #1 until you have 5 tabs opened and playing videos. 4. Toggle between the tabs 5. This will generate a Shockwave crash (http://code.google.com/p/chromium-os/issues/detail?id=13861) 6. error 4 in Get your client_id, to go/crash and find the crash report What is the expected output? User should be able to view crash report What do you see instead? Crash reports are not generated. I checked after 15 mins and no crash reports. Please use labels and text to provide additional information. Comment 1 by kmixter@chromium.org, Apr 7 2011 Processing Is there a uploads.log in Crash Reports directory in the profile? Does it have the crashes? If so, then maybe we didn't wait long enough. If not, maybe this is an OOM error in which case Chrome will not be able catch anything to send, or possibly this is not an operating system crash but rather an unexpected early exit. Search in /var/log/messages for segfault. Comment 2 by josephv@chromium.org, Apr 8 2011 Processing Labels: Mstone-R12 ReleaseBlock-Nominate Comment 3 by josephv@chromium.org, Apr 8 2011 Processing chronos@localhost /var/log $ more messages | grep segfault 2011-04-07T10:51:59.939213-07:00 localhost kernel: [ 737.938380] chrome[3467]: segfault at 0 ip 766b21b8 sp 7f890430 error 4 in chrome[74490000+346a000] 2011-04-07T11:0