[Ubuntu-x-swat] [Bug 1516531] Re: Fullscreen Freeze.
Hey Christopher, I see you are still self-subscribed so I hope you see this update. I had a few more instances occur between Kodi and Chrome (viewing youtube) while in full-screen. First, I want to say that there are NO crash reports when the freeze occurs. Crash reports do get created such as one relating to gnome when I was transcoding rough videos (I think relating to thumbnail generation with the output file). I also am able to confirm what I thought was a possible cause in a particular case. Sometimes the freeze occurs while coming out of fullscreen (ESC for chrome or \ for kodi). But what happened just now which made it very clear was a desktop notification from skype caused the freeze to occur even though I wasn't trying to come out of fullscreen. I went to tty1 while still in the system, and like I just mentioned, there were no crash logs. I DID run apport-cli to save 2 files to my desktop. 1) for xorg by process name and 2) for gnome-session by pid. If you think either of these will be helpful or have something else you want me to try/capture, let my know and I'll make the file submissions. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1516531 Title: Fullscreen Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516531/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1406725] Re: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1406725 Title: Severe graphical corruption (mostly horizontal streaks/lines) running software clients (including Xmir) on android To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1406725/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1523444] [NEW] Xorg crahed with segfault
Public bug reported: I was about to click on a button in Chromium when Xorg unexpectedly crashed. This bug just happened and I doubt that it is reproducible. This might be a kernel and not an xorg error, please re-categorize if needed. Relevant section from the Xorg files: [ 6812.749] (EE) Backtrace: [ 6812.749] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55f0bc03968e] [ 6812.749] (EE) 1: /usr/bin/X (0x55f0bbe85000+0x1b89f9) [0x55f0bc03d9f9] [ 6812.749] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e9cbbe000+0x352f0) [0x7f5e9cbf32f0] [ 6812.749] (EE) [ 6812.749] (EE) Segmentation fault at address 0x0 [ 6812.749] (EE) Fatal server error: [ 6812.749] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 6812.749] (EE) [ 6812.749] (EE) Relevant section from syslog: Dec 7 11:39:25 ultra-d kernel: [ 6818.582120] [ cut here ] Dec 7 11:39:25 ultra-d kernel: [ 6818.582137] WARNING: CPU: 3 PID: 1318 at /build/linux-26_gwp/linux-4.2.0/drivers/gpu/drm/i915/i915_gem.c:5269 i915_gem_track_fb+0x129/0x140 [i915]() Dec 7 11:39:25 ultra-d kernel: [ 6818.582139] WARN_ON(!(old->frontbuffer_bits & frontbuffer_bits)) Dec 7 11:39:25 ultra-d kernel: [ 6818.582139] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nfsv3 nfs_acl rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache hp_wmi spa rse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp joydev snd_hda_codec_hdmi input_leds snd_hda_codec_realtek kvm_intel snd_hda_codec_generic kvm snd_hda_intel snd_hda_codec crct10dif_ pclmul snd_hda_core crc32_pclmul snd_hwdep snd_pcm aesni_intel aes_x86_64 lrw gf128mul snd_seq_midi glue_helper snd_seq_midi_event ablk_helper cryptd snd_rawmidi snd_seq snd_seq_device serio_raw snd_timer snd so undcore mei_me mei lpc_ich 8250_fintek tpm_infineon mac_hid ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_recent xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6ta ble_filter ip6_tables nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables sunrpc parport_pc p pdev lp parport autofs4 hid_generic usbhid hid i915 psmouse i2c_algo_bit drm_kms_helper e1000e ahci drm libahci ptp pps_core wmi video Dec 7 11:39:25 ultra-d kernel: [ 6818.582178] CPU: 3 PID: 1318 Comm: Xorg Tainted: G OE 4.2.0-19-generic #23-Ubuntu Dec 7 11:39:25 ultra-d kernel: [ 6818.582179] Hardware name: Hewlett-Packard HP EliteDesk 800 G1 SFF/1998, BIOS L01 v02.65 07/13/2015 Dec 7 11:39:25 ultra-d kernel: [ 6818.582180] 466f5698 880212e8fac8 817e93f9 Dec 7 11:39:25 ultra-d kernel: [ 6818.582182] 880212e8fb20 880212e8fb08 8107b3d6 Dec 7 11:39:25 ultra-d kernel: [ 6818.582183] 880211e43600 0010 880211b7c000 880211b7c000 Dec 7 11:39:25 ultra-d kernel: [ 6818.582184] Call Trace: Dec 7 11:39:25 ultra-d kernel: [ 6818.582188] [] dump_stack+0x45/0x57 Dec 7 11:39:25 ultra-d kernel: [ 6818.582191] [] warn_slowpath_common+0x86/0xc0 Dec 7 11:39:25 ultra-d kernel: [ 6818.582193] [] warn_slowpath_fmt+0x55/0x70 Dec 7 11:39:25 ultra-d kernel: [ 6818.582200] [] i915_gem_track_fb+0x129/0x140 [i915] Dec 7 11:39:25 ultra-d kernel: [ 6818.582211] [] intel_prepare_plane_fb+0xe7/0x1a0 [i915] Dec 7 11:39:25 ultra-d kernel: [ 6818.582215] [] drm_atomic_helper_prepare_planes+0x59/0xe0 [drm_kms_helper] Dec 7 11:39:25 ultra-d kernel: [ 6818.582225] [] ? drm_atomic_check_only+0x215/0x540 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582235] [] intel_atomic_commit+0x42/0x100 [i915] Dec 7 11:39:25 ultra-d kernel: [ 6818.582242] [] drm_atomic_commit+0x37/0x60 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582245] [] drm_atomic_helper_plane_set_property+0x87/0xc0 [drm_kms_helper] Dec 7 11:39:25 ultra-d kernel: [ 6818.582250] [] ? _object_find+0x69/0xa0 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582255] [] drm_mode_plane_set_obj_prop+0x2d/0x90 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582261] [] drm_mode_obj_set_property_ioctl+0x1c6/0x270 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582265] [] drm_ioctl+0x125/0x610 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582267] [] ? fsnotify+0x316/0x4a0 Dec 7 11:39:25 ultra-d kernel: [ 6818.582272] [] ? drm_mode_obj_get_properties_ioctl+0xa0/0xa0 [drm] Dec 7 11:39:25 ultra-d kernel: [ 6818.582274] [] do_vfs_ioctl+0x295/0x480 Dec 7 11:39:25 ultra-d kernel: [ 6818.582276] [] ? __sb_end_write+0x35/0x70 Dec 7 11:39:25 ultra-d kernel: [ 6818.582277] [] ? vfs_write+0x15a/0x1a0 Dec 7 11:39:25 ultra-d kernel: [ 6818.582278] [] SyS_ioctl+0x79/0x90 Dec 7 11:39:25 ultra-d kernel: [ 6818.582280] [] entry_SYSCALL_64_fastpath+0x16/0x75 Dec 7 11:39:25 ultra-d kernel: [ 6818.582281] ---[ end trace 6e41c462e0fbe35d ]---
[Ubuntu-x-swat] [Bug 1517998] Re: Crash after resume.
Boban Aleksov, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-503 ** Tags added: latest-bios-310 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1517998 Title: Crash after resume. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1517998/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1506914] Re: Screen brightness not working using keyboard shortcut fn+F5/F6 not working.
Vidvranjek, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags removed: bios-outdated-205 ** Tags added: latest-bios-205 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1506914 Title: Screen brightness not working using keyboard shortcut fn+F5/F6 not working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1506914/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1523088] Re: WARN_ON(!wm_changed) warning and stacktrace in kernel log
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1523088 Title: WARN_ON(!wm_changed) warning and stacktrace in kernel log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1523088/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1519029] Re: Lenovo X240 in Dock, bad resolution on logon and no mouse pointer
OK, I think there are actually two separate bugs here. (1) The display corruption issue was resolved by swapping in an HDMI cable for the VGA cable. Still, this worked before so it's a regression, but not a really horrible one. I should have been using an HDMI cable anyway. (2) The mouse pointer issue is resolved if I restart lightdm. There are several open bugs about that and discussions in various fora. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1519029 Title: Lenovo X240 in Dock, bad resolution on logon and no mouse pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1519029/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1523688] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1521268 *** https://bugs.launchpad.net/bugs/1521268 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1521268, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1523688/+attachment/4531135/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531138/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531150/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531152/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531153/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531154/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1523688/+attachment/4531155/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1521268 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1523688 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1523688/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected
Tested 4.3 kernel, failed to boot in any scenario. Hangs on Loading ramdisk. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1520519 Title: ASUS ROG GL552 TouchPad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520519/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected
Indeed I have tried to update the kernel. Unfortunately, the 4.3 kernel does not boot. It hangs on Loading Ramdisk. Also tried nomodeset option to no avail. I have tried this as a Ubuntu 15.10 live USB and also by upgrading the kernel to 4.3 on a running Ubuntu 14.04 installation. Both hang at Loading Ramdisk. I am a total newbie but it seems the newer kernel is not capable of seeing the hard drives? If you feel there will be a major difference, I am plenty happy to attempt loading the 4.4 kernel to the machine, however, it seems there are more issues at play and I don't know if it will make a large difference. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1520519 Title: ASUS ROG GL552 TouchPad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1520519/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1523366] Re: fglrx (not installed): fglrx kernel module failed to build
*** This bug is a duplicate of bug 859101 *** https://bugs.launchpad.net/bugs/859101 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 859101, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 859101 fglrx 2:8.881-0ubuntu2: fglrx kernel module failed to build (kernel includes at ... not found or incomplete file: .../linux/version.h) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1523366 Title: fglrx (not installed): fglrx kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1523366/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1449560] Re: Cannot login with Nvidia Optimus hardware installed(Ubuntu 15.04)
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1449560 Title: Cannot login with Nvidia Optimus hardware installed(Ubuntu 15.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1449560/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
