[Ubuntu-x-swat] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi all. Please excuse my novice approach guys but I hope that I am making some kind of contribution! I to have a Lenovo Legion 5 and I am running Opensuse Tumbleweed with Kernel 5.9.11-1 with Gnome 3.38. With some help from the Opensuse forum I have the following error; input: MSFT0001:00 04F3:3186 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c- MSFT0001:00/0018:04F3:3186.0001/input/input7 This as you may gather stops my trackpad from working and they have suggested I visit here and ask for any help! All the best - Harry -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
I can confirm that rolling back to linux-firmware=1.173.12 solves the issue with Kernel: 5.3.0-40-generic x86_64. -- 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/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1865130/+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 1811159] Re: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20
And... spoke too soon. It happens under xrender as well. Shorter freezes, frequency is the same. -- 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/1811159 Title: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1811159/+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 1811159] [NEW] temporary freeze under opengl, not xrender, 18.10 & kernel 4.20
Public bug reported: Several times an hour, usually when switching focus from one window to another, all but the mouse will stop changing for a few seconds to a minute or so. If a video is playing the sound will proceed as if normal but the screen will not change. The shape of the mouse will not change. This is with stock ubuntu 18.10 under opengl with nouveau and i915 drivers active (xrandr). I tried using the latest possible ubuntu- compiled kernel, 4.20 with exactly the same results. This did not happen before sometime after the cosmic native initial install. When I change kde to 'xrender' -- the problem disappears. The oft reported dmesg content is: [83492.038575] WARNING: CPU: 2 PID: 2114 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038576] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ebtable_filter ebtables ip6table_filter ip6_tables devlink iptable_filter bpfilter cmac bnep bridge stp llc snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp i915 kvm_intel kvmgt vfio_mdev crct10dif_pclmul crc32_pclmul nouveau mdev vfio_iommu_type1 ghash_clmulni_intel vfio aesni_intel kvm aes_x86_64 crypto_simd snd_hda_codec_hdmi cryptd uvcvideo ttm glue_helper videobuf2_vmalloc snd_hda_intel irqbypass videobuf2_memops btusb intel_cstate drm_kms_helper snd_hda_codec snd_usb_audio videobuf2_v4l2 btrtl dell_wmi videobuf2_common dell_smbios btbcm snd_seq_dummy intel_rapl_perf btintel sparse_keymap drm dcdbas videodev dell_wmi_descriptor snd_seq_oss snd_usbmidi_lib snd_hda_core mxm_wmi media joydev input_leds 8250_dw wmi_bmof snd_seq_midi snd_hwdep snd_seq_midi_event bluetooth snd_pcm snd_rawmidi mei_me idma64 snd_seq snd_seq_device i2c_algo_bit [83492.038598] mei fb_sys_fops syscopyarea sysfillrect mac_hid virt_dma ecdh_generic sysimgblt snd_timer snd soundcore acpi_pad sch_fq_codel parport_pc ppdev lp sunrpc parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c hid_generic usbhid uas hid usb_storage alx i2c_i801 ahci mdio intel_lpss_pci libahci intel_lpss wmi pinctrl_sunrisepoint video pinctrl_intel [83492.038611] CPU: 2 PID: 2114 Comm: Xorg Not tainted 4.20.0-042000-generic #201812232030 [83492.038611] Hardware name: Dell Inc. XPS 8910/0WPMFG, BIOS 1.1.7 07/17/2018 [83492.038625] RIP: 0010:nvif_vmm_put+0x6d/0x80 [nouveau] [83492.038626] Code: 00 00 48 8d 55 e0 be 02 00 00 00 48 c7 45 e0 00 00 00 00 48 89 45 e8 e8 a1 e5 ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 ba c3 7e cc 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 [83492.038627] RSP: 0018:ba4a0308fbc0 EFLAGS: 00010282 [83492.038628] RAX: fffe RBX: ba4a0308fbf0 RCX: [83492.038629] RDX: 0010 RSI: ba4a0308fb30 RDI: ba4a0308fbd0 [83492.038629] RBP: ba4a0308fbe0 R08: c0d05b90 R09: [83492.038630] R10: 91cc290bd310 R11: 0030 R12: ba4a0308fc28 [83492.038630] R13: 91cc2bec60b0 R14: R15: 91cc290ba800 [83492.038631] FS: 7f5a5f2f0a80() GS:91cc2ea8() knlGS: [83492.038632] CS: 0010 DS: ES: CR0: 80050033 [83492.038633] CR2: 7f5a5800c000 CR3: 00043f42e003 CR4: 003606e0 [83492.038633] DR0: DR1: DR2: [83492.038634] DR3: DR6: fffe0ff0 DR7: 0400 [83492.038634] Call Trace: [83492.038659] nouveau_vma_del+0x75/0xc0 [nouveau] [83492.038682] nouveau_gem_object_close+0x1e0/0x1f0 [nouveau] [83492.038692] drm_gem_object_release_handle+0x34/0xa0 [drm] [83492.038698] drm_gem_handle_delete+0x61/0x90 [drm] [83492.038703] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038709] drm_gem_close_ioctl+0x25/0x30 [drm] [83492.038715] drm_ioctl_kernel+0xad/0xf0 [drm] [83492.038720] drm_ioctl+0x237/0x420 [drm] [83492.038726] ? drm_gem_handle_create+0x40/0x40 [drm] [83492.038728] ? do_iter_write+0xdd/0x190 [83492.038750] nouveau_drm_ioctl+0x73/0xc0 [nouveau] [83492.038752] do_vfs_ioctl+0xa9/0x640 [83492.038754] ? __sys_recvmsg+0x88/0xa0 [83492.038755] ksys_ioctl+0x67/0x90 [83492.038756] __x64_sys_ioctl+0x1a/0x20 [83492.038758] do_syscall_64+0x5a/0x110 [83492.038759] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [83492.038760] RIP: 0033:0x7f5a606273c7 [83492.038761] Code: 00 00 90 48 8b 05 c9 3a 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 99 3a 0d 00 f7 d8 64 89 01 48 [83492.038762] RSP: 002b:7ffd2a2c6438 EFLAGS: 3246 ORIG_RAX: 0010 [83492.038763] RAX: ffda RBX: 555e65a090c0 RCX: 7f5a606273c7 [83492.038763] RDX: 7ffd2a2c6470 RSI: 40086409 RDI: 0012 [83492.038764] RBP: 7ffd2a2c6470 R08: 555e64a01d78 R09: 0001 [83492.038764] R10:
[Ubuntu-x-swat] [Bug 1684123] Re: bus: MMIO read of 00000000 FAULT at 3e6684 [ IBUS ]
nouveau :01:00.0: bus: MMIO read of FAULT at 10ac08 [ IBUS ] nouveau :01:00.0: bus: MMIO read of FAULT at 3e6684 [ IBUS ] 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1684123 Title: bus: MMIO read of FAULT at 3e6684 [ IBUS ] To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1684123/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
comment #39 fixed it for me -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1493888] Re: FGLRX incompatible with gcc 5
I'm seeing the exact same problem as Phillip Gemmell in post #243. When trying to update fglrx with the wily-proposed versions I get the message "Release 'wily-proposed' for 'flgrx-*' was not found". This is all happening on a fresh install of 15.10. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1493888 Title: FGLRX incompatible with gcc 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1493888/+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 1290002] Re: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update
Is this issue ever going to be fixed? Or no one cares anymore about older Ubuntu versions? 12.04 was supposed to be LTS! These issues should have not been neglected, nor allowed to happen in the first place. Before that specific update, which i suspect is this one: xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5), everything on my keyboard was working flawlessly. I cannot use the quickbuttons around the volume wheel or the volume wheel at all. This should be an easy fix for the developers. Please look into it as it is very annoying. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1290002 Title: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1290002/+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 1316873] [NEW] Left mouse button stops working
Public bug reported: This problem has plagued me for a few years across different laptops and Ubuntu versions. Current I am experiencing this on a Dell Inspiron 15z running Ubuntu 14.04 LTS. It typically starts after I have used the chat or call feature in gmail, by clicking on the phone icon in the left chat margin. I am a Firefox user and have not tested this with chrome etc. It has not happened if i dont install google-talkplugin so it is quite possible that the plugin is to blame. Symptom === The left mouse button on all attached mice - USB , Trackpad and touch - will not do anything however the right mouse button continues to work. This happens to all applications and also to the desktop. The keyboard continues to function as normal. When this occurs , my solution is to Alt-F4 close all windows and log out of the X session. When I re-login the left mouse button works as normal. This is an irritant and work disruptor as I have to save all browser and desktop applications to safe state before I logout to reset the mouse. I will appreciate any soltion or workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 6 21:41:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058f] InstallationDate: Installed on 2014-04-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5523 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 6 21:20:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty 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/1316873 Title: Left mouse button stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1261916] Re: Missing letters in spice client session with KVM guest
If the graphics drivers on the system running spice viewer are relevant, it's the nvidia 304-updates. I mention this because the nature of the 'visual static' or 'visual artifacts' seems to change when moving from one to another multi-head monitor. However the missing letters remain unchanged no matter the monitor, no matter whether ending and restarting virt-viewer and virt-manager. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1261916 Title: Missing letters in spice client session with KVM guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1261916] Re: Missing letters in spice client session with KVM guest
"Installation has finished. ou can continue testing ubuntu now," (should be 'You' and 'Xubuntu'.The two buttons are titled 'Continue esting' and 'Restart ow'.The icons on the home screen have changed to 'rash' 'ile system' 'ome' nad 'Install ubuntu 14.0'. Looks to be a strange bug to do with highlighting letters for keyboard shortcuts --- sort of. There are strange little graphics artifacts here and there as well. There must be something else going on too since the updated messages listing what was being installed or removed repeated bits of earlier messages while displaying nothing of what presently was being installed or removed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1261916 Title: Missing letters in spice client session with KVM guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1261916] Re: Missing letters in spice client session with KVM guest
This problem happens 'out of the box' using nothing more xubuntu trusty iso installed on two systems, one running virt-manager and the other hosting vms. So far, so good. To reproduce: try a standard xubuntu amd64 install on a vm guest using qxl as the video driver and spice as the display system. Somewhere during the install questions to do with disk use, every second or thid letter randomly just disappears. "Removing firefo " a few dozen times,. Removing kpart redisplayed a few dozen times. The 'Thank you we'd love to hear about your experiences' screen has title "In ta". Trusty / qxl / spice on vm guests is compeltely unusable. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-qxl in Ubuntu. https://bugs.launchpad.net/bugs/1261916 Title: Missing letters in spice client session with KVM guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-qxl/+bug/1261916/+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 1039523] Re: Mouse Scroll Wheel not working in spice vm guests
On 04/02/2014 10:36 PM, Christopher M. Penalver wrote: > Michal Suchanek / Harry Coin, thank you for your comment. So your hardware > and problem may be tracked, could you please file a new report by executing > the following in a terminal: > ubuntu-bug xorg > > Please ensure you have xdiagnose installed, and that you click the Yes > button for attaching additional debugging information. > > For more on this, please see the official Ubuntu documentation: > Ubuntu X.Org Team, Ubuntu Bug Control, and Ubuntu Bug Squad: > https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue > Ubuntu Community: > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > > When opening up the new report, please feel free to subscribe me to it. > > Please note, not filing a new report will delay your problem being > addressed as quickly as possible. > > Thank you for your understanding. > > ** Changed in: xserver-xorg-input-evdev (Ubuntu) > Status: Confirmed => Incomplete > I tried it out with trusty beta 2 with exactly the same results as saucy -- no scroll wheel operation. However, I have found a major clue. do: service spice-vdagent stop and the scroll wheel works (but cuttting and pasting and related is broken). and after service spice-vdagent start the scroll wheel stops again, but cutting and pasting works. There is some sort of fight between spice-vdagent and the evdev xorg driver. -- 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/1039523 Title: Mouse Scroll Wheel not working in spice vm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+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 1301722] Re: Mouse Scroll Wheel not working in spice vm guests
** Bug watch added: Red Hat Bugzilla #805902 https://bugzilla.redhat.com/show_bug.cgi?id=805902 -- 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/1301722 Title: Mouse Scroll Wheel not working in spice vm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1301722/+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 1301722] Re: Mouse Scroll Wheel not working in spice vm guests
As I use xubuntu, (standard ubuntu is way too 'heavy' for our purpose) is there a version from that world you can suggest? Whatever the regular ubuntu results it won't help me. On 04/03/2014 08:50 PM, Christopher M. Penalver wrote: > Harry Coin, could you please test for this with the latest development > release of Ubuntu? ISO images are available from > http://cdimage.ubuntu.com/daily-live/current/ . > > If it remains an issue, could you please just make a comment to this. > > Thank you for your understanding. > > Helpful bug reporting tips: > https://wiki.ubuntu.com/ReportingBugs > > ** Description changed: > > - > - https://bugs.launchpad.net/bugs/1039523 > - > - > - Im runnning Precise in various qemu-kvm virtual machines with Spice. > - > - The ScrollWheel stops working in the virtual machine as soon the > spice-vdagent gets started. > - After killing the spice-vdagent process the Scroll Wheel works again. > - Seems to be an evdev Bug, see solved Fedora Bug: > - > - https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=805902 > - Michal Suchanek / Harry Coin, thank you for your comment. So your hardware > and problem may be tracked, could you please file a new report by executing > the following in a terminal: > - ubuntu-bug xorg > + I'm running Precise in various qemu-kvm virtual machines with Spice. The > ScrollWheel stops working in the virtual machine as soon the spice-vdagent > gets started. After killing the spice-vdagent process the Scroll Wheel > works again. > + Seems to be an evdev Bug, see solved Fedora Bug: > + https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=805902 > >ProblemType: Bug >DistroRelease: Ubuntu 13.10 >Package: xorg 1:7.7+1ubuntu6 >ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 >Uname: Linux 3.11.0-18-generic x86_64 >ApportVersion: 2.12.5-0ubuntu2.2 >Architecture: amd64 >CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' >CompositorRunning: None >Date: Wed Apr 2 22:55:21 2014 >DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job >DistroCodename: saucy >DistroVariant: ubuntu >ExtraDebuggingInterest: Yes, if not too technical >GraphicsCard: > - Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) > -Subsystem: Red Hat, Inc Device [1af4:1100] > + Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) > +Subsystem: Red Hat, Inc Device [1af4:1100] >InstallationDate: Installed on 2013-05-26 (311 days ago) >InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 > (20130423.1) >LightdmGreeterLog: > - ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions > directory: Error opening directory '/usr/share/lightdm/remote-sessions': No > such file or directory > - > - ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: > Failed to open file '/home/harry/.face': No such file or directory > + ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions > directory: Error opening directory '/usr/share/lightdm/remote-sessions': No > such file or directory > + > + ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: > Failed to open file '/home/harry/.face': No such file or directory >Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub >MachineType: Bochs Bochs >MarkForUpload: True >ProcEnviron: > - LANGUAGE=en_US > - TERM=xterm > - PATH=(custom, no user) > - LANG=en_US.UTF-8 > - SHELL=/bin/bash > + LANGUAGE=en_US > + TERM=xterm > + PATH=(custom, no user) > + LANG=en_US.UTF-8 > + SHELL=/bin/bash >ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic > root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7 >SourcePackage: xorg >UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago) >dmi.bios.date: 01/01/2011 >dmi.bios.vendor: Bochs >dmi.bios.version: Bochs >dmi.chassis.type: 1 >dmi.chassis.vendor: Bochs >dmi.modalias: > dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: >dmi.product.name: Bochs >dmi.sys.vendor: Bochs >version.compiz: compiz N/A >version.ia32-libs: ia32-libs N/A >version.libdrm2: libdrm2 2.4.46-1ubuntu1 >version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 >version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A >version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 >version.x
[Ubuntu-x-swat] [Bug 1301722] [NEW] Mouse Scroll Wheel not working in spice vm guests
Public bug reported: https://bugs.launchpad.net/bugs/1039523 Im runnning Precise in various qemu-kvm virtual machines with Spice. The ScrollWheel stops working in the virtual machine as soon the spice-vdagent gets started. After killing the spice-vdagent process the Scroll Wheel works again. Seems to be an evdev Bug, see solved Fedora Bug: https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=805902 Michal Suchanek / Harry Coin, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report by executing the following in a terminal: ubuntu-bug xorg ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 2 22:55:21 2014 DistUpgraded: 2013-10-21 18:32:59,232 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Device [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2013-05-26 (311 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) LightdmGreeterLog: ** (lightdm-gtk-greeter:25761): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory ** (lightdm-gtk-greeter:25761): WARNING **: Failed to load user image: Failed to open file '/home/harry/.face': No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-18-generic root=UUID=adda9701-5de5-45dd-9068-ce97f8259354 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-21 (163 days ago) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Fri Mar 28 12:35:38 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 inputspice vdagent tablet TOUCHSCREEN, id 9 xserver.errors: Failed to load module "evdec" (module does not exist, 0) Failed to load module "evdec" (module does not exist, 0) No input driver matching `evdec' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 0 vendor QXL xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy 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/1301722 Title: Mouse Scroll Wheel not working in spice vm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1301722/+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 1039523] Re: Mouse Scroll Wheel not working in spice vm guests
Still broken in saucy. ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: Expired => Confirmed -- 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/1039523 Title: Mouse Scroll Wheel not working in spice vm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+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 1290002] [NEW] Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update
Public bug reported: Description:Ubuntu 12.04.4 LTS Release:12.04 I run update on Ubuntu 12.04 64Bit on 2014-03-07, and after restarting my pc, the keyboard volume wheel doesn't adjust the volume in Ubuntu OS anymore. Keyboard is Dell X295D Multimedia USB Keyboard (Greek) I can confirm that the volume wheel is not malfunctioned because the volume wheel trigger is detectable in Settings>Keyboard>Shortcuts>Sound and Media>Volume Down/Volume Up, and it is also working in other programs (XBMC for Ubuntu). The packages included in the update are: Install: linux-image-3.2.0-60-generic:amd64 (3.2.0-60.91), linux-headers-3.2.0-60:amd64 (3.2.0-60.91), linux-headers-3.2.0-60-generic:amd64 (3.2.0-60.91) Upgrade: libmagickcore4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), gnome-settings-daemon:amd64 (3.4.2-0ubuntu0.6.4, 3.4.2-0ubuntu0.6.5), icedtea-netx:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), libmagickwand4:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), linux-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), libmagickcore4-extra:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), libgnutls26:amd64 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), libgnutls26:i386 (2.12.14-5ubuntu3.6, 2.12.14-5ubuntu3.7), xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5), icedtea-netx-common:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), icedtea-6-plugin:amd64 (1.2.3-0ubuntu0.12.04.3, 1.2.3-0ubuntu0.12.04.4), imagemagick-common:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), linux-headers-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), linux-image-generic:amd64 (3.2.0.59.70, 3.2.0.60.71), libdvdnav4:amd64 (4.2.0-1, 4.2.0-1ubuntu0.1), imagemagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3), linux-libc-dev:amd64 (3.2.0-59.90, 3.2.0-60.91), perlmagick:amd64 (6.6.9.7-5ubuntu3.2, 6.6.9.7-5ubuntu3.3) ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update to xkb-data:amd64 (2.5-1ubuntu1.3, 2.5-1ubuntu1.5) + Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1290002 Title: Volume wheel (Dell keyboard) not adjusting Ubuntu volume properly after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1290002/+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 1247535] [NEW] crash on startup
Public bug reported: crash on startup ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-32.47-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Nov 3 17:35:14 2013 DistUpgraded: 2013-10-20 19:13:14,565 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:2557] MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-32-generic root=UUID=8a3bdd1e-0357-4a28-91bc-33b6d74b3479 ro vesafb.invalid=1 nopat SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-20 (13 days ago) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sun Nov 3 17:25:13 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy 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/1247535 Title: crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1247535/+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 1187500] Re: [Saucy] Unity is slow on Intel graphics
perfectly fixed. Thank you very much -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1187500 Title: [Saucy] Unity is slow on Intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1187500/+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 1039523] Re: Mouse Scroll Wheel not working in spice vm guests
** Summary changed: - Mouse Scroll Wheel not working + Mouse Scroll Wheel not working in spice vm guests -- 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/1039523 Title: Mouse Scroll Wheel not working in spice vm guests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+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 1039523] Re: Mouse Scroll Wheel not working
I found that doing: mkdir ~/shouldhavebeendoneatcanonicalalongtimeago cd ~/shouldhavebeendoneatcanonicalalongtimeago apt-get source xserver-xorg-input-evdev apt-get build-dep xserver-xorg-input-evdev http://cgit.freedesktop.org/xorg/driver/xf86-input-evdev/log/ download and unpack the tar at [head], cp -r (overwrite) the contents of the xserver-xorg with the newer stuff cd xserver-xorg... rm debian/patches/* debchange -n (put in a remark as to the date of the fix) dpkg-buildpackage -b in the vm, install the result (dpkg -i ../(latest deb there).deb and ... scrolling once again works in vms where it was broken before. I've tried to attach the .deb for amd_64 with this post. ** Attachment added: ".deb compiled using source as of 5/27/13" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+attachment/3688188/+files/xserver-xorg-input-evdev_2.7.3-0ubuntu2b2.1_amd64.deb -- 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/1039523 Title: Mouse Scroll Wheel not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1039523/+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 1175795] [NEW] desk top
Public bug reported: can't set desktop background no background at all ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri May 3 07:25:44 2013 DistUpgraded: 2013-04-26 20:04:05,546 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.012, 3.8.0-19-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Turks XT [Radeon HD 6670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:2557] InstallationDate: Installed on 2013-02-01 (90 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) JockeyStatus: kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietary, Disabled, Not in use) kmod:fglrx_updates - ATI Fire GL (Proprietary, Enabled, Not in use) MachineType: Gigabyte Technology Co., Ltd. GA-970A-D3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=8a3bdd1e-0357-4a28-91bc-33b6d74b3479 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to raring on 2013-04-26 (6 days ago) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F10 dmi.board.name: GA-970A-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF10:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-D3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-D3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri May 3 07:24:45 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 8 inputPlus More Enterprise LTD. USB-compliant keyboard KEYBOARD, id 9 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu6 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring 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/1175795 Title: desk top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1175795/+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 1037896] Re: Starting Firefox kills xserver immediately
Nvidia-graphics-drivers (nvidia-current) do not work with xserver_1.13 branch if a 3d desktop session is selected. Also when using a 2d desktop (like gnome classic), you cannot use firefox or thunderbird ATM. Not even the latest stable nvidia drivers (304.37) work. -- 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/1037896 Title: Starting Firefox kills xserver immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+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 1037896] Re: Starting Firefox kills xserver immediately
** Package changed: xserver-xorg-video-nouveau (Ubuntu) => nvidia- graphics-drivers (Ubuntu) -- 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/1037896 Title: Starting Firefox kills xserver immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037896/+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 992745] Re: X doesn't load in Quantal, downgrading libxfont1 to Precise version fixes it
Confirming this issue. Workaround goes by downgrading libxfont1 to the previous version (1.4.4-1). -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/992745 Title: X doesn't load in Quantal, downgrading libxfont1 to Precise version fixes it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/992745/+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 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
** Also affects: touchpad-indicator Importance: Undecided Status: New -- 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/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+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 550625] Re: Alps touchpad is recognized but synaptics clients and scrolling do not work
@Seth Thanks for the driver on post #466. for over a year now I've been using the imps hack in /etc/modprobe.d With this, I am even now able to use touchpad indicator as it correctly sees the touchpad as a touchpad and not a ps2 mouse. Thank you!!! I'm running Ubuntu 11.04 on an Acer TimelineX 3820TG. -- 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/550625 Title: Alps touchpad is recognized but synaptics clients and scrolling do not work To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/550625/+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 892862] Re: X is very slow
This is because your setup wasn,t able to load nvidia module, so nvidia-current is not in use. Instead your system did load nouveau module, the open source X driver. See this: [1284918.684] (EE) NVIDIA: Failed to load the NVIDIA kernel module. Please check your [1284918.684] (EE) NVIDIA: system's kernel log for additional error messages. [1284918.684] (II) UnloadModule: "nvidia" [1284918.684] (EE) Failed to load module "nvidia" (module-specific error, 0) [1284918.684] (II) LoadModule: "nouveau" [1284918.685] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so The version nvidia-current_280.13-0ubuntu6 and the version nvidia-current-updates_285.05.09-0ubuntu0.1 from the Oneiric official repositories both support xserver 1.10. -- 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/892862 Title: X is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/892862/+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 764379] Re: Partial screen corruption and poor performance on GeForce 6150
Hi Bryce, Unfortunately I no longer have the hardware I reported this bug on. You might want to close it for now. -- 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/764379 Title: Partial screen corruption and poor performance on GeForce 6150 To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/764379/+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 880449] Re: Problem with titlebar
-- 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/880449 Title: Problem with titlebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/880449/+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 880449] [NEW] Problem with titlebar
Public bug reported: When hiding all visible windows and making them visible again (via Ctrl+Alt+D) the titlebars of all windows are not clickable (i.e. when clicking on the titlebar of a window, it actually becomes unfocused and the click is picked up by the workspace desktop instead). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu3 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,wall,vpswitch,resize,gnomecompat,place,regex,compiztoolbox,resizeinfo,imgpng,move,session,snap,grid,animation,workarounds,fade,expo,unitymtgrabhandles,scale,ezoom,unityshell] CompositorRunning: compiz Date: Sun Oct 23 12:50:12 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.2, 3.0.0-12-generic-pae, i686: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0112] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:0112] MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic-pae root=UUID=488f3a84-6094-4dad-a6ab-d85c65610aed ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H67M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd02/21/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu5 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 oneiric running-unity 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/880449 Title: Problem with titlebar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/880449/+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 560433] Re: [clarkdale] Xorg freeze
"My guess is there is a bug in the video driver that shows when the 3d section of the video card is used." Yup, you are 100% correct there. I've forgotten about this bug - until you commented & I got the notification about it. I suffered from similar problem to you. But I managed to resolve it by installing the xorg-edgers PPA : https://launchpad.net/~xorg-edgers You might wish to try the driver first : https://launchpad.net/~xorg- edgers/+archive/drivers-only (I went for the whole setup though - Acer laptop here with Intel i915 chip) Another safer bet compared to the whole xorg-edgers is probably the Ubuntu-X PPA : https://launchpad.net/~ubuntu-x-swat/+archive/x-updates Hope it helps someone else. Good luck. -- 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/560433 Title: [clarkdale] Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/560433/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Hi Seth, One bad experience I have had since installing the patched kernel. After countless good boots I decided to add the following lines to /etc/tc.local in order to use switcheroo: chown "username" /sys/kernel/debug/vgaswitcheroo/switch # change "username" with your user name echo OFF > /sys/kernel/debug/vgaswitcheroo/switch Everything seemed to work for the first 5 or so boots but then I started getting the blackscreens again. The message was similar but not the same. Unfortunately I didn't manage to get a screen of it. Once I got back into my desktop I removed the lines from rc.local and then the issue disappeared. I've gone ahead and added the lines again to see if I can recreate the issue but so far nothing. Not sure if this info is of any use to you at all but I thought I would share just in case it would. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Cool! it seems to be working for me. I even got a little taste of the Plymouth boot screen which I haven't seen in a long time :) I'll continue testing and let you know if I experience the B[lack]SOD. On Fri, Aug 26, 2011 at 8:19 PM, josejuan05 <727...@bugs.launchpad.net>wrote: > I have 20 consecutive successful boots on this commit. I have no boot > failures yet. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/727620 > > Title: > [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in > normal boot (Hybrid graphics) > > Status in The Linux Kernel: > Confirmed > Status in X.org XServer - ATI gfx chipset driver: > Confirmed > Status in “linux” package in Ubuntu: > Incomplete > Status in “xserver-xorg-video-ati” package in Ubuntu: > Invalid > > Bug description: > [Problem] > On hybrid graphics hardware with this ATI chip and another (e.g. Intel), a > failure occurs resulting in a black screen and errors from the radeon kernel > module, as shown below. > > [Cause] > From upstream developer: > > "The switcheroo code needs more work to switch properly on some > systems it seems. There are a set acpi methods required to > activate/deactivate the respective gpus. The drivers need to load and > initialize active hw. If the hw is not active when the driver loads, > then the hw is not set up properly and it won't work. Probably some > ordering issues in how the switcheroo acpi methods are called." > > [Workarounds] > Several options: > > 1. If your BIOS includes functionality to disable the Intel card, use > BIOS settings to select which chip to load. > > 2. Disable KMS by adding `radeon.modeset=0` in the boot line. Note > that the default radeon gallium driver only works with KMS, so YMMV. > > [Original Report] > I'm running natty, and every since the upgrade to 6.14.0 I've been unable > to consistently boot. After some discussion in the forums, I tried > repeatedly to boot into recovery mode. In most cases, I got a black screen. > One time though, when I was able to successfully increase the brightness, I > saw some errors from the radeon module. I took a photo (available at > http://i.imgur.com/P0bQ0.jpg), and here's the stack and call trace, as > best as I can read it: > > Stack: > 880149eb8000 880149eb8000 0011 0911 > fff4 88014b6c7800 88014b0f7b58 a022aba0 > 8801460f7b58 880149eb8000 00410028 > Call Trace: > [] evergreen_cp_resume+0x3a0/0x630 [radeon] > [] evergreen_startup+0x157/0x260 [radeon] > [] ? r600_pcie_gart_init+0x60/0x70 [radeon] > [] evergreen_init+0x1ac/0x2d0 [radeon] > [] radeon_device_init+0x409/0x490 [radeon] > [] radeon_driver_load_kms+0xb2/0x1a0 [radeon] > [] drm_get_pci_dev+0x18e/0x300 [drm] > [] ? kmem_cache_alloc_trace+0xff/0x120 > [] radeon_pci_probe+0xb2/0xba [radeon] > [] local_pci_probe+0x5f/0xd0 > [] pci_device_probe+0x119/0x120 > [] ? driver_sysfs_add+0x7a/0xb0 > [] really_probe+0x68/0x190 > [] driver_probe_device+0x45/0x70 > [] __driver_attach+0xab/0xb0 > [] ? __driver_attach+0x0/0xb0 > [] bus_for_each_dev+0x5e/0x90 > [] driver_attach+0x1e/0x20 > [] bus_add_driver+0xc5/0x280 > [] ? radeon_init+0x0/0x1000 [radeon] > [] driver_register+0x76/0x140 > [] ? radeon_init+0x0/0x1000 [radeon] > [] __pci_register_driver+0x56/0xd0 > [] drm_pci_init+0xe4/0xf0 [drm] > [] ? mutex_lock+0x1e/0x50 > [] ? radeon_init+0x0/0x1000 [radeon] > [] drm_init+0x58/0x70 [drm] > [] radeon_init+0xc4/0x1000 [radeon] > [] do_one_initcall+0x45/0x190 > [] sys_init_module+0x103/0x260 > [] system_call_fastpath+0x16/0x1b > Code: 00 45 8b 84 24 e4 0a 00 00 45 85 c0 0f 8e c7 09 00 00 41 8b 84 24 d4 > 0a 00 00 89 c2 83 c0 01 40 c1 e2 02 49 03 94 24 c8 0a 00 00 02 00 44 05 > c0 41 8b 94 24 e4 0a 00 00 41 23 84 24 f4 0a 00 > RIP [] evergreen_cp_start+0x57/0xc80 [radeon] > RSP > CRZ: c90411ce1ffc > ---[ end trace 37702c56f2e23247 ]--- > udevd-work[94]: '/sbin/modprobe -bv > pci:v1002d68C1sv103Csd1436bc03sc00i00' unexpected exit with > status 0x0009 > > There is also some register info dumped at the top of the screen > visible in the photo, that I didn't bother to write, as I'd most > certainly get something wrong. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/linux/+bug/727620/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to
[Ubuntu-x-swat] [Bug 821702] Re: [Oneiric] Nvidia-current 280.13 hangs up the system
The latest cairo update (v. 1.10.2-6ubuntu3) fixes this issue for now as it is a non gl build. -- 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/821702 Title: [Oneiric] Nvidia-current 280.13 hangs up the system To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/821702/+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 821702] Re: [Oneiric] Nvidia-current 280.13 hangs up the system
** Description changed: The latest stable nvidia-current from Oneiric repos (280.13-0ubuntu1) hangs up my system. - This happens every time I start synaptic. - Then, if I try to close it, it won't close until the system asks to force quit it. - Then, however, the whole system hangs (speeding up CPU). + This happens every time after I have started synaptic. + Then, if I try to close this application, it won't close until the system asks to force quit it. + Then, however, the whole system hangs (also speeding up CPU). If I then try to shut down or reboot, I get a message saying terminal is not responding. So somehow terminal process does not appear to shut down. - This is easy to reproduce, as it happens each time I install nvidia- + This is easy to reproduce, as it happens every time with nvidia- current_280.13. The previous version 275.09.07-0ubuntu4 works just fine. In addition to this, also the beta version 280.04 (from xorg-edgers) works OK. - However, the later beta 280.11 will also hang up my system just like 280.13 does. + However, the later beta 280.11 will also hang up just like 280.13 does. + + This issue seems to be related to cairo and particularly enabling gl support. + This feature was applied to cairo from the version 1.10.2-6ubuntu1. + Downgrading cairo to earlier version (1.10.2-2ubuntu4) solves the issue. + This leads to the conclusion that nvidia-current is incompatible with gl enabled cairo. I have a fully updated 64-bit Oneiric-alfa3 Mobo: Gigabyte GA-MA790XT-UD4P Graphics card: XFX GTX285 1 GB -- 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/821702 Title: [Oneiric] Nvidia-current 280.13 hangs up the system To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/821702/+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 821702] Re: [Oneiric] Nvidia-current 280.13 hangs up the system
So I have done some more testing now. NVidia proprietary drivers are really not compatible with libgl-mesa build which is gl-enabled. This is the issue. Workaround: I installed the latest cairo build from Oneiric official repos, that is a non gl build (1.10.2-2ubuntu4). Then I installed the latst nvidia-current from Oneiric official repos (280.13-0ubuntu1). everything works now fine, without any hang-ups and without any high speeding up CPU problems. ** Also affects: cairo Importance: Undecided Status: New -- 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/821702 Title: [Oneiric] Nvidia-current 280.13 hangs up the system To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/821702/+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 821702] [NEW] [Oneiric] Nvidia-current 280.13 hangs up the system
Public bug reported: The latest stable nvidia-current from Oneiric repos (280.13-0ubuntu1) hangs up my system. This happens every time I start synaptic. Then, if I try to close it, it won't close until the system asks to force quit it. Then, however, the whole system hangs (speeding up CPU). If I then try to shut down or reboot, I get a message saying terminal is not responding. So somehow terminal process does not appear to shut down. This is easy to reproduce, as it happens each time I install nvidia- current_280.13. The previous version 275.09.07-0ubuntu4 works just fine. In addition to this, also the beta version 280.04 (from xorg-edgers) works OK. However, the later beta 280.11 will also hang up my system just like 280.13 does. I have a fully updated 64-bit Oneiric-alfa3 Mobo: Gigabyte GA-MA790XT-UD4P Graphics card: XFX GTX285 1 GB ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- 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/821702 Title: [Oneiric] Nvidia-current 280.13 hangs up the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/821702/+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 813581] Re: libdrm-nouveau1a
You cannot remove that package. The mesa package libgl1-mesa-dri depends on all three libdrm packages (libdrm-intel1, libdrm-nouveau1a, libdrm-radeon1). The main xserver (xserver-xorg-core) depends on those same three libdrm packages (via libdrm2). Thus xserver, drm and mesa are linked together. -- 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/813581 Title: libdrm-nouveau1a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/813581/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Sorry to sound stupid, but I think there are many people affected by this in layman terms, what's the status of this issue? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+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 798049] Re: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative
I can confirm the nvidia-current_275-09-07-0ubuntu2 works with mesa_7.10.3-0ubuntu1. That first mesa 7.10.3 build does not break the 275.09 series nvidia-current. The breakage was added to the later builds. So now we need to remove the breakage from the newest mesa_7.10.3. However, nvidia-current_275.09.07-0ubuntu2 works only if it is installed after the mesa packages. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798049 Title: nvidia-* and fglrx need to be migrated to per-architecture gl_conf alternative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/798049/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
@Seth You wouldn't know how to fix this would you? :) I do worry about it though as i am constantly having to reboot many times until I finally get into Ubuntu. It's annoying as well as embarrassing around my Mac and Window using colleagues. They think I'm an idiot for using Ubuntu... maybe I am? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
@Seth I still can't seem to find the error message that I see on boot freeze in the logs. I tired taking a photo of it. Maybe it'll help? uname -a Linux ClarifyUbuntu 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "screens of the error" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/727620/+attachment/2173263/+files/error..zip -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/727620/+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 798007] Re: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
There is another bug report on this very same issue: Bug #798049 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798007/+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 798049] Re: nvidia-current needs to be migrated to per-architecture gl_conf alternative
*** This bug is a duplicate of bug 798007 *** https://bugs.launchpad.net/bugs/798007 ** This bug has been marked a duplicate of bug 798007 [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798049 Title: nvidia-current needs to be migrated to per-architecture gl_conf alternative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798049/+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 798007] Re: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
Bryce, I am sorry but I do not have apport installed. I am using a very minimalistic setup. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798007/+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 798007] Re: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
One more note. The package libgl1-mesa-glx 7.10.3-0ubuntu1 breaks: fglrx (<= 2:8.850-0ubuntu1) nvidia-173 (<= 173.14.30-0ubuntu2) nvidia-current (<= 270.41.19-0ubuntu1) However, as I said above, I use nvidia-current_275.09.07, which is the latest stable in Oneiric official repos. Thus the installation (apt) should not even have broken anything. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798007/+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 798007] Re: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
Chris, No, apt did not remove anything nor did suggest it. I did the upgrade with synaptic, so nothing wrong about that (no errors). There was only the notification to upgrade xorg-server to the version 1.10.2 first, which is a new dependency. But as I mentioned, I downgraded the mesa back to 7.10.2 and all is OK now. I may try later today the mesa 7.11.0 tree and libdrm 2.4.26 tree from Xorg-edgers PPA. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798007/+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 798007] [NEW] [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current
Public bug reported: Latest mesa upgrade from 7.10.2 to 7.10.3 breaks 3D capabilites. Gnome-shell falls back to gnome-panel. This happens in my setup with Nvidia graphics card and latest nvidia-current (275.09.07) in use. The .xsession-errors file gives this message: gnome-session-is-accelerated: No hardware 3D support. gnome-session-check-accelerated: Helper exited with code 256 gnome-session[1113]: WARNING: Session 'gnome' runnable check failed: Exited with code 1 So 3D is not anymore working with 7.10.3 mesa. Downgrading to 7.10.2 solves this issue. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/798007 Title: [Oneiric] Latest mesa (7.10.3) breaks 3D with nvidia-current To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/798007/+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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
@Seth, Does it matter that the error occurs before the drives are mounted? I'm not sure it's actually saving the log when the error occurs. Either way, on the next occurrence, I'll send this log. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) ___ 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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
Seth, yeah I'm on natty. Can you help me identify the log you need? I'm not sure which is relevant. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) ___ 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 727620] Re: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics)
I just wanted to add that with the HD5650 on an Acer Aspire I have the same issues. One thing that doesn't seem to get mentioned here much is the vesafb. More than half the time I boot I get an error stating that their was an error inserting vesafb. I sometimes also receive an error stating that the module vesafb.ko was not found. Either way, the system fails to boot. I have no idea if this information is being output to a log somewhere as it seems to occur even before the filesystems are mounted. Can someone suggest to me which log to look for? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/727620 Title: [Radeon HD 5650 and 5470] Kernel BUG during recovery boot and in normal boot (Hybrid graphics) ___ 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 776978] Re: everything on screen is garbled apart from the top bar (2 monitors, different resolutions, unity, natty)
Just an observation... In my dual boot environment (Windows7 and Ubuntu) the longer I stay in Ubuntu without switching Windows the worse and more frequent my video issues happen. Once I log into windows, even if just for a minute, when I boot back into Ubuntu, I am then able to add a monitor without problem. It also seems to help with the other issues I have such as crashing on sleep mode. -- 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/776978 Title: everything on screen is garbled apart from the top bar (2 monitors, different resolutions, unity, natty) ___ 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 764379] Re: Partial screen corruption and poor performance on GeForce 6150
** Also affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- 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/764379 Title: Partial screen corruption and poor performance on GeForce 6150 ___ 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 649809] Re: the session settings manager can try starting before the login screen one exits
The excellent video of Lucazade shows clearly how gnome-settings daemon first works, but is then killed. It really may be that gnome-settings-daemon somehow is still hanging after first login, but is killed after a new logout/login. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/649809 Title: the session settings manager can try starting before the login screen one exits ___ 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 649809] Re: the session settings manager can try starting before the login screen one exits
I can confirm the race situation is fixed with this new package in PPA. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in Ubuntu. https://bugs.launchpad.net/bugs/649809 Title: the session settings manager can try starting before the login screen one exits ___ 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 650539] Re: SRU: Launching a Qt app crashes X when using Xinerama
It's been almost three weeks since my post. Any chance this issue could get fixed soon? After all the patch exists already so there's not much to do but to apply and release it. This is easily solved but very important to us because Xorg seem to update every now and then and when updated everyone has to patch the new version. -- 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/650539 Title: SRU: Launching a Qt app crashes X when using Xinerama ___ 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 724921] Re: Please upgrade nvidia-current to v. 270.29
This wish has been fixed with the upgrade of nvidia-graphics- drivers_270.29-0ubuntu2. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Fix Released -- 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/724921 Title: Please upgrade nvidia-current to v. 270.29 ___ 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 724921] [NEW] Please upgrade nvidia-current to v. 270.29
Public bug reported: Nvidia proprietary dirvers in Natty repos (nvidia-current v. 260.19.29) do not support the latest xserver 1.10 rc2 in Natty repos. So please upgrade the nvidia-current to the latest beta (version 270.29) to get the support for this X 1.10 rc2. This driver is available from X Updates PPA and it works very well with the most recent Natty fully upgraded. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- 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/724921 Title: Please upgrade nvidia-current to v. 270.29 ___ 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 650539] Re: SRU: Launching a Qt app crashes X when using Xinerama
> I am still seeing this issue in 2:1.9.0-oubuntu7.3 using the NVIDIA
> driver version NVIDIA-Linux-x86-260.19.12 or NVIDIA-Linux-x86-260.19.29
No wonder. I verified the issue exists still by doing this:
$ apt-get source xserver-common
$ zgrep -A2 -B2 650539 xorg-xserver_1.9.0-0ubuntu7.3.diff.gz
+ * debian/patches/207_Xext_panoramiXprocs_fix_typo.patch:
+- This prevents Qt applications from crashing when using
+ Xinerama multi-head with drivers such as nvidia (LP: #650539).
+
+ -- Alberto Milone Mon, 22 Nov 2010 18:55:50
+0100
So it is reported to be fixed in the change log.
$ grep -A4 "pDst == screenInfo" xorg-xserver-1.9.0/Xext/panoramiXprocs.c
if((pDst == screenInfo.screens[0]->root) ||
(pWin->drawable.id == screenInfo.screens[0]->screensaver.wid))
{
rep.dstX += screenInfo.screens[0]->x;
rep.dstY += screenInfo.screens[0]->y;
So if compared to the original patch (https://launchpad.net/~jared-
bunting/+archive/xorg-xserver-650539), it is not fixed, only falsely
reported to be fixed.
I'd really liked to see this fix included soon and before next Ubuntu is
released. Althought I'm sure the history still continues to repeat
itself and this will not get fixed before Ubuntu 11.04. Then the Ubuntu
11.04 version will break the multimonitor setup of Xorg (or something
related) again and the fixing takes again more than releasing even next
Ubuntu 11.10 and so on. That's the neverending cycle that have been past
i-cannot-even-remember-how-many Ubuntus. I guess it's just so rare to
use multimonitor setup that they don't test it before release.
--
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/650539
Title:
SRU: Launching a Qt app crashes X when using Xinerama
___
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 710247] Re: Xorg crashes at all
*** This bug is a duplicate of bug 709977 *** https://bugs.launchpad.net/bugs/709977 Yes it is the bug # 709977 Backtrace: [11.120] 0: /usr/bin/X (xorg_backtrace+0x26) [0x45be16] [11.120] 1: /usr/bin/X (0x40+0x59c9a) [0x459c9a] [11.120] 2: /lib/libpthread.so.0 (0x7f1732a1a000+0xfc80) [0x7f1732a29c80] [11.120] 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f172d89f000+0x639d) [0x7f172d8a539d] [11.120] 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f172d89f000+0x439d) [0x7f172d8a339d] [11.120] 5: /usr/bin/X (0x40+0x87897) [0x487897] [11.120] 6: /usr/bin/X (NewInputDeviceRequest+0x3b7) [0x487e87] [11.120] 7: /usr/bin/X (0x40+0x80588) [0x480588] [11.120] 8: /usr/bin/X (0x40+0x80b3e) [0x480b3e] [11.120] 9: /usr/bin/X (config_init+0x9) [0x469349] [11.120] 10: /usr/bin/X (InitInput+0x95) [0x466ee5] [11.120] 11: /usr/bin/X (0x40+0x218d6) [0x4218d6] [11.120] 12: /lib/libc.so.6 (__libc_start_main+0xfe) [0x7f1731983d1e] [11.120] 13: /usr/bin/X (0x40+0x214b9) [0x4214b9] [11.120] Segmentation fault at address 0x1010 [11.120] Caught signal 11 (Segmentation fault). Server aborting ** This bug has been marked a duplicate of bug 709977 Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so * You can subscribe to bug 709977 by following this link: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/709977/+subscribe -- 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/710247 Title: Xorg crashes at all ___ 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 710217] Re: [i915] Screen goes blank after splash.
*** This bug is a duplicate of bug 709977 *** https://bugs.launchpad.net/bugs/709977 This segfaulting bug has been fixed with a new evdev driver. Old driver: 2.6.0-1ubuntu1 New driver: 2.6.0-1ubuntu2 Bug #709977 ** This bug has been marked a duplicate of bug 709977 Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so * You can subscribe to bug 709977 by following this link: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/709977/+subscribe -- 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/710217 Title: [i915] Screen goes blank after splash. ___ 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 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so
** Package changed: xorg-server (Ubuntu Natty) => xserver-xorg-input- evdev (Ubuntu Natty) -- 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/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so ___ 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 709977] Re: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so
I very much doubt this is a bug in xorg-server (xserver 1.9 series). The crash ([ 11.710] segmentation fault at address 0x1010) happens very clearly with Nvidia graphics cards and with nvidia-current binary drivers. In fact with nvidia, the system will not even boot to gdm. Also using wireless or bluetooth mouse causes x to crash. But it is important to notice that this happens only with xserver-xorg-input-evdev_2.6.0 input driver (controlling mouse and kb). Downgrading to previous version (2.3.2) fixes this completely. This has also been tested with vanilla xserver-xorg-input-evdev (2.6.0) in Arch Linux and xserver 1.9.3 with same results. So this is not Ubuntu-specific issue. This might not even be a bug at all. Evdev 2.6.0 might simply not support xserver 1.9. Note, that evdev works well with xserver 1.10 series. This can also be tested with the packages in xorg-edgers PPA. The only issue, which can be considered a bug, is that this evdev driver (2.6.0) in Natty official repos: - depends erraneously on virtual package xorg-input-abi-11 (which refers to xserver 1.9 series as a matter of fact) - provides erraneously a virtual package xserver-xorg-input-11 (also refering to xserver 1.9 series). Correct dependency is xorg-input-abi-12 and correct provided package is xserver-xorg-input-12. This way this evdev 2.6.0 could not be even installed on systems with xserver 1.9. -- 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/709977 Title: Xorg crashed with SIGSEGV in RemoveDevice() - segfault at 1010 error 4 in evdev_drv.so ___ 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 649809] Re: Meerkat (10.10) does not apply theme properly
With NVidia GTX 285, Natty-64 bit, workaround #68 did really fix this theme issue. Confirming, it is a gdm bug. ** Tags added: natty -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. https://bugs.launchpad.net/bugs/649809 Title: Meerkat (10.10) does not apply theme properly ___ 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 703688] Re: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa)
Anyway this drivers offers a preliminary support for xserver 1.10, not full support. -- 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/703688 Title: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa) ___ 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 703688] Re: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa)
Yes I can confirm this error occuring with the nvidia-current_270.18 and xserver 1.9.99.901 (1.10 rc1). GLX module shared object (libglx.so) does not support server ABI and loading fails. This happens even if "IgnoreABI" is used. If "IgnoreABI" is not used in xorg.conf, gdm and x are not loaded (boot stops showing plymouth). This means compiz is out of work. Seems to be a bug in the binary driver, though. -- 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/703688 Title: [Natty] Need X-server 1.10-compatible nvidia driver (xorg-edgers ppa) ___ 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 692134] Re: Please update nvidia-current to the latest stable version
The fix has been released in Natty: nvidia-current_260.19.29-0ubuntu1 ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Fix Released -- 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/692134 Title: Please update nvidia-current to the latest stable version ___ 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 692134] [NEW] Please update nvidia-current to the latest stable version
Public bug reported: In Natty repos we have the version nvidia-current_260.19.21. However Nvidia Corporation has raised the status of the version 260.19.29 to stable. This has been published on 2010.12.13. Users can find the stable version also in the Xorg-Edgers PPA. Here are the release highlights: Added support for the following GPUs: GeForce GTX 460 SE GeForce GTX 570 Quadro 5000M NVS 300 Fixed a bug that caused some OpenGL applications to become unresponsive for up to a minute on some GPUs when changing the resolution or refresh rate. Added support for NVIDIA 3D Vision Pro. See the "Stereo" X configuration documentation in the README for further details. Added a new X configuration option "3DVisionProConfigFile" to allow user provide a filename which NVIDIA X driver uses to store 3D Vision Pro configuration settings. See "Appendix B. X Config Options" in the README for more information. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- 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/692134 Title: Please update nvidia-current to the latest stable version ___ 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 686070] Re: black screen (no more gdm/X server) with nvidia propriatery after gfxpayload=keep activation
And not even driver-by-driver basis, more like by graphics card basis. For me (with Nvidia 285 GTX) nvidia-current has always worked OK. Now I am using the latest beta from X-Updates (X-Swat): 260.19.26-0ubuntu1 And yes, I use the line "gfxpayload=keep" in my /etc/grub.d/00_header resulting a pretty plymouth. -- 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/686070 Title: black screen (no more gdm/X server) with nvidia propriatery after gfxpayload=keep activation ___ 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 683909] Re: Black screen at boot
*** This bug is a duplicate of bug 683775 *** https://bugs.launchpad.net/bugs/683775 ** This bug has been marked a duplicate of bug 683775 Natty Alpha 1, i915 has blank screen after boot * You can subscribe to bug 683775 by following this link: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/683775/+subscribe -- 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/683909 Title: Black screen at boot ___ 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 618253] Re: Error shown on screen after resume with radeon card
I'm also getting this error 1 out of 5 times during suspend on Maverick (kernel 2.6.35.4). Hardware: laptop: HP Compaq 6830s with ATI video. regards, Harry -- Error shown on screen after resume with radeon card https://bugs.launchpad.net/bugs/618253 You received this bug notification because you are a member of Ubuntu-X, which is the registrant for xserver-xorg-driver-ati. ___ 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
I have not seen any instability issues with the new beta driver 260.19.06 in my maverick 64-bit setup. The sluggishness issue is completely gone and also gnome-shell works fluently now. Please pay attention to that Brandon Snider has uploaded this new beta driver (nvidia-current) in X Updates PPA: https://launchpad.net/~ubuntu-x-swat/+archive/x-updates It is built both against lucid and maverick. Note also that the X updates lucid build cannot be installed on maverick. The lucid package nvidia-current provides virtual package xserver-xorg-video-6, which would break mavericks xserver 1.9. The maverick package nvidia-current provides virtual package xserver-xorg-video-8, suitable for xserver 1.9. Note also, that this is the way it should be. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
Yes I confirm what maba just wrote in comment #22. I only downloaded the packages nvidia-current and nvidia-settings from that PPA. Then I installed them with dpkg in terminal. There is no need to change sources.list that way. Anyway, the driver runs well in maverick too. The PPA itself is for Karmic and Lucid. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
Now that we have a fix for this bug, could perhaps Alberto Milone build this into maverick's repos. This sluggishness issue is after all quite an annoying one. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
NoahY, Like Daniel wrote (comment 10), this beta driver does not yet contain that bug fix. It will be included into the next version, perhaps into the stable 260 series driver. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
If you want to test this beta driver 260.19.04, you will find it here (X-Updates): https://launchpad.net/~ubuntu-x-swat/+archive/x-updates -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
And that might be an update to the newly released beta driver 260.19.04. See: http://www.phoronix.com/scan.php?page=news_item&px=ODU3NQ -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 630105] Re: Incompatibility with the new X.org 8.0 ABI
** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid -- Incompatibility with the new X.org 8.0 ABI https://bugs.launchpad.net/bugs/630105 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 630690] Re: Malformed patch, package nvidia-current 256.53-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build
Could perhaps Robert Hooker or Alberto Milone comment on this. The development of the kernel 2.6.36 is quite far now and a number of interested users might want to try it in Maverick. -- Malformed patch, package nvidia-current 256.53-0ubuntu1 failed to install/upgrade: nvidia-current kernel module failed to build https://bugs.launchpad.net/bugs/630690 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
Brian, this bug (X won't start since 1.9 update, no screens found) has been fixed and the fix has been released. I can confirm nvidia-current_256.53 fixes this bug. The performance issue is another bug and that one is dealt elsewhere, see the bug #629910 -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 630105] Re: Incompatibility with the new X.org 8.0 ABI
An addition, the link Opengeek provided in the description is outdated and way too complicated. It must also be noted that it is for Lucid (10.04) and not for Maverick (10.10). Experienced users may use terminal and "sudo apt-get" to install applications and drivers, but for beginners it is safer to use synaptic in order to resolve dependencies automatically. It gets even more complicated to download applications and to install them as local packages with "sudo dpkg -i". This will easily lead to broken packages if dependencies are not met. -- Incompatibility with the new X.org 8.0 ABI https://bugs.launchpad.net/bugs/630105 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 630105] Re: Incompatibility with the new X.org 8.0 ABI
Opengeek, The new nvidia-current_256.53 is not incompatible with the new xserver 1.9. What driver version are you using? If not v. 256-53, do an upgrade. -- Incompatibility with the new X.org 8.0 ABI https://bugs.launchpad.net/bugs/630105 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
Just out of curiosity, could this bug have something to do with desktop sluggishness that was observer to be caused by libcairo? The libcairo code was temporarily changed in order to overcome the incompatibility with nvidia-current back then. See the bug #605979 And one more thing. This bug does not in any way affect video performance. HD videos (1920:1080) run really well. -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629910] Re: nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
Yes I can confirm there is a regression issue with xserver 1.9 (at least up to 1.9.0-0ubuntu4) and nvidia-current (at least up to 256.53). This is most prominent when scrolling in some applications. I have found that synaptic is a very good example of this one. Scrolling is severely influenced there. With xserver 1.8 branch and nvidia-current 256.44 scrolling was very fluent: a big difference compared to xserver 1.8 branch with ati open source drivers (xserver-xorg-video-radeon). Now the open source ati drivers are clearly faster than nvidia-current_256.53 with xserver 1.9. But, for the time being I cannot say if this is a regression in xserver 1.9 or have certain codes changed in the new xserver so much, that nvidia drivers ought to be changed as well. At least it seems not to be a regression in nvidia-current, because the same driver (256.44) works very well with xserver 1.8, but not with xserver 1.9 (with IgnoreABI command). -- nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text https://bugs.launchpad.net/bugs/629910 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
Tim Jones and Randall Ross, The beta freeze is over and new packages are being built in Launchpad all the time. So new stable nvidia-current_256.53 will soon find its way there. But, I do not expect it to resolve any of the sluggisshness issues, though. There are not too many changes in the 256.53 driver compared to the pre-release version 256.52. I have tested version 256.52 quite a lot now (see my comment #71) and that did not resolve sluggisshness. If it is a driver issue. -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629451] Re: NVIDIA driver not loadable
*** This bug is a duplicate of bug 616023 *** https://bugs.launchpad.net/bugs/616023 ** This bug has been marked a duplicate of bug 616023 nVidia card : X won't start since 1.9 update, no screens found -- NVIDIA driver not loadable https://bugs.launchpad.net/bugs/629451 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 628804] Re: [Maverick] Please update nvidia-current to 256.53
*** This bug is a duplicate of bug 616023 *** https://bugs.launchpad.net/bugs/616023 ** This bug has been marked a duplicate of bug 616023 nVidia card : X won't start since 1.9 update, no screens found -- [Maverick] Please update nvidia-current to 256.53 https://bugs.launchpad.net/bugs/628804 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 629162] Re: nVidia drivers in Maverick do not work due to ABI level
*** This bug is a duplicate of bug 616023 *** https://bugs.launchpad.net/bugs/616023 ** This bug has been marked a duplicate of bug 616023 nVidia card : X won't start since 1.9 update, no screens found -- nVidia drivers in Maverick do not work due to ABI level https://bugs.launchpad.net/bugs/629162 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
Aaron, Thank you for your heads up. I made an error in my comment #69 above. What I wanted to say was that nvidia-current worked very fluently with xserver 1.8 regarding any scrolling. This is true for both Lucid Lynx (10.04) and Maverick Merkaat (10.10). And once again, immediately after upgrading my maverick setup to xserver 1.9 branch (rc5 at that time), I noticed severe sluggisshness, especially with the application "Synaptic". However, the browsers like Chromium and Firefox and on the other hand, word processor like Openoffice.org writer do not seem to suffer this kind of sluggisshness. I experienced this sluggisshness both with the drivers nvidia-current_256.44 and 256.52. I have not tested this with v. 256.53 as this is not yet available as a deb package. I hope Alberto Milone is working on that one. I will not argue with you, Aaron, about what you meant to say, but these are your exact words (taken from the bug #623399, comment #5): "If scrolling using the same driver but a different X server shows different performance, it's highly likely that the regression is in the X server and not the driver." As you said "highly likely", it made me think you really believe this to be true. Well now you have corrected this and that is it. I have no reason not to believe you. Thank You once again. -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
Hi Randall, You are correct about the new issue of 2D and 3D acceleration sluggishness. The 2D sluggishness in scrolling for instance can clearly be seen like this: open synaptic and try to scroll the package list with mouse. However, this may not be a driver issue after all. At least NVidias Aaron Plattner claims it is merely a regression in xserver 1.9. Anyway, threre was no scrolling sluggishness issues in xserver 1.9 with the NVidia drivers 256.44. It worked very fluently. -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623399] Re: nvidia drivers fail to start in Maverick X11
*** This bug is a duplicate of bug 616023 *** https://bugs.launchpad.net/bugs/616023 The pre-release 256.52 can be found from PPA's xorg-edgers and x-updates (x-swatt). But Nvidia has already published stable drivers too (256.53). -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 616023] Re: nVidia card : X won't start since 1.9 update, no screens found
Alberto, please build the deb packages from the new stable version 256.53 (publiced 31.8.2010). -- nVidia card : X won't start since 1.9 update, no screens found https://bugs.launchpad.net/bugs/616023 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623399] Re: nvidia drivers fail to start in Maverick X11
So NVidia has now publiced a new driver pre-release 256.52. That one does support new video ABI xserver xorg 8, which is required by the xserver 1.9. Now this will fix this bug. It is no more needed to put ignoreAbi text into the xorg.conf to bypass this issue. So, please do build a nvidia-current_256.52 deb package into maverick repo (restricted). -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623399] Re: nvidia drivers fail to start in Maverick X11
Aaron, Thank You for the news. About the driver compatibility. I did mean the same issue we see when we compare the driver performance on xserver 1.8 branch: with nvidia proprietary drivers any scrolling action is very fluent, but with open source ati drivers it certainly is not. Now I see exactly the same sluggishness with nvidia drivers on xserver 1.9.0 and of course with open source ati drivers too. -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623399] Re: nvidia drivers fail to start in Maverick X11
Jeff, Only Nvidia folks know that, like Aaron Plattner. Perhaps he could comment this. However, by applying the IgnoreAbi option we can make maverick boot again. But there are a lot of other issues with the recent nvidia-current_265.44 drivers, that need to be fixed. So this is only a partial or superficial workaround for xserver 1.9 branch. One example: Open Synaptic and try to scroll (with mouse) the package list. There is a huge difference compared to these drivers with xserver 1.8 branch. It is true that Nvidia is a bit lagging now that xserver 1.9 has been publiced. -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623399] Re: nvidia drivers fail to start in Maverick X11
Hi Jeff Craig, NVidia proprietary drivers (nvidia-current) do not accept the new ABI, which is required by the xserver 1.9 branch. In order to avoid this you need to add the following lines to your xorg.conf. Section "ServerFlags" Option "ignoreABI" "True" EndSection Nvidia-current_265.44 do work OK with xserver 1.9 after that. You may, however, find that scrolling is not so fluent as it was with the xserver 1.8 branch. We just have to wait for the new nvidia drivers to overcome that. -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623399 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 623400] Re: nvidia drivers fail to start in Maverick X11
*** This bug is a duplicate of bug 623399 *** https://bugs.launchpad.net/bugs/623399 This is a duplicate bug report to the bug #623399 ** This bug has been marked a duplicate of bug 623399 nvidia drivers fail to start in Maverick X11 -- nvidia drivers fail to start in Maverick X11 https://bugs.launchpad.net/bugs/623400 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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 621003] Re: nvidia-xconfig does not set ignoreABI
Nvidia-settings actually should not set that option. The option "IgnoreAbi" is in use now with xserver 1.9 because there are no nvidia drivers around to fully support this new xserver. So, IgnoreAbi is a workaround, not a fix. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New => Invalid -- nvidia-xconfig does not set ignoreABI https://bugs.launchpad.net/bugs/621003 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers 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
