[Ubuntu-x-swat] [Bug 1725236] Re: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10
I see same problem running Ubuntu 16.04 with Geforce GTX 1060 card, that is vulkan programs failing with VK_ERROR_INCOMPATIBLE_DRIVER. Attaching output of the vulkaninfo just in case. Replacing libGL.so.1 with libGLX_nvidia.so.0 in nvidia_icd.json also solves the issue for me. ** Attachment added: "valkaninfo_error" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1725236/+attachment/4996058/+files/valkaninfo_error -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1725236 Title: vulkaninfo fails with VK_ERROR_INCOMPATIBLE_DRIVER since 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1725236/+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 1725991] Re: GNOME applications are not shown in wmctrl -lx output on Wayland
This is correct, as far as I know. wmctrl is for X window management whereas GNOME/GTK and some other apps are native Wayland not using X. Only legacy apps using Xwayland will show up in wmctrl. Although you could ask wmctrl for some kind of enhancement to list the non-X apps. ** Changed in: wayland (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: wmctrl (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725991 Title: GNOME applications are not shown in wmctrl -lx output on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725991/+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 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1720213 Title: Word moving with left-arrow-ctrl broken in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720213/+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 1720901] Re: VLC under Wayland causes system freezes in fullscreen mode
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1720901 Title: VLC under Wayland causes system freezes in fullscreen mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720901/+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 1719408] Re: Application window outside of its frame in spread mode
Still in the 17.10 final release too. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1719408 Title: Application window outside of its frame in spread mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1719408/+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 1717474] Re: Multi monitor config issues
** Tags added: multimonitor ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1717474 Title: Multi monitor config issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1717474/+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 1705124] Re: Snap apps have blurry icons in Wayland session
** No longer affects: wayland (Ubuntu) ** Summary changed: - Snap apps have blurry icons in Wayland session + Snap apps have pixelated icons in Wayland session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705124 Title: Snap apps have pixelated icons in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705124/+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 1710145] Re: "mid-click lower" not woking with headerbar in Wayland session
*** This bug is a duplicate of bug 1698083 *** https://bugs.launchpad.net/bugs/1698083 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 1698083, 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. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1698083 Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1710145 Title: "mid-click lower" not woking with headerbar in Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1710145/+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 1717474] Re: Multi monitor config issues
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- 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/1717474 Title: Multi monitor config issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1717474/+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 1231454] Re: Wayland on Mir
Wayland is just a protocol, so it doesn't have "backends" of its own. Actually, desktop environments that support Wayland clients use "native" backends. That means they implement their own logic to interface with the kernel and the hardware. So you would be asking for a mir client that emulates that kernel DRM/KMS layer. I don't think anyone is ever going to do that. >From another perspective though, good news! Mir 0.28.0 introduces support for Wayland apps. ** Package changed: wayland (Ubuntu) => mir ** Changed in: mir Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1231454 Title: Wayland on Mir To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1231454/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
It sounds more like a kernel issue if the touchpad's not working at all. If you install and run 'sudo evtest', is the touchpad device listed and testable? (try also in a separate VT login - Ctrl+Alt+F4) ** Changed in: libinput (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1726934/+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 1708994] [NEW] package xserver-xorg-video-ast-hwe-16.04 missing
You have been subscribed to a public bug: There is no xserver-xorg-video-ast-hwe-16.04 package. So i can not use the ASpeed graphics for output anymore. I needed the hwe for the GTX 1060 nouveau driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evince 3.18.2-1ubuntu4.1 ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 7 06:51:11 2017 ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug hwe xenial xorg xserver -- package xserver-xorg-video-ast-hwe-16.04 missing https://bugs.launchpad.net/bugs/1708994 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 1696929] Re: X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy
Ah, yes sorry. I've changed the bug title again because generalizing was just asking for trouble. There would be a never-ending stream of "me too! not fixed!" from other users with other hardware. ** Summary changed: - Touchpads are unresponsive and laggy + X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1696929/+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 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
** Package changed: evince (Ubuntu) => xorg (Ubuntu) -- 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/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1708994/+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 1727696] [NEW] System does not shut down without Ctrl+Alt+F7
Public bug reported: This is a fresh 17.10 installation, for some reason defaulting to Xorg instead of wayland (no choice given in the login screen). Anyway, shutting down from X session doesn't work. Screen stays blank black, cursor blinking in top left corner. Seems like it's stuck there forever (haven't had patience to wait long enough). Found a workaround: in the black screen cursor blinking state above, hit Ctrl+Alt+F7. One second or so after that, the system shuts down cleanly every time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 BootLog: /dev/sda1: clean, 153154/2842624 files, 1254197/11368960 blocks CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 14:27:05 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. N56VZ [1043:2103] InstallationDate: Installed on 2017-10-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. N56VZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=be8c6652-102f-4bc2-9739-4c7954b40a80 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N56VZ.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N56VZ 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.:bvrN56VZ.217:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N56VZ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- 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/1727696 Title: System does not shut down without Ctrl+Alt+F7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727696/+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 1708874] Re: Touchpad stops working after a few seconds
I have the same, identical bug with the IdeaPad 320-15ABR (same of Ben i think, according with him hardware specs). Ubuntu 17.10 and Linux 4.13.0-16-generic I think the package provided isn't the right one. As I just wrote the bug is identical, but i the package xserver-xorg-input-synaptic isn't installed on my system. So the issue should be find somewhere else. I just tried installing the kernel 4.14 RC6, but the bug is still here. Some ideas? my /proc/bus/input/devices entry: I: Bus=0018 Vendor=06cb Product=8251 Version=0100 N: Name="Synaptics TM3336-001" P: Phys=i2c-SYNA2B36:00 S: Sysfs=/devices/platform/AMD0010:00/i2c-0/i2c-SYNA2B36:00/0018:06CB:8251.0001/input/input6 U: Uniq= H: Handlers=mouse0 event6 B: PROP=1 B: EV=b B: KEY=e520 3 0 0 0 0 B: ABS=6f38103 -- 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/1708874 Title: Touchpad stops working after a few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1708874/+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 1727733] [NEW] Screen acts strangely when clicking Dash icon
Public bug reported: I'm new to Ubuntu One so I don't really know what info to submit, but my problem is as follows: Everything seems to work just fine in 16.04 - except for one thing: Dash. When I click the icon (or press the superkey) the screen goes sort of crazy: coloured strips and odd stuff appear. Sometimes the computer freezes and I have to start all over again; sometimes it is possible to save the day by (fairly quickly)clicking the Dash icon once again - and sometimes things work out by themselves. I have searched for a solution on the internet, but in vain. Maybe it has something to do with memory mapping? Computer info: AMD Athlon 64 Processor 3500+ with 3 GB RAM (I think it was originally 1 GB but I extended it some years ago) in HP Pavilion 3510no desktop (old stuff; probably at least 10 years old). Graphics Gallium 0.4 on NV 46 (according to Settings - what do I know ...) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 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 Date: Wed Oct 25 14:52:42 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G72 [GeForce 7300 LE] [1043:0346] InstallationDate: Installed on 2017-06-27 (120 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 058f:9360 Alcor Micro Corp. 8-in-1 Media Card Reader Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP Pavilion 061 RA975AA-ABS t3510.se ProcEnviron: LANGUAGE=sv PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic root=UUID=099bfe13-94a1-482f-b3aa-13341d87945d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.11 dmi.board.name: Nash dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.11:bd06/16/2006:svnHPPavilion061:pnRA975AA-ABSt3510.se:pvr0nx0211RE101NASHM00:rvnMSI:rnNash:rvr1.0:cvn:ct3:cvr: dmi.product.name: RA975AA-ABS t3510.se dmi.product.version: 0nx0211RE101NASHM00 dmi.sys.vendor: HP Pavilion 061 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Oct 25 14:43:13 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputTV-1 VGA-1 xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1727733 Title: Screen acts strangely when clicking Dash icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727733/+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 1727742] [NEW] "peek" hangs Wayland display server
Public bug reported: I have "peek" installed from its PPA repository as described at https://github.com/phw/peek#ubuntu . When I attempt to record a GIF with peek under Wayland, it counts down and then my display hangs. I can't even switch VTs, so the only thing I can do at this point is power-cycle my laptop. I know it's just the display hanging, not everything, because the music I'm listening to continues to play. This occurs whether or not I set GDK_BACKEND to x11 before launching peek. Peek works fine when I use it under Xorg instead of Xwayland. See also https://github.com/phw/peek/issues/202 , the bug I filed with the peek developers about this, but regardless of whether peek is doing something wrong, it shouldn't be able to cause the display server to hang. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:09:23 2017 DistUpgraded: 2017-10-20 10:34:09,954 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.10.0-37-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Crystal Well Integrated Graphics Controller [8086:0d26] (rev 08) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Crystal Well Integrated Graphics Controller [1558:7410] InstallationDate: Installed on 2017-05-19 (159 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System76, Inc. Galago UltraPro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- 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/1727742 Title: "peek" hangs Wayland display server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1727742/+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 1727227] Re: error on boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1727227 Title: error on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727227/+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 1727770] [NEW] wayland does not have logic for a Lenovo laptop on the dock
Public bug reported: I have a Lenovo T440s (haswell) and an ultradock with external monitor. If I resume on the dock, wayland seems to recognize the lid as closed and suspends. The work around is to (1) open the lid, bring up the display control tab and switch to single monitor, choose the external one (on the DP); and (3) apply. Then I can close the lid. The laptop will boot correctly on the dock with the lid closed. I tried changing the dconf parameter org.gnome.settings- daemon.plugins.power to 'nothing' but that doesn't seem to matter. Obviously, this is not a critical issue, but it sure is annoying. This should "just work". ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-server0 1.14.0-1 Uname: Linux 4.13.9-041309-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:59:35 2017 Dependencies: gcc-7-base 7.2.0-8ubuntu3 libc6 2.26-0ubuntu2 libffi6 3.2.1-6 libgcc1 1:7.2.0-8ubuntu3 DistUpgraded: 2017-10-20 11:39:46,873 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.13.0-16-generic, x86_64: installed acpi-call, 1.1.0, 4.13.9-041309-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2016-05-06 (537 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20ARA0S100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.9-041309-generic root=UUID=0a196d38-a419-4a42-b659-7108068e6ce5 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 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 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727770 Title: wayland does not have logic for a Lenovo laptop on the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1727770/+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 1727742] Re: "peek" hangs Wayland display server
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Package changed: xorg-server (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1727742 Title: "peek" hangs Wayland display server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727742/+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 1723758] Re: Xorg X11 nouveau video driver for NVIDIA graphics chipsets locks up (hangs)
Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1330355. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-04-26T01:01:05+00:00 John wrote: My machine locks up several times a week. From /var/log/messages I see: Apr 25 16:48:36 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 00040060 Apr 25 16:48:36 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 00140010 Apr 25 16:48:36 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 2001a020 Apr 25 16:48:36 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data ff636880 Apr 25 16:48:36 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 0002 ... Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: Xorg[1248]: failed to idle channel 2 [Xorg[1248]] Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 00040060 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data beef0201 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 00140010 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 2001a020 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data ff636881 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data 0002 Apr 25 16:48:51 jschmitt-dt kernel: nouveau :02:00.0: fifo: CACHE_ERROR - ch 2 [Xorg[1248]] subc 0 mthd data Apr 25 16:49:06 jschmitt-dt kernel: nouveau :02:00.0: Xorg[1248]: failed to idle channel 2 [Xorg[1248]] Sometimes I can still ssh to the machine, other times I cannot. When I can ssh to the machine, I can sometimes use this to bring back the machine to a working state: $ systemctl isolate rescue.target and then $ systemctl isolate graphical.target The only other option I have is to physically reset the machine. $ cat /etc/redhat-release Fedora release 22 (Twenty Two) $ uname -a Linux jschmitt-dt 4.4.6-201.fc22.x86_64 #1 SMP Wed Mar 30 18:30:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 xorg-x11-drv-nouveau-debuginfo-1.0.11-2.fc22.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- nouveau/+bug/1723758/comments/0 On 2016-04-27T00:20:36+00:00 John wrote: Apr 26 16:54:45 jschmitt-dt kernel: nouveau :02:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE] Apr 26 16:54:45 jschmitt-dt kernel: nouveau :02:00.0: gr: 0010 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 08b8 data 00040314 Apr 26 16:54:57 jschmitt-dt audit[14074]: auid=1620 uid=1620 gid=1620 ses=1 pid=14074 comm="chromium-browse" exe="/usr/lib64/chromium-browser/chromium-browser" sig=0 arch=c03e syscall=273 compat=0 ip=0x7fac2cfcd4f4 code=0x5 Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[1253]] get 00200355b4 put 00200355e0 ib_get 0021 ib_put 02dc state 80004244 (err: INVALID_CMD) push 00406040 Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: fifo: DMA_PUSHER - ch 2 [Xorg[1253]] get 002003566c put 0020035698 ib_get 0023 ib_put 02dc state 80004244 (err: INVALID_CMD) push 00406040 Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: 0010 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0234 data 0004488c Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE] Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: 0010 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 023c data 003048b0 Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: DATA_ERROR 0004 [INVALID_VALUE] Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: 0010 [] ch 2 [000fb21000 Xorg[1253]] subc 2 class 502d mthd 0240 data 02f8 Apr 26 16:55:21 jschmitt-dt kernel: nouveau :02:00.0: gr: DATA_ERROR 000c [INVALID_BITFIELD] Apr 26 16:55:21 jschmitt-dt kernel: nouvea
[Ubuntu-x-swat] [Bug 1509434] Re: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin
Launchpad has imported 2 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1259475. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2015-09-02T16:41:48+00:00 Markus wrote: Set KWin to use EGL via KDE System Settings. With Version 2.99.917-6.20150211.fc22 everything works fine, with 2.99.917-15.20150729.fc22 several Plasma widgets (most notably the digital clock) stop updating after a minute or so. Reply at: https://bugs.launchpad.net/fedora/+source/plasma- desktop/+bug/1509434/comments/0 On 2016-07-19T19:56:07+00:00 Fedora wrote: Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/fedora/+source/plasma- desktop/+bug/1509434/comments/9 ** Changed in: plasma-desktop (Fedora) Status: Unknown => Won't Fix ** Changed in: plasma-desktop (Fedora) Importance: Unknown => 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/1509434 Title: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509434/+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 1727790] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 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 #1557346, 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/1727790/+attachment/4996859/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996862/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996872/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996874/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996875/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996876/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1727790/+attachment/4996877/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1557346 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/1727790 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1727790/+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 1557346] Re: Xorg crashed with SIGABRT in OsAbort()
** Tags added: bugpattern-needed -- 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/1557346 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1557346/+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 1509434] [NEW] Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin
You have been subscribed to a public bug: After my upgrade from 15.04 to 15.10 certain Plasma elements don't redraw. This affects the task bar (in the panel), the starter and the desktop at least. So after starting an application it's not shown in the task bar. After adding a favourite it's not shown in the starter and after dropping a file on the desktop it's not shown. For the task bar I found a work around, by selecting the auto hide function. So each time I move to the bottom edge the task bar pops up, gets redrawn and shows the correct open applications. For the starter: after adding a favourite, click the starter icon (closes), then click again (opens with the change shown). For the desktop I could only logoff, then login. Prior to upgrading I had 15.04 with the Kubuntu Backports installed, and had not this issue. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: kubuntu wily -- Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin https://bugs.launchpad.net/bugs/1509434 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg 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 127101] Re: laptop hangs when switching video mode
Launchpad has imported 11 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=244416. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-06-15T15:02:45+00:00 Bryan wrote: Description of problem: When using the Intel experimental video driver on my thinkpad T60 with intel 945 gm, often my system will freeze, and the screen will show a bunch of gray block on a black screen moving around. If I switch to the 810 drivers, I don't have this issue. Version-Release number of selected component (if applicable): xorg-x11-drv-i810-2.0.0-3.fc7 xorg-x11-server-Xorg-1.3.0.0-8.fc How reproducible: not very--this is intermittent. However, it happens usually on logout or system shutdown. Steps to Reproduce: 1. logout or shutdown 2. 3. Actual results: system freezes with lots of gray blocks on a black screen Expected results: successful logout or shutdown Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/4 On 2007-06-15T15:36:27+00:00 Matěj wrote: Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. Could you please also try to run without any /etc/X11/xorg.conf whatsoever and let X11 autodetect your display and video card? Attach to this bug /var/log/Xorg.0.log from this attempt as well, please. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/127101/comments/5 On 2007-06-21T23:14:02+00:00 Bryan wrote: See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243760 for the requested attachments Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/6 On 2007-11-08T21:34:18+00:00 Tomas wrote: Just a note that I'm able to reproduce this in nearly 100 % of cases using the xrandr command as described here: http://bugs.freedesktop.org/show_bug.cgi?id=11525#c0 And it seems they fixed this upstream. I haven't tested it yet, though. (and I'm not running Fedora on this HW, anyway) Should be commit eecd3ccedee6c4acf101591f7e60673660379e62 in master branch of xf86-video-intel. (I wanted to paste a link to gitweb, but gitweb.fd.o seems dead) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/194 On 2008-01-10T22:59:33+00:00 Jesse wrote: Yeah, 9xx should be pretty solid at this point. Please retest when you can and update the bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/201 On 2008-01-14T10:12:39+00:00 Tomas wrote: (as far as I'm concerned, that single patch -- which I applied manually -- fixed all my problems and X+intel have been really solid since) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/202 On 2008-01-18T02:27:54+00:00 Jesse wrote: Tomas, I know this isn't really a Fedora issue at this point since you manually applied the patch, but I wonder if you could test upstream git? I made some changes in this area recently and hopefully things will still work for you. If not, I'd definitely appreciate if you could file a bug at freedesktop.org against the intel driver for the problem. Thanks, Jesse Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/203 On 2008-01-28T15:42:07+00:00 Tomas wrote: I updated to latest git and things seem to work. If they stop, I'll make a note about it :) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/127101/comments/204 On 2008-01-28T17:15:31+00:00 Matěj wrote: I guess, this is not NEEDINFO anymore. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- inte
[Ubuntu-x-swat] [Bug 219353] Re: compiz corruption upon resume
Launchpad has imported 27 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=250677. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-08-02T20:34:48+00:00 David wrote: Description of problem: Desktop effects sometimes has screen corruption coming out of suspend. I will attach an image that illustrates what I mean. Version-Release number of selected component (if applicable): Full 2.6.22.1-41.fc7, all packages up to date as of date of this report. How reproducible: Sometimes, not always. Happens to me sometimes when I suspend at night and then the next morning turn on. Steps to Reproduce: 1. Have desktop effects turned on 2. Suspend 3. Restart Actual results: Sometimes gives results as in the attached picture Expected results: Shouldn't show screen corruption Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/0 On 2007-08-02T20:34:50+00:00 David wrote: Created attachment 160543 screen shot illustrating the screen corruption Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/1 On 2007-08-02T20:36:17+00:00 David wrote: Created attachment 160544 the xorg.conf file - which is completely default Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/2 On 2007-08-02T20:37:14+00:00 David wrote: Created attachment 160545 the Xorg.0.log file Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/3 On 2007-08-02T20:41:55+00:00 David wrote: Created attachment 160546 the /var/log/messages Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/4 On 2007-08-06T22:15:48+00:00 Richard wrote: I have the same problem on my Dell Latitude D610, with ATI Mobility Radeon X300. The bug is 100% repeatable: all window decorations are corrupted when coming out of suspend. My solution is to force them to repaint using Alt+Tab or Ctrl+Alt+Left or some other keystroke that triggers beryl. I can attach confs and logs if needed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/5 On 2007-08-06T22:18:20+00:00 Richard wrote: Created attachment 160775 Corrupt window decorations. Screen shot taken after resuming from suspend, before any interaction with beryl. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/6 On 2007-10-05T22:14:25+00:00 Matěj wrote: *** This bug has been marked as a duplicate of 210602 *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/7 On 2007-10-12T10:07:38+00:00 Matěj wrote: Per https://bugzilla.redhat.com/show_bug.cgi?id=210602#c12 reopening this bug. David, bug 210602 was against Rawhide. Could you please upgrade both your /etc/X11/xorg.conf and /var/log/Xorg.0.log with Rawhide computer? Also could you try please to run X without any /etc/X11/xorg.conf whatsoever? What happens then? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/8 On 2007-10-12T10:10:06+00:00 Matěj wrote: *** Bug 210602 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/linux-restricted- modules-2.6.24/+bug/219353/comments/9 On 2007-10-13T05:31:51+00:00 David wrote: Created attachment 226301 Xorg.0.log I don't have rawhide running here as from what I understand it isn't necessarily stable, and my computer requires stability as I do my work on it. But with kernel 2.6.22.9-91.fc I still see graphical corruption when running X without any /etc/X11/xorg.conf and I have updated the attached Xorg.0.log with that log. I also see https://bugzilla.redhat.com/show_bug.cgi?id=250683 on suspend which is a real pain because every time I come out of suspend I have to unplug and re-plug my
[Ubuntu-x-swat] [Bug 108527] Re: X freezes when compiz is enabled on ATI X300
Launchpad has imported 33 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=219632. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-12-14T15:38:14+00:00 Ed wrote: Description of problem: After enabling "desktop effects", display experiences random lockups during display of said effects, and occasionally compiz will fail to start upon login. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.6.3-1.fc6 How reproducible: Just about every time. Steps to Reproduce: 1. Buy a Lenovo ThinkPad T43p (http://www.thinkwiki.org/wiki/Category:T43p for hardware specifications, I have the 15" 1600x1200 TFT). 2. Enable desktop effects using the xorg radeon driver. 3. Use desktop for a while, possibly log out and back in again. Actual results: On login, compiz will *sometimes* fail to start; disabling and then re-enabling desktop effects fixes this. However, after several minutes to several hours of use, the desktop will eventually hang (always in the middle of displaying a fade, wobble, or other effect). Expected results: The same stability I got out of the non-AIGLX desktop. ;-) This was actually a very stable setup prior to trying out AIGLX, with both the radeon driver and with fglrx. Additional info: Here's the lspci info for my video card (I'll attach the full lspci output in a moment, along with the xorg.conf I'm using and a relevant Xorg.0.log): 01:00.0 VGA compatible controller: ATI Technologies Inc M24 1T [FireGL M24 GL] (rev 80) (prog-if 00 [VGA]) Subsystem: IBM Unknown device 0570 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/0 On 2006-12-14T15:38:15+00:00 Ed wrote: Created attachment 143639 xorg.conf Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/1 On 2006-12-14T15:39:14+00:00 Ed wrote: Created attachment 143640 Xorg.0.log Log from a typical session that freezes. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/2 On 2006-12-14T15:39:33+00:00 Ed wrote: Created attachment 143641 lspci -vvv output Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/3 On 2006-12-14T15:40:31+00:00 Ed wrote: Also note that the system itself does not freeze; only the display. When this happens, I'm able to ssh back into the laptop from another machine and "gracefully" shut things down, but the screen never returns to normal until the system is rebooted. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/4 On 2007-01-09T22:53:46+00:00 Christopher wrote: Created attachment 145205 lspci -vvv output Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/5 On 2007-01-09T22:54:31+00:00 Christopher wrote: Created attachment 145206 xorg.conf file Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/6 On 2007-01-09T22:55:07+00:00 Christopher wrote: Created attachment 145207 Log from aiglx enabled sessions Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/7 On 2007-01-09T22:57:47+00:00 Christopher wrote: I see this also. This on a Thinkpad T42. See above attachments. Workaround is obviously to disable desktop effects however given that it took me a while to find the (probable) cause I would ask this to be re-prioritised upwards as there is likely to be a number of folks who are banging their heads into walls/screens on this one. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/108527/comments/8 On 2007-01-23T21:00:01+00:00 Christopher wrote: Edward, Could you please test with the latest flash plugin (ie. 9 final) as I believe this to be the source of our problems. Regards Chris Reply at:
[Ubuntu-x-swat] [Bug 27724] Re: Touchpads should be unaffected by left handed mouse option
Launchpad has imported 29 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=324721. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-10-09T11:44:32+00:00 David wrote: Description of problem: If you change the mouse preferences to left handed, this SHOULD NOT change the functionality of a tap on a laptop's touchpad, which should still function as the primary mouse button click. But on f7, switching to use a left-handed mouse changes the touchpad touch functionality to be the reverse of what you'd expect. This is annoying and frustrating to left-handed users. >From dmesg: input: PS/2 Mouse as /class/input/input1 input: AlpsPS/2 ALPS GlidePoint as /class/input/input2 input: AT Translated Set 2 keyboard as /class/input/input3 Versions: Kernel 2.6.22.9-91.fc7 nautilus-2.18.3-1.fc7 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/27724/comments/7 On 2007-10-10T23:08:41+00:00 Matěj wrote: Being a left-handed myself, I would ask just one question -- why do you use left-handed mouse settings with touchpad? It doesn't make any sense to me. Do you use both mouse and touchpad in the same time? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/27724/comments/8 On 2007-10-10T23:28:31+00:00 David wrote: I normally use an external mouse when my notebook is at home but if I decide to use the touchpad or take the computer somewhere where I need to use it because I don't have the mouse, then I shouldn't need to go into the settings to switch it back to right handedthat becomes very annoying after 100 or so times of using the notebook at home and then using it elsewhere, having to switch it. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/27724/comments/9 On 2008-05-14T14:40:58+00:00 Bug wrote: This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists. Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs: http://docs.fedoraproject.org/release-notes/ The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/27724/comments/10 On 2008-07-15T05:35:49+00:00 Peter wrote: This isn't really a mouse driver bug, it's a conceptual issue with the X server's event processing. Problem being that the SetPointerMapping request by default changes the core pointer device. Up to X11R7.4, any core event, no matter who actually generates it, comes from the core pointer and thus assumes the core pointer's mapping (which in your case is left-handed). This problem is fixed in Xorg git, but needs a vastly different input system. It also requires configuration tools to set the button mapping per device, and not just for the core pointer. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/27724/comments/11 On 2008-07-15T07:41:26+00:00 Peter wrote: Did some more research, fix is possible for F9. X.Org Bug 11683 [1] changed the mapping behaviour to take the device's butt
[Ubuntu-x-swat] [Bug 1509434] Re: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin
EOL release, no debug info, and no response for year+. ** Changed in: xorg (Ubuntu) Status: Incomplete => Invalid ** No longer affects: xorg (Ubuntu) ** Package changed: plasma-desktop (Fedora) => xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Importance: Medium => Undecided ** Changed in: xorg (Ubuntu) Status: Won't Fix => New ** Changed in: xorg (Ubuntu) Remote watch: Red Hat Bugzilla #1259475 => None ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1509434 Title: Kubuntu panel, starter, desktop do not redraw on change using EGL in kwin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509434/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
Hey Daniel, When I run 'sudo evtest' my touchpad is listed as "ELAN1200:00 04F3:303E Touchpad", but when I try to test it, not input is read like it would be for something like my keyboard or any other device. I placed this bug under libinput since this bug was not present in Ubuntu 17.04 which did not use Gnome Wayland as its default compositor. Mind you, 17.04 wasn't exactly great for using the touchpad to begin with as it would occasionally cut out altogether and become as useless as it is not until a restart but at least I would be able to use it again after the restart. Since my upgrade to 17.10, and the reinstall that followed when the upgrade didn't work, I have not been able to use my touchpad at all, hence I believe it has to do with the input system on Wayland. My touchpad also does not work in separate VT logins. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1726934/+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 1726595] [NEW] Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
You have been subscribed to a public bug: OBSERVED BEHAVIOR: Matlab stays in busy state when using some functions like "plot" or even "exit", while executing through a ssh tunnel with X11 forwarding. REPRODUCE THE BUG: You need matlab (my version is R2017a) to reproduce the bug. I suspect any version >= 2014b would reproduce the bug (HG2 framework), and maybe any version. 1. Connect to self (or from other machine) with X forwarding: $ ssh -X user@localhost 2. Launch matlab $ matlab & 3. Plot something >> plot(1,1) ADDITIONAL INFORMATION - Normal behavior would be appearance of a new window and a single point at position (1,1). - No ressources seem to be used. - Opening a figure alone is possible. (>> figure). Opening other windows from the graphical user interface is possible - Opening Matlab without the java machine seems to work, but matlab relies heavily on java. At least "exit" which doesn't work with java, works without java. - Providing Matlab with open-jdk version 1.8.0_144 didn't change anything. - This used to work perfectly for as long as I have been using Ubuntu (since 2012). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: openssh-client 1:7.5p1-10 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 23 17:44:23 2017 ExecutablePath: /usr/bin/ssh InstallationDate: Installed on 2017-08-25 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago) modified.conffile..etc.ssh.ssh_config: [modified] mtime.conffile..etc.ssh.ssh_config: 2017-10-23T16:25:50.569560 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 https://bugs.launchpad.net/bugs/1726595 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland 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 111257] Re: totem crashes with 'BadAlloc (insufficient resources for operation)' when using compiz and xserver-xorg-video-intel driver
Launchpad has imported 68 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=239125. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-05-05T05:09:13+00:00 Jens wrote: Description of problem: Totem immediately crashes under Compiz when playing back movie files of any type (avi, mpeg, mov, ogg, etc) Error on the command line is as follows: The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 57 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Version-Release number of selected component (if applicable): totem-2.18.1-3.fc7 How reproducible: 100% Steps to Reproduce: 1. Open *any* movie file, any format 2. Watch Totem croak Additional info: Under Metacity, everything plays fine. Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/111257/comments/6 On 2007-05-06T13:24:02+00:00 Bastien wrote: Works here. Could you please run "totem --sync", and reproduce the problem as described in the error message? Make sure you install the relevant -debuginfo packages so that the backtrace has debugging information. Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/111257/comments/7 On 2007-05-06T20:28:26+00:00 Jens wrote: Trying to watch this: http://www.redhat.com/v/ogg/060407_CDadapco.ogg $ totem --sync 060407_CDadapco.ogg The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 51 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Then I tried just opening totem with "totem --sync" and opening the file from the File --> Open menu item, and got: $ totem --sync ((( opened file with File --> Open ))) The program 'totem' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 48 error_code 11 request_code 140 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/111257/comments/8 On 2007-05-06T20:29:18+00:00 Jens wrote: Oh, and yes, all the debuginfo packages are installed. Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/111257/comments/9 On 2007-05-08T09:11:07+00:00 Bastien wrote: You need to run it under gdb, and break on gdk_x_error(), as per the error message. Reply at: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/111257/comments/10 On 2007-05-08T17:22:42+00:00 Jens wrote: sorry - I'm not very familiar with gdb... I tried anyhow, and the session looked like the following: $gdb (gdb) file /usr/bin/totem Reading symbols from /usr/bin/totem...Reading symbols from /usr/lib/debug/usr/bin/totem.debug...done. Using host libthread_db library "/lib/libthread_db.so.1". done. (gdb) break gdk_x_error Breakpoint 1 at 0x453d83: file gdkmain-x11.c, line 614. (gdb) run --sync Starting program: /usr/bin/totem --sync Error in re-setting breakpoint 1: No source file named gdkmain-x11.c. (the above gets printed about 15 times...) [Thread debugging using libthread_db enabled] [New Thread -1208166688 (LWP 5364)] [New Thread -1223857264 (LWP 5366)] [New Thread -1234347120 (LWP 5367)] [New Thread -1249436784 (LWP 5368)] [New Thread 27011984 (LWP 5369)
[Ubuntu-x-swat] [Bug 144322] Re: interlacing broken in gutsy on radeon/ati open source driver
Launchpad has imported 8 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=437700. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-03-16T17:53:33+00:00 Andy wrote: Description of problem: After upgrading from F7 to F8 my 50Hz PAL RGB interlace mode was broken (similar problems also noted in ubuntu bugzilla and xorg bugzilla) the actual output was the even rows of top half of the screen, followed a spurious vsync pulse halfway down the screen, followed by the even rows of the top half of the screen. Version-Release number of selected component (if applicable): xorg-x11-drv-ati-6.8.0-1.fc8 How reproducible: 100% After if some delving into the CRTC register values I decided to try doubling the vertical values, this seems to work nicely, I've made it conditional on the interlace flag, probably similar fix needed for CRTC2. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/144322/comments/54 On 2008-03-16T17:53:33+00:00 Andy wrote: Created attachment 298199 Fix CRTC vtotal/vdisplay/vsyncstart registers for interlace Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/144322/comments/55 On 2008-03-19T13:12:48+00:00 DualIP wrote: I'm glad finally a coder looks into this, and patched code surfaces. Although the recent posted patch will work for most users, imho it's not a proper patch. Over here I didn't use git,but applied the patch to 6.8.0 source. On my radeon7000 setup, the patch works fine when starting xorg into this mode: Modeline "PALWS" 24.75 1280 1321 1437 1584 576 580 585 625 -hsync -vsync interlace However I do have an additional PAL modeline in xorg.conf: Modeline "PAL" 22.50 1152 1195 1301 1440 576 580 583 625 -hsync -vsync interlace Using xrandr to switch from using the 1st modeline to 2nd gives wrong PAL output! The screen OSD reads 15k-below30Hz, where it should shoud 15k-50Hz. This mode suggest Vregisters are set to twice required value It seems to me that somewhere a bug is introduced after V6.6.3, that somehow halves the Vregister settings on interlace mode. On my radeon 7000, this bug only shows up when starting an interlaced mode, not after switching from an interlaced mode to another interlaced mode. (that was my workaround, start interlaced, then jump to another interlaced mode) "Hey, this pipe line is leaking half of the oil!" "Then start pumping twice as much to get the required output." Obvious that'll give required output , but (as environmentalists will agree) isn't the way to fix it ;-) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/144322/comments/71 On 2008-03-19T14:05:30+00:00 Andy wrote: (In reply to comment #2) > imho it's not a proper patch. Heh, I won't disagree with you :-) I needed a fix that works for me, and I thought others might benefit, someone who knows the driver might fix it in a far better way. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/144322/comments/72 On 2008-11-26T10:10:50+00:00 Bug wrote: This message is a reminder that Fedora 8 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 8. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '8'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 8's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 8 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.laun
[Ubuntu-x-swat] [Bug 90587] Re: [VM800]via unichrome pro (0x1106, 0x3344) unsupported
Launchpad has imported 16 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=389011. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2007-11-18T01:00:15+00:00 Dave wrote: Description of problem: VIA UniChrome Pro IGP on board graphics is not detected correctly and xorg fails if the via driver is selected. The vesa driver works. Version-Release number of selected component (if applicable): xorg-x11-drv-via-0.2.2-4.fc8 How reproducible: Every time. Steps to Reproduce: 1. Install F8 2. Check to see what xorg.conf driver is set to (it will be vesa) 3. Shutdown X, Change driver to via, start X Actual results: X will fail to start Expected results: X should start Additional info: lspci -vvv info 01:00.0 VGA compatible controller: VIA Technologies, Inc. UniChrome Pro IGP (rev 01) (prog-if 00 [VGA]) Subsystem: VIA Technologies, Inc. UniChrome Pro IGP Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/7 On 2007-11-18T01:00:15+00:00 Dave wrote: Created attachment 262621 xorg.conf used with via set as driver Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/8 On 2007-11-18T01:02:19+00:00 Dave wrote: Created attachment 262631 xorg log file when display set to via Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/9 On 2007-11-18T01:11:10+00:00 Dave wrote: Here is the Smolt profile, incase it's of any help: http://smolt.fedoraproject.org/show?UUID=5efb271a-504d-4e82-91ee-3eb5337f9a75 Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/10 On 2007-11-28T16:10:42+00:00 Adam wrote: Mass migration: via -> openchrome. Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/11 On 2007-11-28T21:44:56+00:00 Xavier wrote: Please retry with xorg-x11-drv-openchrome. This is the successor to xorg-x11-drv-via. Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/12 On 2007-12-02T10:21:29+00:00 Dave wrote: Created attachment 275001 xorg.log file from openchrome driver This does indeed manage to bring up an X display on the machine. I'm unsure as to what performance I should expect with this driver, but it seems to be a little sluggish. Also when X starts, there are what seems to be a number of false starts before the display settles... i.e. X display starts to appear, then back to console, then back to the X "watch" in the center of the screen before finally the GDM login screen redraws. Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/13 On 2007-12-02T10:22:25+00:00 Dave wrote: Created attachment 275011 xorg.conf file with openchrome driver Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/14 On 2007-12-04T22:14:18+00:00 Matěj wrote: Could we get /var/log/Xorg.0.log as well, please? Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/15 On 2008-01-21T15:38:55+00:00 Matěj wrote: Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/discover- data/+bug/90587/comments/16 On 2008-02-09T09:48:43+00:00 Martin wrote: I had a similar problem with my laptop six months ago. I did a bit of googling around and found (might have been on a Ubuntu forum) that a manual edit to xorg.conf was needed. Here is the relevant section: Section "Device" Identifier "Videocard0" Driver "via" BusID "PCI:1:0:0" Option "EnableAGPDMA" "true" VendorName "Videocard vendor" BoardName "VIA Technologies, Inc. S3 Unichro
[Ubuntu-x-swat] [Bug 213191] Re: [i855GME] system freezes when switching to external monitor
Launchpad has imported 7 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=441192. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-04-07T04:07:20+00:00 Jeff wrote: >From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.13) Gecko/20080325 Ubuntu/7.10 (gutsy) Firefox/2.0.0.13 Description of problem: Fedora 9 beta w/updates. Panasonic CF-51 with 855GME integrated video. If I use the Fn+F3 display switch without an external monitor connected the system usually freezes. No log messages, no magic SysReq, no remote ssh, no LED toggling, no messages on serial console - just a black screen with a frozen mouse cursor. It doesn't matter if the monitor was connected when X was started. Even with it connected the switch doesn't seem to have any effect on display switching as the view is cloned regardless. There is only a small display flicker when the switch is actuated to indicated that anything happened (unless it decides to freeze). I tried switching to the i810 driver but it can't find any devices. The vesa driver works and switches correctly with the external monitor connected and doesn't misbehave if it's not. Version-Release number of selected component (if applicable): xorg-x11-drv-i810-2.2.1-19.fc9.i386 How reproducible: Always Steps to Reproduce: 1.Login to desktop with intel driver enabled. 2.Disconnect external monitor. 3.Attempt to switch to external monitor. Actual Results: Black screen with mouse cursor, system freeze. Expected Results: Either not switch or black out and return after subsequent key actuation. Additional info: A similar bug exists in Ubuntu Hardy 8.04 beta with a Toshiba M35X-S114 using the same chipset: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/213191 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/3 On 2008-04-07T04:09:44+00:00 Jeff wrote: Created attachment 301459 lspci -vvnn Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/5 On 2008-04-07T04:10:21+00:00 Jeff wrote: Created attachment 301460 dmesg Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/6 On 2008-04-07T04:11:50+00:00 Jeff wrote: Created attachment 301461 General log not specific to occurance of problem Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/7 On 2008-05-14T09:00:12+00:00 Bug wrote: Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/11 On 2009-06-10T00:01:45+00:00 Bug wrote: This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/213191/comments/17 On 2009-07-14T17:3
[Ubuntu-x-swat] [Bug 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
Interesting: Exception in thread "AWT-EventQueue-1" com.jogamp.opengl.GLException: Caught GLException: AWT-EventQueue-1: createImpl ARB n/a but required, profile > GL2 requested (OpenGL >= 3.1). Requested: GLProfile[GL3bc/GL3bc.sw], current: 3.0 (Compat profile, compat[ES2], FBO, software) - 3.0 Mesa 17.2.2 So something to do with opengl over remote X11 connections. I'll switch the bug over to wayland, and maybe add a xorg task ** Package changed: openssh (Ubuntu) => wayland (Ubuntu) ** Changed in: wayland (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1726595/+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 1715479] Re: Touchpad won't stay disabled after resuming from suspend
Launchpad has imported 37 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1448962. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-05-08T21:25:01+00:00 Matt wrote: laptop: Lenovo T460P O/S: fedora 25, fully updated BIOS setting: Touchpad: off // already filed a bug with Lenovo as a BIOS error gnome-control-center mouse: Touchpad: off # libinput-debug-events -event2 DEVICE_ADDED Power Button seat0 default group1 cap:k -event7 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event6 DEVICE_ADDED Video Bus seat0 default group2 cap:k -event1 DEVICE_ADDED Sleep Button seat0 default group3 cap:k -event4 DEVICE_ADDED Yubico Yubico Yubikey II seat0 default group4 cap:k -event10 DEVICE_ADDED Integrated Camera seat0 default group5 cap:k -event3 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group6 cap:k -event5 DEVICE_ADDED SynPS/2 Synaptics TouchPadseat0 default group7 cap:pg size 100x58mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on -event8 DEVICE_ADDED TPPS/2 IBM TrackPoint seat0 default group8 cap:p left scroll-nat scroll-button -event9 DEVICE_ADDED ThinkPad Extra Buttonsseat0 default group9 cap:k -event5 POINTER_AXIS +2.79s vert 3.14* horiz 0.00 (finger) event5 GESTURE_SWIPE_BEGIN +4.04s 3 event5 GESTURE_SWIPE_UPDATE +4.04s 3 0.00/ 1.87 ( 0.00/15.75 unaccelerated) I'm assuming that when I touch the touchpad, this should NOT happen. There is a bigger picture here and that is when my palm rests too heavy on the touchpad, it messes with the clicking of my mouse. I'll grab tabs and scroll bars and won't let go until I click on them again. I can reproduce this by putting 3 fingers on the touchpad and clicking on a scoll bar or tab and it will start messing up in short order. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1715479/comments/0 On 2017-05-09T02:42:33+00:00 Peter wrote: libinput-debug-events is unrelated to the gnome session, it creates a new context and the gnome settings have no effect on it. is this in an X session? If so, what does xinput list-props "SynPS/2 Synaptics TouchPad" show after disabling the touchpad in gnome? for the palm issues, etc. please file a separate bug, thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1715479/comments/1 On 2017-05-09T12:45:38+00:00 Matt wrote: Yes, this in an X session. $ xinput list-props "SynPS/2 Synaptics TouchPad" unable to find device SynPS/2 Synaptics TouchPad will be filing seperate bug for other issues. thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1715479/comments/2 On 2017-05-09T22:48:56+00:00 Peter wrote: run xinput list to find the device name, I wonder if I mistyped anything. then substitute the device name with the one for the touchpad. if you see devices like "wayland pointer" etc, then you're under wayland, in which case the xinput approach won't work. log out and back in as Gnome on Xorg on the user's login screen (click the gear icon), then see if you can reproduce it there. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1715479/comments/3 On 2017-05-10T00:25:51+00:00 Matt wrote: $ loginctl SESSIONUID USER SEAT c1 42 gdm seat0 2 1000 username seat0 $ loginctl show-session 2 -p Type Type=x11 $ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Logitech Logitech USB Optical Mouse id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)]
[Ubuntu-x-swat] [Bug 353208] Re: [PM800] Panel on PM800 is not supported.
Launchpad has imported 31 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=450845. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-06-11T10:35:15+00:00 Valent wrote: Description of problem: On GDM screen and in GNOME laptop has wrong resolution detected (see the attachement). After setting resolution in "System / Preferences / Hardware / Screen Resolution" then in Gnome after login I see the correct resolution but still on each GDM I see that the correct resolution is not detected (look at the attachement). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/0 On 2008-06-11T10:36:15+00:00 Valent wrote: Created attachment 308916 gdm screen gdm login with wrong resolution set. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/1 On 2008-06-11T10:47:15+00:00 Xavier wrote: Rather than a screenshot, I'd like to have the xorg conf and xorg log, please. This can probably be worked around by setting the correct resolution in the xorg conf. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/2 On 2008-06-12T13:05:18+00:00 Valent wrote: Created attachment 309066 xorg.conf Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/3 On 2008-06-12T13:05:50+00:00 Valent wrote: Created attachment 309067 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/4 On 2008-06-12T23:25:49+00:00 Xavier wrote: As a workaround, in the Display SubSection of your xorg.conf, add the following line : Modes"1024x768" I'm afraid there's not much that can be done for this bug until some development around the panel code happen upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/5 On 2008-06-13T08:15:02+00:00 Valent wrote: Sorry for my ignorance, but what do you mean by "upstream panel code"? Do you mean that I should report this bug to upstream unichrome project? X11? Or something else. Cheers, Valent. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/6 On 2008-06-13T09:06:02+00:00 Xavier wrote: Sorry for not being clear. Upstream is currently working on improving the panel code. This code is not completely stable yet, but I hope it will be in the coming weeks. I'm following openchrome development very closely and the new code will be in Rawhide soon after it is in openchrome subversion repository. Actually, there is already a pre-version of this code in Rawhide, but I can't promise it'll work. For the time being, the only possible solution to your problem is probably to work around it. One other possible workaround could be to use Option "PanelSize" "1024x768" in the Device section of xorg.conf, with or without Modes "1024x768" in the Display SubSection. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/7 On 2008-06-13T09:52:50+00:00 Valent wrote: Oh, thank you. I can live with this bug and if you need I can test the new openchorome driver code if it will be pushed into Fedora 9 testing-updates repo. Just tell me if you would find my feedback helpful or if you got everything under control :) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/8 On 2008-06-30T23:26:18+00:00 Xavier wrote: Valent, can you please give the latest rawhide package a try ? xorg-x11-drv-openchrome-0.2.902-8.fc10 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/353208/comments/9 On 2008-08-11T16:17:11+00:00 Valent wrote: ok, I'll try it... Reply
[Ubuntu-x-swat] [Bug 1727877] [NEW] AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
Public bug reported: This is a new laptop HP 15-BS576TX which has Intel HD 620 Integrated graphics and a 2GB AMD Radeon 520 Graphics card running on Ubuntu wayland session. Intel integrated graphics is only listed, if you check gnome-control-centre details page (See attached images). But, if I run [code]DRI_PRIME=1 gnome-control-centre[/code] to reach details info it shows "AMD HAINAN" as the only card available. So, it seems the Xwayland session not automatically managing hybrid graphics (shifts to dedicated card for resource hungry apps). What I expected is Gnome control centre will list both the cards. tl;dr: AMD/Intel hybrid graphics not configured correctly in wayland. Dedicated Card is not showing up in system informations. Here are the details: lspci -knnn shows that AMD Radeon 520 card is detected: 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1002:6660] (rev 83) Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] Kernel driver in use: radeon Kernel modules: radeon, amdgpu and Integrated Intel HD 620 graphics: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Kernel driver in use: i915 Kernel modules: i915 lshw -C video *-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:128 memory:b000-b0ff memory:a000-afff ioport:6000(size=64) memory:c-d *-display description: Display controller product: Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 83 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:129 memory:9000-9fff memory:b120-b123 ioport:5000(size=256) memory:b124-b125 Now, if I run any app with DRI_PRIME=1 it works and shows below info: :~$ DRI_PRIME=1 glxinfo |grep -i Opengl* OpenGL vendor string: X.Org OpenGL renderer string: AMD HAINAN (DRM 2.50.0 / 4.13.0-16-generic, LLVM 5.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.2 OpenGL core profile shading language version string: 4.50 So, I assumed Radeon 520 is working fine. Then, noticed that there is no mention of gallium 3d? I see that there is amdgpu driver module also loaded. From the list, R520 card seems to be supported by the radeon driver. lsmod |grep radeon radeon 1470464 0 ttm94208 2 amdgpu,radeon i2c_algo_bit 16384 3 amdgpu,radeon,i915 drm_kms_helper167936 3 amdgpu,radeon,i915 drm 356352 28 amdgpu,radeon,i915,ttm,drm_kms_helper ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Fri Oct 27 03:50:59 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:832b] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430] [103c:832b] InstallationDate: Installed on 2017-10-22 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: HP HP Laptop 15-bs0xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=50b901ea-f329-4a72-ae11-f7203ae53c2e ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.38 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd07/24/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.38:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N
[Ubuntu-x-swat] [Bug 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
** Also affects: xorg-server 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/1727877 Title: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1727877/+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 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
The FPS I get with AMD R 520 card seems to be very low, if I run glxgears when compared to Intel Integrated graphics: -HP-Laptop-15-bs0xx:~$ vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 40135 frames in 5.0 seconds = 8026.788 FPS 41018 frames in 5.0 seconds = 8203.442 FPS 40897 frames in 5.0 seconds = 8179.312 FPS 40758 frames in 5.0 seconds = 8151.432 FPS With Radeon card, seems to be very slow. vblank_mode=0 also results in horizontal lines in glxgears. HP-Laptop-15-bs0xx:~$ DRI_PRIME=1 vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 13545 frames in 5.0 seconds = 2708.850 FPS 13765 frames in 5.0 seconds = 2752.917 FPS 13785 frames in 5.0 seconds = 2756.820 FPS 13785 frames in 5.0 seconds = 2756.957 FPS Is there something I can do to enable full potential of the dedicated card? -- 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/1727877 Title: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1727877/+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 1433329] Re: Xorg without root rights
Launchpad has imported 27 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1078902. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2014-03-20T14:02:17+00:00 Jaroslav wrote: This is a tracking bug for Change: Xorg without root rights For more details, see: http://fedoraproject.org//wiki/Changes/XorgWithoutRootRights The Xorg xserver is a large piece of software which currently runs as root, making it a potential vector for attacks against the system. With recent changes made to systemd-logind it is possible for the xserver to let systemd-logind do device management for it, at which point the xserver will no longer need root rights. Initially this will likely be implemented as the xserver dropping root rights early on. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/0 On 2014-07-04T10:43:34+00:00 Jaroslav wrote: This message is a reminder that Fedora 21 Accepted Changes Freeze Deadline is on 2014-07-08 [1]. At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Freeze. This bug should be set to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon. In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you. [1] https://fedoraproject.org/wiki/Releases/21/Schedule Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/1 On 2014-07-04T10:47:22+00:00 Hans wrote: Hi, Not sure what to do with this bug, all the necessary Xorg bits have long landed, but the only way to run the Xserver as non-root atm is through startx from a text console, as all the display-managers are not ready yet. It might be best to move this to F-22 from a feature pov. Regards, Hans Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/2 On 2014-07-04T11:04:37+00:00 Jaroslav wrote: Hi, thank you for reply. From a feature and (probably even more) from users pov, it makes sense to move it to Fedora 22. I'll make sure all places are correctly updated to reflect it. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/3 On 2014-07-04T13:28:02+00:00 Andrew wrote: Is it possible to leave it for F-21 with startx only? I know I'm a minority here, but that's the way I use. Being done this way it might help to test Xorg in this mode before enabling it for a broader audience. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/4 On 2014-07-04T13:39:13+00:00 Hans wrote: (In reply to Andrew Travneff from comment #4) > Is it possible to leave it for F-21 with startx only? I know I'm a minority > here, but that's the way I use. Being done this way it might help to test > Xorg in this mode before enabling it for a broader audience. For use with startx it requires a tiny bit of manual configuration (because otherwise various dm-s would be broken), see: http://hansdegoede.livejournal.com/14446.html Other then that all the necessary functionality is there, and there is no intention to remove it. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/5 On 2014-07-04T14:22:12+00:00 Andrew wrote: Wow, thanks! Just in case, is it planned to make the same thing available for F-20? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/6 On 2014-07-04T15:25:15+00:00 Hans wrote: (In reply to Andrew Travneff from comment #6) > Wow, thanks! Just in case, is it planned to make the same thing available > for F-20? No. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/comments/7 On 2014-10-20T15:17:12+00:00 Petr wrote: Change moved to F22, so I'm setting the relnotes flag to - for F21. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1433329/com
[Ubuntu-x-swat] [Bug 369333] Re: [CX700] only low resolution allowed and the mouse pointer not appear
Launchpad has imported 14 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=475896. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-12-10T23:06:38+00:00 Milan wrote: Created attachment 326555 Xorg.log from IBM P260 that can do 1280x1024@75 (no xorg.conf) It seems that openchrome stuck on LCD's resolution even I have external CRT connected and LCD on my notebook is off (by driver). I had no luck with xorg.conf fiddling. The situation is the same even no xorg.conf in place. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/0 On 2008-12-10T23:12:32+00:00 Milan wrote: I have: VIA Technologies, Inc. VT8378 [S3 UniChrome] Integrated Video (rev 01) 01:00.0 0300: 1106:7205 (rev 01) (prog-if 00 [VGA controller]) Subsystem: 1025:0033 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- The notebook is Acer Aspire 1350. I've got 1024x768@60. I was able to run higher resolution with older drivers. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/1 On 2008-12-10T23:28:40+00:00 Milan wrote: xorg-x11-drv-openchrome-0.2.903-1.fc10.i386 (no updates yet in repo). Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/2 On 2008-12-11T00:03:21+00:00 Milan wrote: To be more precise and accurate - I've got only 1024x768@60 on external CRT. My notebook can do on its own LCD 1024x768. My IBM P260 CRT can do 1280x1024@85 in MS Windows but in Linux 1024x768@60 only. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/3 On 2008-12-11T21:41:14+00:00 Xavier wrote: >From the log, the driver is activating both the LCD and the CRT. openchrome is >currently not dual head capable, so it uses the same resolution on the 2 >outputs, the lower common denominator wins. You can disable the LCD panel by >adding the following line to the Device section of your xorg conf : Option "ActiveDevice" "CRT" Lemme know if it helps. Regards, Xavier Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/4 On 2008-12-12T06:44:03+00:00 Milan wrote: Yes, ActiveDevice works with my CRT. Thank you. But without ActiveDevice the situation differ: 1) with CRT (IBM P260) - CRT is active, all is visible and Ok - LCD is Off 2) with Dell data projector - nothing is shown on both output devices Should I try some experimental patches or builds or do some testing? Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/5 On 2008-12-22T07:43:57+00:00 Milan wrote: Logged as http://www.openchrome.org/trac/ticket/271 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/6 On 2009-01-06T13:16:49+00:00 Jóhann wrote: Could you update to the latest version, retest and report back to see if this still remains an issue for you. You can get the latest update from here. http://koji.fedoraproject.org/koji/packageinfo?packageID=5229 Thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/7 On 2009-01-06T15:58:18+00:00 Xavier wrote: There's no way to "fix" this bug until openchrome grows dual head support. Currently, there's no way to have a different resolution and refresh rate on different output, the lower one will apply to both output. See comment #4. Hopefully, dual head support shouldn't be too far away, I'll make sure to update both the rawhide package and the F10 testing package as soon as it enters upstream. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- openchrome/+bug/369333/comments/8 On 2009-06-02T09:31:22+00:00 Bartosz wrote: In the Ubuntu this error also exist. But in Ubuntu case, also mouse cursor is not visible on the
[Ubuntu-x-swat] [Bug 319363] Re: [G100] DDC takes so long (to fail) that gdm times out on a slow computer
** Changed in: xorg (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-mga in Ubuntu. https://bugs.launchpad.net/bugs/319363 Title: [G100] DDC takes so long (to fail) that gdm times out on a slow computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-mga/+bug/319363/+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 549447] Re: eGalax touchscreen configured as tablet
Launchpad has imported 61 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=473144. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-11-26T19:15:15+00:00 Jurgen wrote: Created attachment 324781 dmesg output with detected USB touchscreen Description of problem: USB touchscreen driver/pen is not automatically added/usable Version-Release number of selected component (if applicable): xorg-x11-drv-evdev-2.07-3.fc10.i386 How reproducible: Always Steps to Reproduce: 1. Boot system into X 2. Try using the pen 3. Actual results: Pen / touchscreen not usable Expected results: Pen / touchscreen automatically configured and usable Additional info: The proper usb device is detected by the kernel (see also attached dmesg output) but not used by X. usb 4-2: new full speed USB device using uhci_hcd and address 2 usb 4-2: configuration #1 chosen from 1 choice usb 4-2: New USB device found, idVendor=0eef, idProduct=0001 usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 4-2: Product: USB TouchController usb 4-2: Manufacturer: eGalax Inc. input: eGalax Inc. USB TouchController as /devices/pci:00/:00:1d.2/usb4/4-2/4-2:1.0/input/input7 input,hiddev96,hidraw2: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-:00:1d.2-2 Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/0 On 2008-11-26T19:16:16+00:00 Jurgen wrote: Created attachment 324782 Xorg.0.log Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/1 On 2008-12-15T23:20:02+00:00 Peter wrote: Please attach the output of lshal. I'm pretty sure this is an issue with the kernel or hal not providing the right capability lists. Please download http://people.freedesktop.org/~whot/evtest.c, compile it with "gcc -o evtest evtest.c" and then run it as root with "./evtest /dev/input/eventX" where X is the number for the device. You can get the number by looking at /proc/bus/input/devices. Then attach the output of evtest here. Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/2 On 2008-12-16T16:55:03+00:00 Jurgen wrote: Created attachment 327132 Output of evtest /dev/input/event7 Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/3 On 2008-12-16T16:55:39+00:00 Jurgen wrote: Created attachment 327133 Output from lshal Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/4 On 2008-12-16T16:56:15+00:00 Jurgen wrote: Created attachment 327134 Output from cat /proc/bus/input/devices Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/5 On 2008-12-16T16:57:24+00:00 Jurgen wrote: I've attached the requested info. Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/6 On 2008-12-17T04:26:15+00:00 Peter wrote: This is actually a HAL issue (two separate ones). Please try the packages from http://koji.fedoraproject.org/scratch/whot/task_1002708/ and let me know how it goes. If it doesn't work, please attach the output from lshal again. Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/7 On 2008-12-18T17:47:36+00:00 Jurgen wrote: Created attachment 327343 lshal output from updated hal Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/8 On 2008-12-18T17:48:13+00:00 Jurgen wrote: Created attachment 327344 Xorg.0.log with updated hal Reply at: https://bugs.launchpad.net/fedora/+source/xserver-xorg-input- evdev/+bug/549447/comments/9 On 2008-12-18T17:51:53+00:00 Jurgen wrote: I've installed the updated hal packages from koji. The last lines from the Xorg.0.log file show that the proper touch device is found, unfortunately the touchscreen still does not work. Excerpt from Xorg.0.log: (**) eGalax I
[Ubuntu-x-swat] [Bug 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
** Also affects: wayland 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/1727877 Title: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop To manage notifications about this bug go to: https://bugs.launchpad.net/wayland/+bug/1727877/+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 337926] Re: vino: mouse cursor stays in upper left corner
Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=490984. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-03-18T19:10:19+00:00 Fabrice wrote: With current rawhide, I experience the same problem than the one described here: https://bugs.launchpad.net/ubuntu/+source/libxtst/+bug/337926 It can be very simply reproduced with the xevent program as described in the ubuntu bug report. I filled this bug for the xorg intel driver component, instead of libXtst, because it seems to me specific to the intel driver. I could not reproduce it on another rawhide box, with the radeon driver. Reply at: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/10 On 2009-03-20T10:32:13+00:00 Fabrice wrote: reassigning to xorg-x11-server, as it seems its a bug in the XTEST extension. I think that GetPointerEvents() in ProcXTestFakeInput() should be called with POINTER_SCREEN flag set. The problem is visible on the eeepc (like described in the ubuntu bug), because of the synaptics driver, that changes pDev->valuator->axes->min_value and max_value. On my other rawhide box, these values are -1, and the bug is somewhat hidden is that case. Reply at: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/11 On 2009-03-25T06:51:43+00:00 Peter wrote: Fixed with xorg-x11-server-1.6.0-15. Thanks for reporting. Reply at: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/comments/12 ** Changed in: fedora Importance: Unknown => Medium -- 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/337926 Title: vino: mouse cursor stays in upper left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/337926/+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 66104] Re: [Gutsy] scim: input freezes in various applications under XIM mode
Launchpad has imported 25 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=201284. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-08-04T00:55:49+00:00 Leon wrote: Description of problem: Sometimes a KDE app will not accept inputs anymore (even input method is not activated). The only thing I can do to have input again is change to "Simple Composing Input Method" which is a test input method module in Qt, or restart the application. How reproducible: not everytime Steps to Reproduce: 1. Use a KDE app long enough Actual results: No inputs were outputted Expected results: Output english letters Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/0 On 2006-08-08T05:56:02+00:00 Jens wrote: Yep, I think I saw this on KDE desktop while testing this morning. Need to test with another IM to see if it is a kde/qt problem or issue with scim. XIM seems to work fine with other apps. Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/1 On 2006-08-15T02:21:29+00:00 Leon wrote: Reproducible in FC6 devel using the following test case by Choe Hwanjin: 1. $ export XMODIFIERS=@im=SCIM 2. $ export GTK_IM_MODULE=xim 3. $ gedit/kedit 4. press ctrl-N 5. try to type something Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/2 On 2006-08-15T02:54:45+00:00 Jens wrote: See http://sourceforge.net/mailarchive/forum.php?thread_id=30112584&forum_id=43684 for more details. It seems like that this is a xorg-x11 regression according to discussion there. Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/3 On 2006-08-15T09:42:37+00:00 Jens wrote: Reproduced on fc5 and fc6. RHEL4 and fc4 seem ok. Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/4 On 2006-08-17T13:29:34+00:00 Jens wrote: gedit loops with kinput2 and uim xim on rawhide. Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/5 On 2006-08-18T15:12:13+00:00 Kevin wrote: Adding upstream bug from the thread referred to in comment #3 above for tracking: https://bugs.freedesktop.org/show_bug.cgi?id=7869 Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/6 On 2006-08-19T05:38:37+00:00 Jens wrote: (Problem also occurs with gcin fwiw.) Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/7 On 2006-08-19T10:03:40+00:00 Jens wrote: I'm not easily able to reproduce the problem on kde apps. A workaround for gtk xim at least seems to be to set "/FrontEnd/X11/Dynamic = true" in .scim/config (but that breaks deadkey support under XIM direct input). Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/8 On 2006-08-20T04:21:13+00:00 Jens wrote: This can also easily be reproduced with kinput2 and gedit. 1. setup kinpu2 and restart desktop 2. run gedit 3. activate kinput2 with Shift-Space and press Ctrl-n at this point gedit goes into a hard loop. Reply at: https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104/comments/9 On 2006-08-20T09:38:51+00:00 Jens wrote: Also reproduced with libX11-0.99.3 fwiw. Here is a backtrace of where gedit loops with kinput2: #0 XIfEvent (dpy=0x6ca790, event=0x7fff84fd6000, predicate=0x2ab427a0 <_CheckCMEvent>, arg=0x10b4000 " \220ê�*") at IfEvent.c:58 #1 0x2ab42cea in _XimXRead (im=0x10b4000, recv_buf=0x7fff84fd61f0 "", buf_len=2048, ret_len=0x7fff84fd6144) at imTrX.c:446 #2 0x2ab45f86 in _XimReadData (im=0x10b4000, len=0x7fff84fd61a6, buf=0x7fff84fd61f0 "", buf_size=2048) at imTransR.c:154 #3 0x2ab46323 in _XimRead (im=0x10b4000, len=0x7fff84fd71fe, buf=0x7fff84fd61f0 "", buf_size=2048, predicate=0x2ab48c20 <_XimSyncCheck>, arg=0x10b8800 "\200\217ê�*") at imTransR.c:231 #4 0x2ab49d0e in _XimForwardEvent (ic=0x10b8800, ev=0x7fff84fd7290, sync=1) at imDefLkup.c:296 #5 0x2ab39c8b in _Xi
[Ubuntu-x-swat] [Bug 551193] Re: typo in mod() macro leads to 3rd-party controllable Xorg crash/exploit
Launchpad has imported 18 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=495733. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-04-14T14:39:07+00:00 Andrew wrote: Description of problem: When attempting to load http://www.buffalonews.com/entertainment/moviestv/index.html Xorg crashes: #0 0x0020161f in fbCopyAreammx (pSrc=0x8cdea90, pDst=0x8cb9620, src_x=0, src_y=3846, dst_x=18, dst_y=3871, width=920, height=60788) at fbmmx.c:2240 #1 0x00201776 in fbCompositeCopyAreammx (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=3846, xMask=0, yMask=0, xDst=18, yDst=3871, width=920, height=64598) at fbmmx.c:2303 #2 0x001f24fb in fbComposite (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=994, xMask=0, yMask=0, xDst=18, yDst=3871, width=920, height=178) at fbpict.c:1299 #3 0x00247eeb in XAAComposite (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=-926, xMask=0, yMask=0, xDst=18, yDst=789, width=920, height=178) at xaaPict.c:536 #4 0x0070c8d8 in i830_xaa_composite (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=-926, xMask=0, yMask=0, xDst=18, yDst=789, width=920, height=178) at i830_xaa.c:873 #5 0x0815e026 in cwComposite (op=1 '\001', pSrcPicture=0x8cf5030, pMskPicture=0x0, pDstPicture=0x8c304f0, xSrc=0, ySrc=-926, xMsk=0, yMsk=0, xDst=18, yDst=789, width=920, height=178) at cw_render.c:275 #6 0x0815a996 in damageComposite (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=-926, xMask=0, yMask=0, xDst=18, yDst=789, width=920, height=178) at damage.c:541 #7 0x08147b23 in CompositePicture (op=1 '\001', pSrc=0x8cf5030, pMask=0x0, pDst=0x8c304f0, xSrc=0, ySrc=-926, xMask=0, yMask=0, xDst=18, yDst=789, width=920, height=178) at picture.c:1789 #8 0x0814d95f in ProcRenderComposite (client=0x8c6c5c8) at render.c:758 #9 0x0814acd5 in ProcRenderDispatch (client=0xafa4f000) at render.c:2005 #10 0x0808815a in Dispatch () at dispatch.c:459 #11 0x0806fab5 in main (argc=10, argv=0xbfefe174, envp=Cannot access memory at address 0xafa4f008 This also hoses my virtual terminals (ctrl+alt+F1 gives me a white screen) and I have to reboot to get them back. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.1.1-48.52.el5 How reproducible: always Steps to Reproduce: 1. Grab the latest Firefox 3.5: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/firefox-3.5b4pre.en-US.linux-i686.tar.bz2 2. install it (bzip2 -dc firefox*bz2 | tar -x) 3. Run it (cd firefox; ./firefox) 4. Visit http://www.buffalonews.com/entertainment/moviestv/index.html ==> crash Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/551193/comments/0 On 2009-04-29T14:07:26+00:00 Matěj wrote: Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/551193/comments/1 On 2009-04-29T14:54:57+00:00 Andrew wrote: Created attachment 341765 X log Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/551193/comments/2 On 2009-04-29T14:55:39+00:00 Andrew wrote: Created attachment 341766 xorg.conf Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/551193/comments/3 On 2009-04-29T15:25:14+00:00 Andrew wrote: Created attachment 341775 Xorg-crashing html testcase Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/551193/comments/4 On 2009-05-06T21:28:43+00:00 Matěj wrote: X crasher HTML actually doesn't show anything on this RHEL5's firefox-3.0.10-1.el5 and neither the real page crashes (I have flash- plugin installed and Javascript fully on). Moreover, I don't see anything suspicious in the Xorg.0.log. Are you able to reproduce this issue with firefox running in the safe mode (i.e. run firefox -safe-mode from the command line)? Possibly ar
[Ubuntu-x-swat] [Bug 198951] Re: gnome-display-properties crashed with SIGSEGV in screen_info_new() - i855, fglrx, radeonhd
Launchpad has imported 9 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=436702. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-03-09T17:46:17+00:00 Charles wrote: Description of problem: Booting the new kernel with "i915.modeset=1" causes gnome-settings-daemon to crash after logging in. >From kernel changelog: * Thu Mar 06 2008 Dave Airlie - Add initial i915 drm modesetting tree - needs i915.modeset=1 on command line + new libdrm + new intel driver to actually be useful Version-Release number of selected component (if applicable): gnome-settings-daemon-2.21.92-2.fc9.x86_64 kernel-2.6.25-0.101.rc4.git3.fc9.x86_64 libdrm-2.4.0-0.9.fc9.i386 libdrm-2.4.0-0.9.fc9.x86_64 xorg-x11-drv-evdev-1.99.1-0.1.fc9.x86_64 xorg-x11-drv-i810-2.2.1-9.fc9.x86_64 xorg-x11-server-Xorg-1.4.99.901-1.20080307.fc9.x86_64 How reproducible: always Steps to Reproduce: 1. boot above kernel version with i915.modeset=1 command line 2. log into GNOME, note dialog about gnome-settings-daemon failing to start 3. try running "/usr/libexec/gnome-settings-daemon" manually Actual results: > /usr/libexec/gnome-settings-daemon ** (gnome-settings-daemon:3497): DEBUG: Successfully connected to D-Bus ** (gnome-settings-daemon:3497): DEBUG: Starting settings manager ** (gnome-settings-daemon:3497): DEBUG: Loading settings plugins from dir: /usr/lib64/gnome-settings-daemon-2.0/ ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/sound.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/sound for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/clipboard for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/media-keys for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrandr for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrdb for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/font.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/font for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/typing-break for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xsettings for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keybindings for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/dummy for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/mouse for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keyboard for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/screensaver for changes ** (gnome-settings-daemon:3497): DEBUG: Loading plugin: /usr/lib64/gnome-settings-daemon-2.0/background.gnome-settings-plugin ** (gnome-settings-daemon:3497): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/background for changes ** (gnome-settings-daemon:3497): DEBUG: Loa
[Ubuntu-x-swat] [Bug 196277] Re: A GNOME login without keypress dosn't set GNOME keyboard settings
Launchpad has imported 18 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=447252. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-05-19T05:40:03+00:00 Ilya wrote: Description of problem: A keyboard layout bug. After boot strange characters entered from keyboard instead proper ones. Also keyboard layout cannot be switched neither by switchkey, nor through menu switcher. Default layout is US English, second layout is Russian-winkeys. The proper layout can only be restored through keyboard properties screen. The attachment shows incorrect characters displayed just after bootup, with layout indicator shows US English as the current layout. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/75 On 2008-05-19T05:40:03+00:00 Ilya wrote: Created attachment 305899 screenshot showing the bug Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/76 On 2008-05-19T06:15:07+00:00 Ilya wrote: By the way, on the fresh system all worked well (FC9-release). The bug appeared after I made updates from the Internet. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/77 On 2008-07-03T17:14:31+00:00 Milan wrote: *** Bug 449305 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/136 On 2008-07-03T17:21:44+00:00 Milan wrote: I'm not sure what component should be selected for this bug. I hit the same problem. After a restart I have to go to the keyboard setting through keyboard applet and change something (deleting and adding keymap). Then keyboard switching works then again. I'm using default GNOME session. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/137 On 2008-07-03T22:14:33+00:00 Ilya wrote: I think official Fedora notes should mention that languages other than English are not fully supported. Otherwise all people who use another language would think Fedora is a very buggy system. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/138 On 2008-07-24T09:31:20+00:00 Simos wrote: This bug appears to be similar to keyboard layout switching shortcut doesn't work after reboot https://bugs.launchpad.net/bugs/196277 Could you please verify that you have enabled autologin on your system? If this is the case, then it would be better to change the report title to "Autologin in GNOME disables keyboard layout switching" Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/166 On 2008-07-24T09:40:00+00:00 Alexey wrote: As i know fedora 9 do not have autologin feature because xserver.1.4.9 do not support it anymore. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/167 On 2008-07-24T10:01:30+00:00 Ilya wrote: You're wrong. It has no GUI for autologin to switch on, but I enabled autologin through config files. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/170 On 2008-07-24T11:36:56+00:00 Simos wrote: I am not familiar with Fedora; in Ubuntu there is an option in System/Administration/Login Window/Security/Enable Automatic Login. What this actually does is it tells GDM to let a specific user in by default. Essentially, it's a GDM option in Ubuntu. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/172 On 2008-07-29T05:03:29+00:00 Peter wrote: There are two separate issues here (from what I can tell so far). One is that the keymap with autologin is different before and after the first key has been pressed (when the keyboard is evdev anyway). The other one is that gnome is incapable of setting the xkb map correctly. Specifying layouts in HAL's fdi file or the xorg.conf works fine, including the switcher applet. I'm still trying to figure out why the second happens. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/196277/comments/180 -
[Ubuntu-x-swat] [Bug 297335] Re: Video on Intel D201GLY2 motherboard broken, can't compile Intel's fixed SiS662 drivers
** Changed in: xserver-xorg-video-sis (Fedora) Status: Unknown => Won't Fix ** Changed in: xserver-xorg-video-sis (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-sis in Ubuntu. https://bugs.launchpad.net/bugs/297335 Title: Video on Intel D201GLY2 motherboard broken, can't compile Intel's fixed SiS662 drivers To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-sis/+bug/297335/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
** Changed in: libinput (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1726934/+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 1726595] Re: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10
"wayland" is just the protocol library, so not the right place to file this. The xorg-server package covers both native Xorg servers and Xwayland so filing there... until someone finds somewhere more appropriate. ** Package changed: wayland (Ubuntu) => xorg-server (Ubuntu) -- 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/1726595 Title: Running Matlab (R) from ssh session with X forwarding doesn't work anymore in 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1726595/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
Please try VT switching to VT4 (Ctrl+Alt+F4), log in and retest with 'evtest'. If you continue to get no results then that's a kernel bug. Because Wayland and libinput are not part of the equation when you're testing the kernel directly. P.S. Also check if your laptop keyboard has a function key for disabling/enabling the touchpad. It might simply be disabled in hardware (for reasons unknown). ** Package changed: libinput (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1727909] [NEW] Using Wayland
Public bug reported: When I've put my pendrive system just close session and I go back to log in screen. It happens in very different ways. Attached goes the logs file. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 26 23:55:20 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd HD Graphics 5500 [144d:c755] InstallationDate: Installed on 2017-10-19 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: SAMSUNG ELECTRONICS CO., LTD. 370E4K ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=b04e4fad-4a52-4169-9ba3-0786c9a0ab39 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P06RCX.075.160311.JJ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP370E4K-KW3BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL8537A0C-C01-G001-S0001+10.0.10240 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RCX.075.160311.JJ:bd03/11/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn370E4K:pvrP06RCX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP370E4K-KW3BR:rvrSGL8537A0C-C01-G001-S0001+10.0.10240:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: SAMSUNG ATIV dmi.product.name: 370E4K dmi.product.version: P06RCX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful crash ubuntu wayland-session ** Attachment added: "Logs file" https://bugs.launchpad.net/bugs/1727909/+attachment/4997355/+files/error -- 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/1727909 Title: Using Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727909/+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 1416601] Re: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343)
** Changed in: xserver-xorg-input-synaptics (Fedora) Status: Unknown => Fix Released ** Changed in: xserver-xorg-input-synaptics (Fedora) Importance: Unknown => Undecided -- 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/1416601 Title: touchpad does not respond to tap-to-clicks in I2C mode in Ubuntu 15.04 on 2015 XPS 13 (9343) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1416601/+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 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
Launchpad has imported 46 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=461829. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-09-10T20:53:26+00:00 Andrew wrote: Created attachment 316355 Xorg.0.log with 2.4.2-7 and XAA Description of problem: X fails to start and the Xorg.0.log shows: (EE) intel(0): Failed to pin front buffer: Cannot allocate memory Fatal server error: Couldn't bind memory for BO front buffer Note that my xorg.conf is set to use XAA instead of EXA because the latter causes the computer to completely hang when X tries to start. In dmesg, the following error appears repeatedly: mtrr: type mismatch for d000,1000 old: write-back new: write-combining [drm:i915_gem_object_bind_to_gtt] *ERROR* GTT full, but LRU list empty [drm:i915_gem_object_pin] *ERROR* Failure to bind: -12<4 Version-Release number of selected component (if applicable): xorg-x11-drv-i810-2.4.2-7 I was able to successfully use XAA with xorg-x11-drv-i810-2.4.2-1, but I have not been able to use either XAA or EXA in any version since. Please let me know if any other output would be helpful. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/0 On 2008-09-10T21:01:28+00:00 Andrew wrote: Created attachment 316357 Xorg.0.log with 2.4.2-7 and EXA I am also attaching the Xorg.0.log from xorg-x11-drv-i810-2.4.2-7 with EXA, which causes the system to completely hang. In some runs, there were no errors in the Xorg.0.log (it just stopped), but in others, it gave more verbose output, which I am attaching. It appears that the same messages appeared in the syslog as with XAA. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/1 On 2008-09-11T07:27:29+00:00 Matěj wrote: Isn't this the same bug as bug 461171, or are we talking about different machine here? Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/2 On 2008-09-11T14:13:03+00:00 Andrew wrote: I could be mistaken, but I believe it to be a different issue. In this case, I cannot ever get X to start, and there are errors that appear in the Xorg.0.log and in dmesg. With 2.4.2-1, X usually worked, but I haven't been able to get it to start with 2.4.2-2 and later. In contrast, bug 461171 is an occasional problem (20% of the time) that I noticed with 2.4.2-1, and it doesn't put any errors in the log. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/3 On 2008-09-19T21:31:44+00:00 Andrew wrote: I was just curious if there's any other information I should provide. By the way, I've tried as recent rpms as xorg-x11-drv-i810-2.4.2-8.fc10.x86_64, still without any luck. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/4 On 2008-09-23T17:17:38+00:00 Andrew wrote: I noticed that there's an upstream commit which looks like it might be a fix: http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video- intel.git;a=commit;h=e2743a409a02978ca8e953dbbeeb96f61bbd5ce6 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/5 On 2008-09-23T22:45:00+00:00 Konrad wrote: I am suffering from the very same problem. The upstream git commit seems to be already present in the latest xorg (xorg-x11-drv-i810-2.4.2-8.fc10.i386).. X startup fails all the time. 100% reliable. (intel 82865G controller) Just went from F8 (X OK) to todays Rawhide, fully uptodate. Surviving with fbdev for now... Greetings, Konrad Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/6 On 2008-10-04T20:00:21+00:00 Konrad wrote: Created attachment 319473 Xorg startop log Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/304871/comments/7 On 2008-10-04T20:02:08+00:00 Konrad wrote: comment #7 with todays rawhide xorg-x11-drv-i810-2.4.2-9. still at fbdev :-( system-config-display is unable to start as well. what can I do to track this down? Konrad Reply at: https://bugs.
[Ubuntu-x-swat] [Bug 1727911] [NEW] fcitx not dispaly
Public bug reported: Choice Fcitx No Fcitx`sign on the top right corner ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 27 11:07:49 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2017-10-24 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 4180AP3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=3b93ab4f-c57d-4ccf-94fd-7c43d7fb3c36 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET73WW (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 4180AP3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET73WW(1.43):bd11/30/2012:svnLENOVO:pn4180AP3:pvrThinkPadT420:rvnLENOVO:rn4180AP3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T420 dmi.product.name: 4180AP3 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- 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/1727911 Title: fcitx not dispaly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727911/+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 1727770] Re: wayland does not have logic for a Lenovo laptop on the dock
** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - wayland does not have logic for a Lenovo laptop on the dock + If I resume on the dock, Gnome Shell seems to recognize the lid as closed and suspends -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1727770 Title: If I resume on the dock, Gnome Shell seems to recognize the lid as closed and suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727770/+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 1727039] Re: Xorg crash
** Package changed: xorg (Ubuntu) => ubuntu -- 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/1727039 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1727039/+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 1724259] Re: gnome-shell frozen and using 100% CPU after docking and display configuration change
** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: libinput via https://bugs.freedesktop.org/show_bug.cgi?id=103298 Importance: Unknown Status: Unknown ** Changed in: libinput (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1724259/+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 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Launchpad has imported 29 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=214446. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2006-11-07T17:53:46+00:00 Travis wrote: Description of problem: The screen does not refresh when connecting to a VNC Server (remote desktop) that has 'Desktop Effects' enabled. When connecting to a Server with Desktop Effects enabled, a screen shot of the desktop is displayed in the client but never again updates. You can monitor the Server's display and see that the mouse and keyboard function, however no output can be seen through the VNC client. Version-Release number of selected component (if applicable): Zod How reproducible: This is consistent with my configuration. Disabling Desktop Effects immediately resolved the problem. Steps to Reproduce: 1. Enable desktop effects 2. Establish a VNC connection to FC6 from remote machine 3. Note the screen displays, but you do not recieve and screen updates Actual results: Expected results: Additional info: The configuration is on a Dell D610 with Intel video drivers. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/0 On 2006-11-07T17:56:06+00:00 Travis wrote: *** Bug 214448 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/1 On 2006-11-08T10:22:26+00:00 Adam wrote: please, could you specify more when is the desktop effect options?? I can't find it + which window manager're you using. thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/2 On 2006-11-08T12:35:17+00:00 Travis wrote: In gnome, under System/Preferences/Desktop Effects. You can 'Enable Desktop Effects' which change the behavior of the Windows to wobble when dragged. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/3 On 2006-11-20T16:31:08+00:00 Victor wrote: I have the same problem, my window manager is the default one, compiz, it shows up in the ps command as following : compiz --sm-client-id default1 gconf If you exits the vncviewer and restart the session the image is updated. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/4 On 2006-12-05T13:43:21+00:00 Adam wrote: Could you please write me if you join to native vncserver (from vnc-server package) or to gnome's vino server? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/5 On 2006-12-05T16:31:54+00:00 Travis wrote: It is the vino server, activated by the Remote Desktop features within Gnome. This is from a very generic installation of FC6. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/6 On 2007-01-18T16:37:18+00:00 Adam wrote: This bug isn't in vnc. Reassigning to proper component. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/7 On 2007-08-17T15:29:49+00:00 Didier wrote: Confirmed on a fully updated F7, with components : vino-2.18.0-1.fc7 vnc-4.1.2-18.fc7 (for vncviewer) compiz-0.4.0-1.fc7 (for desktop effects) Disclaimer : tested with the proprietary nvidia driver (kmod-nvidia-100.14.11-1.2.6.22.1_41.fc7 and xorg-x11-drv-nvidia-100.14.11-1.lvn7) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/8 On 2007-09-03T10:10:53+00:00 Tomasz wrote: This bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=208983 Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/12 On 2007-11-04T01:19:33+00:00 Aaron wrote: x11vnc apparently works where vino fails: http://ubuntuforums.org/showthread.php?t=470306 Perhaps the '-noxdamage' option for x11vnc can be reproduced for vino to fix this? Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/353126/comments/13 O
[Ubuntu-x-swat] [Bug 67188] Re: "Error activating XKB configuration." - Requires manual xorg.conf editing
Launchpad has imported 26 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=446684.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2008-05-15T17:00:10+00:00 Eelco wrote:
Description of problem:
[Actually, the problem occurs in gnome-keyboard-properties, but that one was not
in the components list.]
Choosing keyboard layout Macbook/Macbook Pro (Intl) produces an error in Fedora
9.
Version-Release number of selected component (if applicable):
GNOME gnome-keyboard-properties 2.22.1
How reproducible:
1. start gnome-keyboard-properties
2. select layouts tab
3. select keyboard model MacBook/MacBook Pro (Intl)
4. close
Error message:
==
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation
X server version data:
The X.Org Foundation
10499901
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
Additional info:
Hardware: Macbook (late 2006 model)
Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/36
On 2008-05-15T17:00:10+00:00 Eelco wrote:
Created attachment 305510
screenshot of the error message
Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/37
On 2008-05-17T08:31:35+00:00 Eelco wrote:
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "intl", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "intl", ""
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model = macbook79
options = [Compose key compose:rwin]
overrideSettings = true
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/38
On 2008-05-17T13:05:12+00:00 Lubomir wrote:
Eelco: Thank you for reporting the problem, I am reassigning it to the right
component owner.
The following command might be useful to find out which component does the
binary belong to:
$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)
Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/39
On 2008-05-17T13:08:02+00:00 Eelco wrote:
$ rpm -qf --qf %{name}\\n $(which gnome-keyboard-properties)
control-center
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/40
On 2008-05-22T23:29:09+00:00 Jose wrote:
I'm having the same problem (MacBook with a Portuguese keyboard layout):
$ xprop -root | grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "pt", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "pt", "", ""
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = [pt mac,pt]
model = macbook79
options = [grp grp:alts_toggle]
overrideSettings = true
/jpo
Reply at:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/67188/comments/41
On 2008-09-11T12:33:50+00:00 Peter wrote:
Eelco:
The problem is that the keysyms for mac don't provide a intl variant. The error
can be reproduced on the commandline by running:
setxkbmap -layout us -model macbook79 -variant intl -print | xkbcomp - :0
Error:No Symbols named "intl" in the include file
"macintosh_vndr/us"
Exiting
If this used to work, or you think it should work, please file a bug on
upstream bugzilla: https://bugs.freedesktop.org/enter_bug.cgi?product
=xkeyboard-config
Jose:
I can't reproduce your problem. Can you try to run:
setxkbmap -layout pt -model macbook79 -option grp:alts_toggle -print | xkbcomp
- :0
and check for an error message. If there is one, please attach it. If there is
none, please try if the macbook79 model works with any other layout (e.g. us).
If it does, please try to find which setting triggers the error - it could be
the layout or the alts_toggle option (unlikely).
Reply at: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-
config/+bug/67188/comments/44
On 2008-10-20T21:33:16+00:00 Matěj wrote:
Reporter, could you please reply to the previous question? If you won't
reply in o
[Ubuntu-x-swat] [Bug 542731] Re: [gm45] Xorg crash - Failed to submit batchbuffer: No space left on device
** Changed in: fedora Status: Unknown => Won't Fix ** Changed in: fedora Importance: Unknown => Medium -- 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/542731 Title: [gm45] Xorg crash - Failed to submit batchbuffer: No space left on device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/542731/+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 513011] Re: [drm:radeon_cs_ioctl] Failed to parse relocation error when switching resolutions on HP NX7000 on Lucid
Launchpad has imported 5 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=547598. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-12-15T03:52:37+00:00 Dan wrote: Created attachment 378424 X log from resolution switch attempt Switching resolution on my T42 results in a black screen, though I can hit ESC and return to the previous mode without problems. Happens 100% of the time when switching to 800x600 (since the S-Video output only does 800x600). This didn't happen shortly before F12 Gold but regressed some time after that. 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] kernel-2.6.31.6-166.fc12.i686 xorg-x11-drv-ati-6.13.0-0.12.20091119git437113124.fc12.i686 libdrm-2.4.15-6.fc12.i686 xorg-x11-server-Xorg-1.7.1-7.fc12.i686 mesa-libGL-7.6-0.17.fc12.i686 Running in AGP mode. Interesting log bits: [drm] LVDS-13: set mode 18 Unpin not necessary for f2881e00 ! [drm] LVDS-13: set mode 1a Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/513011/comments/0 On 2009-12-15T03:54:44+00:00 Dan wrote: Attempting to switch to any mode other than 1024x768 (native panel resolution) fails. Other dmesg logs from other attempts: [drm] LVDS-13: set mode 1b Unpin not necessary for f320de00 ! [drm] LVDS-13: set mode 1d [drm] LVDS-13: set mode 1e Unpin not necessary for f3141300 ! [drm] LVDS-13: set mode 20 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/513011/comments/1 On 2010-01-14T08:15:42+00:00 Dave wrote: Please retry with kernel 2.6.32.3-24 along with libdrm/xorg-x11-drv- ati/mesa from updates-testing Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/513011/comments/2 On 2010-02-15T19:31:35+00:00 Dan wrote: On rawhide with this laptop (t42) now, and resolution switching does not work. I don't get any error messages in the kernel logs, *or* in Xorg.0.log, but I simply get a black screen. Xorg.0.log says: [ 336.852] (II) RADEON(0): EDID for output VGA-0 [ 336.856] (II) RADEON(0): EDID for output DVI-0 [ 336.856] (II) RADEON(0): EDID for output LVDS [ 336.857] (II) RADEON(0): Not using default mode "320x240" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "400x300" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "400x300" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "512x384" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "640x480" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "640x512" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "800x600" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "896x672" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "928x696" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "960x720" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "700x525" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Not using default mode "1024x768" (doublescan mode not supported) [ 336.857] (II) RADEON(0): Printing probed modes for output LVDS [ 336.858] (II) RADEON(0): Modeline "1024x768"x60.4 65.00 1024 1040 1176 1336 768 769 775 805 (48.7 kHz) [ 336.858] (II) RADEON(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) [ 336.858] (II) RADEON(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) [ 336.858] (II) RADEON(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz) [ 336.858] (II) RADEON(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz) [ 336.858] (II) RADEON(0): Modeline "848x480"x59.7 31.50 848 872 952 1056 480 483 493 500 -hsync +vsync (29.8 kHz) [ 336.858] (II) RADEON(0): Modeline "720x480"x59.7 26.75 720 744 808 896 480 483 493 500 -hsync +vsync (29.9 kHz) [ 336.858] (II) RADEON(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) [ 336.858] (II) RADEON(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz) [ 336.864] (II) RADEON(0): EDID for output S-vid
[Ubuntu-x-swat] [Bug 665956] Re: Theme änd keyböärd läyöüt göing cräzy
Launchpad has imported 31 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=537708. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-11-15T22:03:07+00:00 Matthew wrote: Description of problem: I've been using "keycode 135 = Mode_switch" in my ~/.xmodmap for years, to change my "menu" key into something useful. Starting sometime fairly recently (not sure exactly; sorry) occasionally (no repeatable case, but happens regularly enough to be annoying), the mode_switch gets stuck in on, such that pressing the key and a letter gives its normal version rather than its mode_switch version. (It's as if the equivalent of caps-lock for mode_switch is on.) There doesn't seem to be any cure but hitting mode_switch a bunch of times and other random typing -- eventually it goes off again. Version-Release number of selected component (if applicable): Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev because it's convenient -- could be a lot of things, I suppose. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/0 On 2009-11-16T15:34:40+00:00 Bug wrote: This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/1 On 2009-11-16T21:32:27+00:00 Matěj wrote: (In reply to comment #0) > Possibly xorg-x11-drv-evdev-2.3.0-1.fc12.x86_64. I'm just blaming evdev > because > it's convenient -- could be a lot of things, I suppose. Let's try to blame Xserver itself :) (it doesn't matter that much because issues of input go to Peter anyway). Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/2 On 2009-12-14T20:59:09+00:00 Matthew wrote: Created attachment 378349 dmesg output Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/3 On 2009-12-14T21:00:19+00:00 Matthew wrote: Created attachment 378350 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/4 On 2009-12-14T21:06:01+00:00 Matthew wrote: Attached requested logs. This is on my Rawhide box. It also happens on my F12 system at home, which has a different radeon card and generally different hardware overall. I can attach that if you think it might be helpful. I think *maybe* the problem is related to the key _next_ to this one; I've defined that to be Multi_key, and it may be related to hitting that accidentally in some way. I still can't reproduce _on purpose_ though. (But it does happen once every couple of days.) Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/5 On 2009-12-14T21:06:56+00:00 Matthew wrote: Created attachment 378354 xmodmap I must add that the ability to type hearts and flowers was added at the request of my 4-year-old daughter. Just sayin'. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/6 On 2010-01-23T22:18:50+00:00 Chris wrote: -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/7 On 2010-01-23T22:25:17+00:00 Matthew wrote: This is still happening, by the way. And I removed the definition for Multi_key, so that's _not_ it. Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/665956/comments/8 On 2010-03-13T11:43:17+00:00 Matthew wrote: This is still happening. It is very annoying. I attached the requested informat
[Ubuntu-x-swat] [Bug 487362] Re: xorg is eating up memory
Launchpad has imported 3 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=560668. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-02-01T15:09:26+00:00 Alan wrote: Description of problem: [RHEL5.3] Xorg Consumes all memory This problem is across a number of systems, about 15 machines, All use KDE. It is possible to make some changes on some systems. What we found out so far is that the machine with the new nVidia driver consumed all memory again. Machines with Vesa drivers are OK so far but the user of that workstation claims that it usually takes some time till it the phenomenon occurs. This case is about one customer who has some sites worldwide. All sites run with same configuration under Sun ULTRA20 M2 Workstation,with nVidia Video card. About 15 of his systems experience this phenomenon worldwide. We tried on one machine to update to a newer nVidia driver, and on another machine to use Vesa driver. It is very problematic for the customer to work with Vesa drivers since he needs to use 1600x1200 screen resolution, and we couln't run this system with such resolution using Vesa driver. After analysing his sar data of workstation with nVidia driver we found out that Xorg begins to consume alot of memory when the user is not working during evening hours. We configured one of the problematic machines to use Vesa drivers,today on that machine Xorg consumes 1.4GB of memory. We configured another machine to use Vesa drivers with an ATI card to make sure that nVidias drivers cause consumption of all memory. (as mentioned previously, we couldn't use 1200x1600 resolution with Vesa driver and nVidia card) In this case we've already seen that the problem reproduces also with ATI video card using Redhat's VESA drives, so this is not video card driver related problem. The customer is currently preparing to deploy RHEL 5 within their organization. The mentioned problem also reproduces on RHEL 4 systems. Version-Release number of selected component (if applicable): How reproducible: It takes a very long time to see this problem One thought about this bug: "how does xorg manage memory for quitting application" question: 12:42 < ofourdan|lunch> pamadio: you can always tell the X server to retain the resources, but that's for very specific use and hardly ever used - But if you want you can :) 12:43 < ofourdan|lunch> one of the use is to set a pixmap to the root window, the app that sets the pixmaps needs to specify thatthe pixmap must not be freed once the app terminates 12:44 < ofourdan|lunch> another use is to make an app to self-recover from a network disconnection. Although this is theorically possible, I am yet to find an apps that implement this :) 12:54 < ofourdan> pamadio: see "man XSetCloseDownMode" 12:55 < ofourdan> pamadio: by default all connections start in DestroyAll mode. >From alanm: I've never seen this in practice either. Steps to Reproduce: Customer s/w has to run for a very long time before this problem is seen Actual results: X.org Server consumes all memory Expected results: Normal operation of Xserver Notes from SEG This looks to be an issue that was supposed to have been fixed in the VESA driver https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=81559 https://enterprise.redhat.com/issue-tracker/?module=issues&action=view&tid=83772 The problem here is that there wasn't a reproducer. Since it took so long for this problem to reappear I gather that there isn't an easy way to reproduce this ? I could create a BZ for this but I know that engineering will want to have some way of reproducing this. This looks to me to be a slow memory leak and without some way of reproducing this I don't know if they will do anything about this. The earlier IT's seem to indicate that this is a leak that occurs when closing a client so I would ask the customer if this is something that happens over a long period of time or does the memory consumption occur all of a sudden ? I also don't see any indication of any long running applications that would eat up memory so it looks to be a VESA driver problem where memory isn't being released when a client closes down. Let me know as soon as you can and I'll create a BZ for this but I'm really not sure if engineering will do much about it. The best I can do is pass it on to them and let them decide. 1) given where we are in the development cycle with RHEL 4. It's pretty late in the cycle. 2) the fact that these are U4 systems. I know that they will want to know why the customer systems have not been updated to U8. 3) the lack of a reproducer. While there have been other reporters of similar behaviour from a couple of othe cus
[Ubuntu-x-swat] [Bug 1725836] Re: No more than 2 displays work simultaneously
Thanks. Perhaps we jumped the gun though... On your login screen do you see two options "Ubuntu" and "Ubuntu on Xorg", or only one? It looks like you might be experiencing a problem with Xorg judging by comment #4: Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): flip queue failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) RADEON(0): Page flip failed: Invalid argument Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) RADEON(0): present flip failed ** Bug watch added: GNOME Bug Tracker #789540 https://bugzilla.gnome.org/show_bug.cgi?id=789540 ** Also affects: mutter via https://bugzilla.gnome.org/show_bug.cgi?id=789540 Importance: Unknown Status: Unknown ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1725836 Title: No more than 2 displays work simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1727877] Re: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop
glxgears is not a benchmark ** No longer affects: xorg-server (Ubuntu) ** Changed in: xorg-server Status: New => Invalid ** Project changed: wayland => gnome-control-center (Ubuntu) -- 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/1727877 Title: AMD Radeon 520 graphics card not detected in wayland session when using AMD/Intel hybrid laptop To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1727877/+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 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
why on earth would you need that for nvidia hardware? ** Changed in: xorg (Ubuntu) Status: Confirmed => Incomplete -- 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/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ast/+bug/1708994/+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 1708994] Re: package xserver-xorg-video-ast-hwe-16.04 missing
besides, the driver has been removed from the archive since xenial which would explain why there's no -hwe-16.04 ** Package changed: xorg (Ubuntu) => xserver-xorg-video-ast (Ubuntu) ** Changed in: xserver-xorg-video-ast (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ast in Ubuntu. https://bugs.launchpad.net/bugs/1708994 Title: package xserver-xorg-video-ast-hwe-16.04 missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ast/+bug/1708994/+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
Re: [Ubuntu-x-swat] [Bug 1725836] Re: No more than 2 displays work simultaneously
I see both. During power up, the messages appear on displays 1 and 3. The sign in is on screen 2 (primary display). The display manager shows 3 displays, but after the apply is selected, only two work. Why do they work with Xfce and not with gnome? Thanks Peter On Fri, Oct 27, 2017 at 2:20 AM, Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thanks. Perhaps we jumped the gun though... > > On your login screen do you see two options "Ubuntu" and "Ubuntu on > Xorg", or only one? > > It looks like you might be experiencing a problem with Xorg judging by > comment #4: > > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): flip queue failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (WW) > RADEON(0): Page flip failed: Invalid argument > Oct 23 08:21:34 hostname /usr/lib/gdm3/gdm-x-session[1533]: (EE) > RADEON(0): present flip failed > > ** Bug watch added: GNOME Bug Tracker #789540 >https://bugzilla.gnome.org/show_bug.cgi?id=789540 > > ** Also affects: mutter via >https://bugzilla.gnome.org/show_bug.cgi?id=789540 >Importance: Unknown >Status: Unknown > > ** Also affects: xorg-server (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1725836 > > Title: > No more than 2 displays work simultaneously > > Status in Mutter: > Unknown > Status in gnome-shell package in Ubuntu: > Incomplete > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > I have three displays that worked fine in 17.04. > Now ith 17.10 I can only use two of them. Either 1 & 2, 1& 3 or 2 2 & 3. > All three seem to be properly specified in monitors.xml. > The display setup scree detects all three. > UBUNTU 17.10 > AMD PitcairnLSB Version: core-9.20160110ubuntu5-amd64: > core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9. > 20160110ubuntu5-noarch > --- > ApportVersion: 2.20.7-0ubuntu3 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-02-23 (242 days ago) > InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 > (20161012.2) > Package: mutter > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 > Tags: artful > Uname: Linux 4.13.0-16-generic x86_64 > UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1725836/+subscriptions > -- 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/1725836 Title: No more than 2 displays work simultaneously To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725836/+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 1592561] Re: Doesn't work on arm64
the driver has been removed from the archive, the hw should use the default modesetting driver instead ** Changed in: xserver-xorg-video-ast (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ast in Ubuntu. https://bugs.launchpad.net/bugs/1592561 Title: Doesn't work on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ast/+bug/1592561/+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 1724487] Re: Quirk for 2-button mouse Logitech M560
What's the point of this bug? You're not saying what to quirk, the driver you're using is not -evdev and any quirks should really go upstream anyway.. (libinput) ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1724487 Title: Quirk for 2-button mouse Logitech M560 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1724487/+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
