[Ubuntu-x-swat] [Bug 1568224] [NEW] psmouse FingerSensingPad lost synchronization, throwing bytes away
Public bug reported: My first bug report, I apologize if I don't do it right, and please let me know how to improve it. Asus Zenbook UX31E initially with Ubuntu 11:10, then 12.04, and then 14.04 worked great until a few weeks ago, when the trackpad became unusable (mouse jumps all over the screen and starts moving and clicking around by itself). Booting from USB with Ubuntu 16.04 beta has the same problem. Dmesg always shows the following type of errors: psmouse serio4 bad data from KBC - timeout psmouse serio4 bad data from KBC - bad parity psmouse serio4 FingerSensingPad at isa0060/serio4/input0 lost synchronization, throwing 3 bytes away The laptop works fine with an external USB mouse, as long as I don't accidentally touch the trackpad. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-input-synaptics 1.8.2-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CasperVersion: 1.368 CurrentDesktop: Unity Date: Sat Apr 9 04:15:38 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: ASUSTeK Computer Inc. UX31E ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz.efi SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160318-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.1-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Apr 9 03:39:35 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6107 vendor COR xserver.version: 2:1.18.1-1ubuntu4 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial ** Attachment added: "dmesg >dmesg.txt; cat /proc/bus/input/devices >devices.txt; xinput list --long >xinput.txt; cp /var/log/Xorg.0.log ./Xorg.0.log.txt; tar -zcvf files.tar.gz *.txt" https://bugs.launchpad.net/bugs/1568224/+attachment/4629927/+files/files.tar.gz -- 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/1568224 Title: psmouse FingerSensingPad lost synchronization, throwing bytes away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1568224/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
now happens to me a black screen and nothing else, I upgraded to mir 0:21 and does not access its only black screen rhyme -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1549455] Re: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"]
I experience this bug on my WeTab. On login, I get a black screen. How can I help to fix it? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1549455 Title: Unity 8 doesn't load on Intel Pineview graphics [qtubuntu: ASSERT: "eglDestroyContext(mEglDisplay, mEglContext) == EGL_TRUE"] To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1549455/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip
A couple weeks ago I did a fresh install of ubuntu-14.04.desktop.iso LTS and the garbled text bug 1507255 was back. Usual fix of Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "uxa" EndSection worked. Xenial new installs have been fine lately. Putting that uxa fix in Xenial prevents X windows from running. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1507255 Title: Garbled graphics in Wily with Intel GMA4500 chip To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1507255/+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 1568180] [NEW] Mouse scroll wheel does not work, and thumb buttons
Public bug reported: General information For all bug categories the following general information should be provided: Ensure you report the bug via ubuntu-bug xorg as outlined above. T What is the full manufacturer and model of your mouse. AULA Killing the Soul Gaming Optical Mouse How is your mouse connected to your PC: serial, PS/2, USB, USB wireless, etc. USB What mechanism does your mouse use: roller ball, optical, trackball, etc. Optical How many physical buttons and scrollwheels does you mouse have? 2-right and left 3- scroll up/down + middle click 2 - thumb buttons In case some mouse buttons or scrollwheels don't work (as expected) Provide the general information. T Open a terminal and enter the following commands: xmodmap -pp > ~/xmodmap-pp xev | grep -i button T Put the mouse cursor into the rectangle and push your mouse buttons. Mention in the bug report which button number is reported, e.g. left = 1, scrollwheel up = 4, horizontal scrollwheel left = 6, thumb button = 8, pinkie button = 9, ... 1 and 3 are the only buttons this utility detects. Attach as separate attachments to your bug report /var/log/Xorg.0.log and ~/xmodmap-pp. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-35.40~14.04.1-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Apr 8 17:25:56 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 15.201, 4.2.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3112] InstallationDate: Installed on 2016-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7376 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-35-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.B0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: K9A2 Platinum (MS-7376) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.B0:bd06/21/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7376:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9A2Platinum(MS-7376):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7376 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Apr 8 16:56:57 2016 xserver.configfile: /etc/X11/xorg.conf xserver.errors: fglrx(0): Cannot read int vect fglrx(0): Cannot read int vect AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Attachment added: "xmodmap-pp" https://bugs.launchpad.net/bugs/1568180/+attachment/4629749/+files/xmodmap-pp -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu.
[Ubuntu-x-swat] [Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
moving to mesa until it's better known, might be triggered by llvm 3.8 and related to bug #1553174 ** Package changed: compiz (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+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 1562387] Re: digimend / wacom drivers do not recognize chinese clone
The xorg.conf.d configuration files are applied one after the other, so your edits to 10-evdev.conf should be unnecessary (since the settings from your 50-huion.conf file will be applied after it). I would suggest filing a bug with linuxwacom (on Sourceforge) indicating that Huion tablets are not covered by the 50-wacom.conf file like other tablets. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1562387 Title: digimend / wacom drivers do not recognize chinese clone To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1562387/+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 1564156] [NEW] xenial: invalid opcode when using llvmpipe
You have been subscribed to a public bug: Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support: /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). ** Affects: system76 Importance: Critical Assignee: Jason Gerard DeRose (jderose) Status: Triaged ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- xenial: invalid opcode when using llvmpipe https://bugs.launchpad.net/bugs/1564156 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. ___ 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 1568104] [NEW] Xorg Needs KVM Support within UbuntuBSD
Public bug reported: When starting X in a KVM instance on UbuntuBSD, Xorg crashes with the following log: http://paste.ubuntu.com/15696451/ ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntubsd xorg xorg-server -- 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/1568104 Title: Xorg Needs KVM Support within UbuntuBSD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568104/+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 1565333] Re: ubuntuBSD support
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/1565333 Title: ubuntuBSD support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1565333/+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 1565333] Re: ubuntuBSD support
xorg also needs KVM Support within ubuntuBSD -- 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/1565333 Title: ubuntuBSD support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1565333/+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 1567343] Re: I am just trying to help you !
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1567343 Title: I am just trying to help you ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1567343/+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 1565224] Re: error
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1565224 Title: error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565224/+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 1243642] Re: .Xmodmap not automatically loaded on start
My use case: remap the ALT and CMD keys on a Macbook so that I get the ALT and SUPER keys on the place where I am used to find them on a "normal" keyboard. -- 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/1243642 Title: .Xmodmap not automatically loaded on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1243642/+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 1566691] Re: Xorg crashed with SIGABRT
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/1566691 Title: Xorg crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1566691/+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 1537065] Re: XRandR Error
To be sure, please give me the output `xrandr` without any options, and of `xrandr --verbose` -- but this sounds a lot like a bug in xrandr and not arandr. (even with VGA2 absent, `xrandr --output foobar -d :0` gives me `warning: output foobar not found; ignoring`. Please include `xrandr --version` as well. -- 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/1537065 Title: XRandR Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1537065/+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 1553328] Re: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref()
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref() To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1553328/+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 1542629] Re: Session crashes when second monitor is connected
I am also suffering from this issue. It occurs with and without nvidia-361 drivers installed. Loading ubuntu causes the computer to freeze. When I use my second window manager, awesome wm, the second monitor isnt detected but the system does not crash. It seems I am only affected by the issue with HDMI. Using DSUB causes no issue. -- 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/1542629 Title: Session crashes when second monitor is connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1542629/+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 1567898] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1543192 *** https://bugs.launchpad.net/bugs/1543192 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 #1543192, 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/1567898/+attachment/4628864/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628867/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628881/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628883/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628884/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628885/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1567898/+attachment/4628886/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() ** 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/1567898 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1567898/+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 1567841] [NEW] One of my two graphics cards has started to freeze the screen
Public bug reported: I run a setup of 2 radeon graphics cards, with 3 screens, in the following layout from left to right counting from 0: Card 0 Screen 1, Card 1 Screen 0, Card 0 Screen 0 rotated ccw I have been running this setup for a year and it has worked fine. This monday I updated some packages and did a reboot, and I usually reboot just once a month cause I patch my running kernel with uptrack. After the reboot I started noticing problems with the second card, Card 1 above. With a mean time between failures of about an hour, the second card freezes the screen, I usually notice that the mouse pointer isn't visible anymore when I move it across from one screen to the middle one. For future reference, the window I have on the middle screen is a fullscreen emacs window. I have tried the following kernels: vmlinuz-3.13.0-77-generic, vmlinuz-3.13.0-79-generic, vmlinuz-3.13.0-83-generic All have the same problem. And nothing shows up in dmesg when the freeze occurs, or in the Xorg.0.log, I made copies from before and after a freeze. If I move the mouse, that I can't see, onto the middle screen, make emacs the active window (again I can't see this), scroll around a bit with the arrow keys and take a screenshot, the screenshot shows the correctly scrolled window, so the big X buffer is actually correctly updated. If I CTRL-ALT-L to lock the screens, they all go black, but when you press enter only the screens on Card 0 shows the lock screen, the middle one again shows frozen emacs. CTRL-ALT-F1 shows two text terminals on the outermost screens, in the middle, you've guessed it, frozen emacs. If I go to the menu and select Switch user, surprise! Now the frozen screen is gone and it is a gray login screen with the login menu actually on the screen to the right. Log back into my still running user, boooh, it again shows the same frozen emacs. Switch to a completely new user, screen in middle is correct and working. And lastly if I log out completely from my user and log in again the screen is now unfrozen, but I have lots of work and it is really really annoying to have to log out 8 times during a day at work. I'm gonna try one more ancient kernel just to see if there have been some changes to drm or the radeon driver, but I am pretty stumped on this one. It all worked fine last week. Description:Ubuntu 14.04.4 LTS Release:14.04 Linux rymdborje 3.13.0-77-generic #121-Ubuntu SMP Wed Jan 20 10:50:42 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,gnomecompat,snap,imgpng,regex,animation,place,move,vpswitch,mousepoll,grid,unitymtgrabhandles,expo,workarounds,session,wall,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 8 10:38:17 2016 DistUpgraded: 2015-03-16 15:26:59,578 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.36, 3.13.0-65-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-77-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-79-generic, x86_64: installed virtualbox, 4.3.36, 3.13.0-83-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:03f2] Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] [1002:6613] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:04bb] InstallationDate: Installed on 2012-03-13 (1486 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-77-generic root=/dev/mapper/fiskgunnar-root ro nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2015-03-16 (388 days ago) dmi.bios.date: 12/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0906 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 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.:bvr0906:bd12/22/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name
[Ubuntu-x-swat] [Bug 1553441] Re: Only one monitor working at the time (xorg-amdgpu)
** Package changed: xserver-xorg-video-amdgpu (Ubuntu) => xserver-xorg- video-ati (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1553441 Title: Only one monitor working at the time (xorg-amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1553441/+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
