[Bug 1530558] [NEW] Xorg crash when using VLC and google chrome
Public bug reported: Ubuntu 15.10, Lubuntu flavor, running LXDE. To reproduce 1. Start Google Chrome (latest official version, google-chrome-stable 47.0.2526.106-1 ), can contain just a single empty tab 2. Start VLC (regular distribution version, 2.2.1-3, video output set to automatic and other settings are defaults) and load a video. 3. Move cursor over the video position slider. 4. Xorg crash 4336.541] (EE) Backtrace: [ 4336.541] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55de7a03d68e] [ 4336.541] (EE) 1: /usr/bin/X (0x55de79e89000+0x1b89f9) [0x55de7a0419f9] [ 4336.541] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f61909ca000+0x352f0) [0x7f61909ff2f0] [ 4336.541] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x24f18) [0x7f618cdc5f18] [ 4336.541] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x26157) [0x7f618cdc7157] [ 4336.541] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x2e161) [0x7f618cdcf161] [ 4336.541] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x80335) [0x7f618ce21335] [ 4336.541] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x80e2c) [0x7f618ce21e2c] [ 4336.541] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x82e1a) [0x7f618ce23e1a] [ 4336.541] (EE) 9: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x58337) [0x7f618cdf9337] [ 4336.541] (EE) 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x3979f) [0x7f618cdda79f] [ 4336.541] (EE) 11: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f618cda1000+0x399a2) [0x7f618cdda9a2] [ 4336.541] (EE) 12: /usr/bin/X (0x55de79e89000+0x13f981) [0x55de79fc8981] [ 4336.541] (EE) 13: /usr/bin/X (0x55de79e89000+0xf492c) [0x55de79f7d92c] [ 4336.541] (EE) 14: /usr/bin/X (0x55de79e89000+0xf5f35) [0x55de79f7ef35] [ 4336.541] (EE) 15: /usr/bin/X (0x55de79e89000+0x5818f) [0x55de79ee118f] [ 4336.541] (EE) 16: /usr/bin/X (0x55de79e89000+0x5c34b) [0x55de79ee534b] [ 4336.541] (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f61909eaa40] [ 4336.541] (EE) 18: /usr/bin/X (_start+0x29) [0x55de79ecf6c9] [ 4336.541] (EE) [ 4336.541] (EE) Segmentation fault at address 0x0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xserver-xorg-core 2:1.17.2-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6 Uname: Linux 4.2.0-22-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Jan 2 17:22:17 2016 InstallationDate: Installed on 2015-03-19 (288 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: xorg-server UpgradeStatus: Upgraded to wily on 2015-12-11 (22 days ago) ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530558 Title: Xorg crash when using VLC and google chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1530558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530558] Re: Xorg crash when using VLC and google chrome
Xorg log ** Attachment added: "Xorg log" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1530558/+attachment/4543187/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530558 Title: Xorg crash when using VLC and google chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1530558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1530558] Re: Xorg crash when using VLC and google chrome
The bug doesn't happen if I select OpenGL output in VLC, only XVideo output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1530558 Title: Xorg crash when using VLC and google chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1530558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769644] Re: Alt-F2 (or lxpanelctl run) doesn't work
This has been fixed very recently in current lxpanel git: http://lxde.git.sourceforge.net/git/gitweb.cgi?p=lxde/lxpanel;a=commit;h=0f83fb71915fd7c87a999ebe83e41b2d033e4340 Hopefully we'll have this soon in ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769644 Title: Alt-F2 (or lxpanelctl run) doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/lxde/+bug/769644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Dmitry, I confirm your solution. I already uninstalled ureadahead (no need for it with a SSD). I added killall dhclient to my /etc/init.d/umountfs (at the beginning of the do_stop function). This problem happens for me only when I use the regular wired ethernet on my ThinkPad X230 (not just when the laptop is docked to the UltraBase as I've reported earlier) . It doesn't happen when I'm using wireless. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
I've tried patches in mentioned in comment #137, but they didn't help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216252]
You are right! :) This is fixed on my IVB with current version (intel(0): SNA compiled from 2.21.15-13-ge98cc0b). Thanks Chris. I'll be optimistic and close this bug now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1216252 Title: scrolling in chrome leads to distorted images To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1216252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
In my case the bug with unclean shutdown happens only when my machine (Thinkpad X230) is docked to the Thinkpad ultrabase when shutting it down. When I shutdown outside of a dock, everything is fine. I don't use ureadahead (have SSD), doesn't matter if there are mounted network filesystems or not, if NetworkManager is running or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1104435] Re: xfce4-session crashed with SIGSEGV in g_slice_alloc()
I confirm this bug, my machine is i5-3320M -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104435 Title: xfce4-session crashed with SIGSEGV in g_slice_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-session/+bug/1104435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056532] Re: geeqie-standard crashes on start with SIGSEGV in editor_command_parse() when unity-lens-photos is installed
My fix has been merged in the current official geeqie upstream here: https://gitorious.org/geeqie/geeqie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056532 Title: geeqie-standard crashes on start with SIGSEGV in editor_command_parse() when unity-lens-photos is installed To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-photos/+bug/1056532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056532] Re: geeqie-standard crashes on start with SIGSEGV in editor_command_parse() when unity-lens-photos is installed
This patch is against 1.1 but should apply to 1.0 too, it fixes the segfault in geeqie itself. ** Patch added: fix segfault https://bugs.launchpad.net/ubuntu/+source/geeqie/+bug/1056532/+attachment/3416179/+files/geeqie-patch-editors-segfault.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056532 Title: geeqie-standard crashes on start with SIGSEGV in editor_command_parse() when unity-lens-photos is installed To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-photos/+bug/1056532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036075] [NEW] tp_smapi doesn't support X230
Public bug reported: It seems that tp_smapi 0.41 doesn't support my Thinkpad X230. When trying to insert the module I get this message in dmesg [ 262.302908] thinkpad_ec: thinkpad_ec_request_row: arg0 rejected: (0x01:0x00)-0x00 [ 262.302910] thinkpad_ec: thinkpad_ec_read_row: failed requesting row: (0x01:0x00)-0xfffb [ 262.302911] thinkpad_ec: initial ec test failed What information or document should one have to properly implement this? I have no experience with thinpad low level stuff, so any help is appreciated. This has also been reported upstream (linux-think...@linux-thinkpad.org mailing list). ** Affects: tp-smapi (Ubuntu) Importance: Undecided Status: New ** Description changed: It seems that tp_smapi 0.41 doesn't support my Thinkpad X230. When trying to insert the module I get this message in dmesg - [ 262.302908] thinkpad_ec: thinkpad_ec_request_row: arg0 rejected: (0x01:0x00)-0x00 [ 262.302910] thinkpad_ec: thinkpad_ec_read_row: failed requesting row: (0x01:0x00)-0xfffb [ 262.302911] thinkpad_ec: initial ec test failed What information or document should one have to properly implement - this. I have no experience with thinpad low level stuff, so any help + this? I have no experience with thinpad low level stuff, so any help is appreciated. This has also been reported upstream (linux-think...@linux-thinkpad.org mailing list). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036075 Title: tp_smapi doesn't support X230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tp-smapi/+bug/1036075/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 772252] [NEW] For newer SandyBridge chipsets, upstream version 4.20 is required
Public bug reported: Binary package hint: memtest86+ Current ubuntu version of memtest86+ - 4.10 - doesn't work with my SandyBridge ASUS P8 H67-M motheboard, and most probably with other SandyBridge machines. Upstream version 4.20 is availabile, and it implements proper SandyBridge support. I suggest updating ubuntu package to include that as soon as possible. ** Affects: memtest86+ (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/772252 Title: For newer SandyBridge chipsets, upstream version 4.20 is required -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305695] Re: Jaunty doesnt allow screenshots getting No command 33 has been defined error with printscreen
I can also confirm this, In addition, probably because i use a usb attached keyboard (on a Cypress USB2PS2 converter), the screenshot functionality is invoked many times, and my PC dies from the heavy swapping (tested on livecd 20081218.1). -- Jaunty doesnt allow screenshots getting No command 33 has been defined error with printscreen https://bugs.launchpad.net/bugs/305695 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 3731] Re: Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
@Tony, Your edid seems to be correct, and X should use it without problems. Video mode setting code for the OS splash screen is in the kernel, and we hope it will be solved when (and if) the mode setting code is moved to the kernel. Regardless of that, current kernel code could be patched, but I'm not currently looking into that. -- Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect https://bugs.launchpad.net/bugs/3731 You received this bug notification because you are a member of Kubuntu Team, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 27667] Re: Problems with xresprobe Samsung 243T LCD
Jerone, I share your emotions about fixing this bug, because I''ve seen a lot of instances of ubuntu showing the wrong resolution for both CRT and LCD displays. Other debian based linux distributions (such as knoppix) actually used get-edit|parse-edid to generate X configuration Monitor section, which seems to be better way to generate it than ddprobe, since it uses the monitors own information about the recommended resolution. Current Xorg server (I'm using git version, but i guess 1.3 also works) has functionality for getting edid info by itself. It works for me if don't enter any monitor specific information in the Xorg.conf monitor section, so that it looks like this: Section Monitor IdentifierGeneric Monitor OptionDPMS EndSection If it doesn't work, it may be that your monitor is sending data with an invalid DDC checksum, but otherwise correct. If it doesn't work, please send the output from the get-edid command (this is in the read-edid package) to xorg list and to this bug. get-edit SM243T.edid, because we're trying to work out how to deal with bad checksum, but otherwise good edid info. -- Problems with xresprobe Samsung 243T LCD https://bugs.launchpad.net/bugs/27667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50048] Re: Unable to adjust refresh rate..
get-edid is in the read-edid package, and it runs as root -- Unable to adjust refresh rate.. https://bugs.launchpad.net/bugs/50048 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50048] Re: Unable to adjust refresh rate..
The new Xorg server should be able to query monitor by itself for DDC edid info about it's capatibilities. This functionality works for me if I leave out monitor specific information from my Xorg.conf like this: Section Monitor IdentifierGeneric Monitor OptionDPMS EndSection In the edid info there should be data for the recommended resolution and refresh rate. The problem is however that some monitors have this data wrong (so you don't get the right resolution or refresh rate), or the checksum of the complete data wrong (so you don't get the edid data used by X at all). Either way, could you send the output of the get-edid Philips170B.edid as attachment to this bug, and possibly the xorg mailing list, so we can see what's wrong with the data and add a quirk for it in the Xorg code? -- Unable to adjust refresh rate.. https://bugs.launchpad.net/bugs/50048 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 3731] Re: Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect
I believe that the same class of problems are causing many monitor resolution/refresh rate problems as listed in bugs 50048, 27667 (these are the bugs I made comments on) and probably many more. The problems with the edid data. The new Xorg server should be able to query monitor by itself for DDC edid info about it's capatibilities, without ddcprobe. This functionality works for me if I leave out monitor specific information from my Xorg.conf like this: Section Monitor Identifier Generic Monitor Option DPMS EndSection In the edid there should be data for the recommended resolution and refresh rate. The problem is however that some monitors have this data wrong (so you don't get the right resolution or refresh rate), or the checksum of the complete data wrong (so you don't get the edid data used by X at all). Either way, could you send the output of the get-edid yourmonitormakeandmodel.edid as attachment to this bug, and possibly the xorg mailing list, so we can see what's wrong with the data and add a quirk for it in the Xorg code? get-edid is in the read-edid package, and it's output can be piped to parse-edid to create the Xorg.conf monitor section). I'm not sure why the checksum for edid data for my monitor is incorrect, it's probably a quirk of my monitor, but for other cases where edid data is different on multiple runs of get-edid or Xorg, it might be best to permanently store this data to be used if nothing valid is detected on subsequent runs. If this gets done in time, it's quite possible that gutsy will finally have good out of the box monitor autodetection support. -- Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs incorrect https://bugs.launchpad.net/bugs/3731 You received this bug notification because you are a member of Kubuntu Team, which is a subscriber of a duplicate bug. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Re: [Bug 27667] Re: Problems with xresprobe Samsung 243T LCD
Yeah, the goal is that X can do this by itself, and I guess other distros are using get-edid|parse-edid or something similar to make this happen. Since your get-edid output is similar to the one I get on my samsung syncmaster 900NF monitor, I guess that X discards your monitors edid information too. Are you sure you don't have the monitor section filled with data about the monitor when using the nv driver? I guess that nvidia binary driver could have separate edid code, but I doubt that nv has one. I hope we'll have some code in Xorg server soon, so you'll be able to test the fix. On 6/9/07, Jerone Young [EMAIL PROTECTED] wrote: Nvidia driver NV driver seem to read the edid just fine. Also on other distros things are fine...but when I run get-edid under Feisty I get this: [EMAIL PROTECTED]:~# get-edid get-edid: get-edid version 1.4.1 Performing real mode VBE call Interrupt 0x10 ax=0x4f00 bx=0x0 cx=0x0 Function supported Call successful VBE version 300 VBE string at 0x0 NVIDIA VBE/DDC service about to be called Report DDC capabilities Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x0 cx=0x0 Function supported Call successful Monitor and video card combination does not support DDC1 transfers Monitor and video card combination supports DDC2 transfers 0 seconds per 128 byte EDID block transfer Screen is not blanked during DDC transfer Reading next EDID block VBE/DDC service about to be called Read EDID Performing real mode VBE call Interrupt 0x10 ax=0x4f15 bx=0x1 cx=0x0 Function supported Call failed The EDID data should not be trusted as the VBE call failed EDID claims 255 more blocks left EDID blocks left is wrong. Your EDID is probably invalid. -- Problems with xresprobe Samsung 243T LCD https://bugs.launchpad.net/bugs/27667 You received this bug notification because you are a direct subscriber of the bug. -- Problems with xresprobe Samsung 243T LCD https://bugs.launchpad.net/bugs/27667 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
