[Ubuntu-x-swat] [Bug 1309550] Re: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop
As we discussed on the maillist in the end of July, this is not a blocker to our certifcate and we should create a greylist note for this. ** Tags removed: blocks-hwcert -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1309550 Title: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu- amdccclesu.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1309550/+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 1309550] Re: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu-amdccclesu.desktop
** Tags added: 201405-15042 blocks-hwcert taipei-lab -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1309550 Title: Exec should be "amdxdg-su -c /usr/bin/amdcccle" in ubuntu- amdccclesu.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1309550/+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 1315285] Re: [AMD Richland + Mars] Unable to switch graphics
HP Pavilion 15 Notebook PC (CID 201405-15042) has a similar issue. 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8610G] [1002:990f] 01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] [1002:6900] in the attachment lp1315285.tar.gz there is aticonfig-lsa.log (suggested by the comment #12) gpu-manager.log (suggested by the comment #5) lspci-nn.log xorg.conf (suggested by the comment #5) ** Attachment added: "lp1315285.tar.gz" https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+attachment/4283290/+files/lp1315285.tar.gz ** Tags added: 201405-15042 -- 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/1315285 Title: [AMD Richland + Mars] Unable to switch graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1315285/+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 1378188] Re: [GNOME3 Staging PPA] strange shadow rendered where client-side decorations are used
Ok, I found where to download the .src.rpm's for the two Fedora packages and compare the included patches. This bug is fixed by upstream commit 48a33fc379b17eed195875222ad773c911d9dff1: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=48a33fc379b17eed195875222ad773c911d9dff1 -- 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/1378188 Title: [GNOME3 Staging PPA] strange shadow rendered where client-side decorations are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1378188/+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 1378188] Re: [GNOME3 Staging PPA] strange shadow rendered where client-side decorations are used
Link to Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=1133142 They had the bug in xorg-x11-drv-intel-2.99.914-2.fc21.x86_64 and included the fix in xorg-x11-drv-intel-2.99.914-3.fc21. If I were more familiar with Fedora's infrastructure I'm sure I could find the patch with the backported fix and maybe even identify the upstream commit. ** Bug watch added: Red Hat Bugzilla #1133142 https://bugzilla.redhat.com/show_bug.cgi?id=1133142 -- 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/1378188 Title: [GNOME3 Staging PPA] strange shadow rendered where client-side decorations are used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1378188/+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 1026046] Re: Missing support for thumb resting on bottom of clickpad
The mtrack driver does allow finger resting in the bottom area, but I found it to be too rough around the edges in other areas that I couldn't use it. The cursor tracking feels weird and unnatural to me. It would also seem to accelerate when I would approach the bottom of my screen. Also, it seemed like it wasn't possible to segment the bottom area into right & left buttons (ie. every click is a left click). This would likely be an issue with the synaptics driver as well though. Its sad that all this time has passed without proper support in linux for clickpads to emulate trackpads with physical buttons. Seems like this has never been a problem for Windows and OSX drivers. I ended up just forcing myself to use tap-to-click. I'm getting used to it, but I still don't like it. I erroneously click every once in a while and dragging just plain sucks. I wish I had physical buttons on my trackpad like before :( Don't know if I should hold out any hope of this issue being resolved anytime soon. -- 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/1026046 Title: Missing support for thumb resting on bottom of clickpad To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1026046/+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 993724] Re: Left-click stops working after suspend
Noah E Crocker, thank you for your comment. So your problem and hardware may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via: ubuntu-bug linux For more on this, please read the official Ubuntu documentation: Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs 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. As well, please do not announce in this report you created a new bug report. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs -- 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/993724 Title: Left-click stops working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/993724/+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 993724] Re: Left-click stops working after suspend
I still have this exact same problem on 14.04 x64 (but it's been around
since 12.04). It happens on new installs of either Ubuntu release.
Thankfully, the workaround here still functions and saved me a lot of
trouble ("modprobe -r usbhid" followed by "modprobe usbhid"). The only
alternative is to reboot the system.
I'm not sure what else you might want from me. If I knew anything about
writing drivers, I'd try to find the bug myself, but I'm not even sure
where to start looking.
--
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/993724
Title:
Left-click stops working after suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/993724/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
This affects me too on Ubuntu Gnome 14.10 with Lenovo Yoga 13 and Intel HD 4000. Basic gnome animations are slow, or better said, they always get at least one lag during animation. I have to say that I played with unity and unity8, then uninstalled it. ibus-gtk was installed so this was no fix for me. I am going to try Gnome Shell staging as suggested. Wanted to try it before anyway... -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I followed your advice and multiseat setup still works. And still seat-1 resume problem remains. I noticed that if I do (as root) a number of commands like: # DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --output DVI-I-2 --off # DISPLAY=:1 XAUTHORITY=/var/run/lightdm/root/:1 xrandr --output DVI-I-2 --auto Then seat-1 comes back after suspend. -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Anyway, have you tried to simplify your config files? For example, in your udev rules, you don't need to tag anything as "seat0" explicitly, and in your xorg.conf file, are you sure you need all that "Screen" and "ServerLayout" sections? In principle just the "Device" sections would be enough. -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I GOT ENLIGHTENED. I know what changed since yesterday. I don't have my printer installed in the multisesat ubuntu, so I'm ocassionally booting into my Debian install where I have my multiseat setup based on a Xephyr approach, where both monitors are connected to the two heads of JUST ONE of the graphics cards. So today the monitor of seat-1 was connected to TWO cards. Hence seat0 saw two monitors and extended its desktop to both, and seat-1 also saw one monitor. When I unplugged the reduntant cable, it all behaves like yesterday: seat-1 wouldn't come back after resume. That's good and bad news: the good news it that the world still works as it is supposed, the bad news is that the seat-1 resume problem remains. I need a break... -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1403652] Re: Xorg crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1338492 *** https://bugs.launchpad.net/bugs/1338492 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1338492, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1403652/+attachment/4283101/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283104/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283117/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283119/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283120/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283121/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1403652/+attachment/4283122/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1338492 Xorg crashed with SIGABRT in OsAbort() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1403652 Title: Xorg crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1403652/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
More details on todays behaviour: After boot both screens come up, but sometimes seat-1 does appear, sometimes not and instead seat0 display extends to both monitors. Regardless of whether seat-1 appears or not, the initial position of mouse pointer of seat0 is offset BUT related to seat0's monitor. I think it is exactly in the middle of a big screen composed of BOTH monitors. If, after boot, seat-1 does not appear, when I do ctrl-alt-f1 ctrl- alt-f7 at seat0 (which CanTTY=yes) then greeter at seat1 appears. BUT only until a screensaver kicks-in: then when I move a mouse at seat-1 (or even without it), instead of seat-1's greeter (no one is logged in at seat-1) a missing part of seat0's display appears - I have same folders at the desktop and they tend to appear in a part of the screen "covered" by seat-1's greeter. And then if I ctrl-alt-f1 ctrl-alt-f7 again, seat-1's greeter appears again. The difference to yesterday and the day before is that I played with installing/uninstalling some packages. The versions of packages of interest as of now are: lightdm: 1.10.4-0ubuntu2 xserver-xorg-core: 2:1.15.1-0ubuntu2.6 I'm using Unity. I have no light-locker installed. I must say that until yesterday I had rock-solid behaviour and fully functioning system except waking up from suspend. Then I perhaps messed something up with the installed packages. What packages other than lightdm and xserver-xorg-core should I check? Is it possible that lightdm 1.10.__4__ is causing problems? -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
You could also disable light-locker for user logged in seat-1 and see if problem persists. Em qua, 17 de dez de 2014 18:44, Laércio de Sousa escreveu: > What about your lightdm.log file? And your Xorg.1.log? Any suspect > message? > > Em qua, 17 de dez de 2014 18:41, Andrzej Pietrasiewicz < > andrzejtp2...@gmail.com> escreveu: > > Regarding the doubt whether not coming back of seat-1 greeter is caused >> by the screenscaver kicking-in: that is not the case. I checked again >> and did a quick suspend and then resume and then looked up the >> x-1-greeter.log and there was no line about the screensaver. It does >> activate but far later than the failed suspend/resume. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1209008 >> >> Title: >> [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 >> seats >> >> Status in X.Org X server: >> Fix Released >> Status in xorg-server package in Ubuntu: >> Fix Released >> Status in xorg-server source package in Trusty: >> Fix Committed >> >> Bug description: >> [Impact] >> >> * In Xorg-server versions older than 1.16, if Xorg is started as a >> non-seat0 X server (i.e. if it was started with "-seat " option >> where "" != "seat0"), it only probes platform bus for graphics >> devices, leaving devices with non-KMS drivers (like NVIDIA proprietary >> drivers and old ones like xf86-video-siliconmotion) unreachable. >> >> Patch "xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch" >> from lp:~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. >> >> * systemd-logind has no intrinsic mechanism to assign non-KMS graphics >> devices to seats. In this case, one should tag another seat device >> (keyboard, USB hub, etc.) in udev as "master-of-seat", and provide a >> suitable xorg.conf for that seat. In order to avoid that a given >> xorg.conf affects other seats, it should be passed to Xorg via >> "-config xorg.conf.custom" option, which requires X server command >> line customization support in DM in use (GDM, for example, has no such >> support). >> >> Patch "xfree86_add_matchseat_key_to_xorg_conf.patch" from lp:~ubuntu- >> multiseat/xorg-server/trusty-matchseat introduces a new MatchSeat key >> for xorg.conf sections "Device", "Screen", and "ServerLayout", which >> will target a given seat only. Example file >> /etc/X11/xorg.conf.d/90-seat-1.conf: >> >> Section "Device" >> Identifier "card0" >> Driver "nvidia" >> Option "NoLogo" "True" >> # This section will only apply for seat-1 >> MatchSeat "seat-1" >> EndSection >> >> * systemd-logind can't handle any VT switching for non-seat0 seats, >> but Xorg-server older than 1.16 still opens VT even if it's started as >> a non-seat0 X server. This may lead to a race condition between X >> servers: if a non-seat0 one is started before a seat0 one, the former >> "steals" VTs from the later. If a seat0 X server can't open VTs, >> systemd-logind can't activate sessions for seat0, leaving user without >> sound or usb input support, for example. >> >> Patch "xfree86_keep_non_seat0_from_touching_vts.patch" from lp >> :~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. >> >> [Test Case] >> >> * Set up a multiseat system where your non-seat0 seats use non-KMS >> video drivers (you may need to tag another device in udev as "master- >> of-seat" in order to achieve it). >> >> * When LightDM/GDM tries to start a Xorg server for your non-seat0 >> seats, it will end up with the following error: "(EE) No devices >> found". >> >> * After applying >> xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch, you can >> configure your seats in LightDM by setting appropriate "xserver- >> config" properties for each seat. However, you can't configure them in >> GDM. >> >> * After applying xfree86_add_matchseat_key_to_xorg_conf.patch, >> configure your seats properly and restart LightDM/GDM services (or >> reboot your computer) repeatedly. In some iterations, it may happen >> that logind can't activate graphical sessions for seat0. If it occurs, >> check output of command "ps -FC Xorg" and you'll see that a non-seat0 >> Xorg server has a lower PID than seat0 one. Moreover, the non-seat0 >> has opened a TTY, while the seat0 hasn't. >> >> [Regression Potential] >> >> * Very low. All these patches were well tested in xorg-server "trusty" >> package available in ppa:ubuntu-multiseat/ppa. >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions >> > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications
Re: [Ubuntu-x-swat] [Bug 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
What about your lightdm.log file? And your Xorg.1.log? Any suspect message? Em qua, 17 de dez de 2014 18:41, Andrzej Pietrasiewicz < andrzejtp2...@gmail.com> escreveu: > Regarding the doubt whether not coming back of seat-1 greeter is caused > by the screenscaver kicking-in: that is not the case. I checked again > and did a quick suspend and then resume and then looked up the > x-1-greeter.log and there was no line about the screensaver. It does > activate but far later than the failed suspend/resume. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1209008 > > Title: > [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 > seats > > Status in X.Org X server: > Fix Released > Status in xorg-server package in Ubuntu: > Fix Released > Status in xorg-server source package in Trusty: > Fix Committed > > Bug description: > [Impact] > > * In Xorg-server versions older than 1.16, if Xorg is started as a > non-seat0 X server (i.e. if it was started with "-seat " option > where "" != "seat0"), it only probes platform bus for graphics > devices, leaving devices with non-KMS drivers (like NVIDIA proprietary > drivers and old ones like xf86-video-siliconmotion) unreachable. > > Patch "xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch" > from lp:~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. > > * systemd-logind has no intrinsic mechanism to assign non-KMS graphics > devices to seats. In this case, one should tag another seat device > (keyboard, USB hub, etc.) in udev as "master-of-seat", and provide a > suitable xorg.conf for that seat. In order to avoid that a given > xorg.conf affects other seats, it should be passed to Xorg via > "-config xorg.conf.custom" option, which requires X server command > line customization support in DM in use (GDM, for example, has no such > support). > > Patch "xfree86_add_matchseat_key_to_xorg_conf.patch" from lp:~ubuntu- > multiseat/xorg-server/trusty-matchseat introduces a new MatchSeat key > for xorg.conf sections "Device", "Screen", and "ServerLayout", which > will target a given seat only. Example file > /etc/X11/xorg.conf.d/90-seat-1.conf: > > Section "Device" > Identifier "card0" > Driver "nvidia" > Option "NoLogo" "True" > # This section will only apply for seat-1 > MatchSeat "seat-1" > EndSection > > * systemd-logind can't handle any VT switching for non-seat0 seats, > but Xorg-server older than 1.16 still opens VT even if it's started as > a non-seat0 X server. This may lead to a race condition between X > servers: if a non-seat0 one is started before a seat0 one, the former > "steals" VTs from the later. If a seat0 X server can't open VTs, > systemd-logind can't activate sessions for seat0, leaving user without > sound or usb input support, for example. > > Patch "xfree86_keep_non_seat0_from_touching_vts.patch" from lp > :~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. > > [Test Case] > > * Set up a multiseat system where your non-seat0 seats use non-KMS > video drivers (you may need to tag another device in udev as "master- > of-seat" in order to achieve it). > > * When LightDM/GDM tries to start a Xorg server for your non-seat0 > seats, it will end up with the following error: "(EE) No devices > found". > > * After applying > xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch, you can > configure your seats in LightDM by setting appropriate "xserver- > config" properties for each seat. However, you can't configure them in > GDM. > > * After applying xfree86_add_matchseat_key_to_xorg_conf.patch, > configure your seats properly and restart LightDM/GDM services (or > reboot your computer) repeatedly. In some iterations, it may happen > that logind can't activate graphical sessions for seat0. If it occurs, > check output of command "ps -FC Xorg" and you'll see that a non-seat0 > Xorg server has a lower PID than seat0 one. Moreover, the non-seat0 > has opened a TTY, while the seat0 hasn't. > > [Regression Potential] > > * Very low. All these patches were well tested in xorg-server "trusty" > package available in ppa:ubuntu-multiseat/ppa. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launc
[Ubuntu-x-swat] [Bug 1401743] Re: HP Z210 workstation with nvidia Quadro 600 card thinks 32 inch sharp TV/monitor is 37 inch
John Ellis, given the issue happens in both Windows and Ubuntu, if a firmware update is available for the TV, that would want to be applied. Despite this, you should still be able to make the same WORKAROUND adjustment in Windows as you do in Ubuntu. Would using arandr and the nouveau driver allow you this opportunity? -- 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/1401743 Title: HP Z210 workstation with nvidia Quadro 600 card thinks 32 inch sharp TV/monitor is 37 inch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401743/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Regarding the doubt whether not coming back of seat-1 greeter is caused by the screenscaver kicking-in: that is not the case. I checked again and did a quick suspend and then resume and then looked up the x-1-greeter.log and there was no line about the screensaver. It does activate but far later than the failed suspend/resume. -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Before suspend: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 1236 1223 12 55708 73248 0 20:56 tty7 00:00:10 /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1238 1223 2 36801 64892 0 20:56 ?00:00:02 /usr/bin/X -core :1 -seat seat-1 -sharevts -auth /var/run/lightdm/root/:1 -nolisten tcp After resume: UIDPID PPID CSZ RSS PSR STIME TTY TIME CMD root 1236 1223 10 93676 173432 1 20:56 tty7 00:00:13 /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root 1238 1223 1 37185 65092 1 20:56 ?00:00:02 /usr/bin/X -core :1 -seat seat-1 -sharevts -auth /var/run/lightdm/root/:1 -nolisten tcp A big difference today is that the monitor assigned to seat-1 comes back alive BUT it extends the display of session at seat0! In other words, today, after resume, both monitors provide a big desktop for session @ seat0. I can't understand how it changed since yesterday. Yesterday the behaviour was as described above: seat-1 card wouldn't come back. I'm also noticing a changed behaviour after boot and when greeters first appear: until yesterday, they appeared almost at the same time, with mouse pointers exactly in the middle of both. Today, they tend to blink a couple of times, and seat0 mouse pointers appears offset to the right. In /etc/lightdm/x-1-greeter.log I can see at the end: [+61,04s] DEBUG: user-list.vala:1030: Adding/updating user hajaszek () [+398,50s] DEBUG: settings-daemon.vala:209: Screensaver activated Please compare the times. The screensaver activates after about 5 minutes after the greeter is first displayed at system start. I can't tell at this moment if this corresponds to the time when I suspended/resumed or to the time where screensaver kicked-in on an otherwise unavailable display. SInce yesterday evening I played with printer drivers from http://www.bchemnet.com/suldr/; I installed/removed some of them back and forth. Then today I did apt-get install apt-show-version, and then did apt-get autoremove as suggested by apt. I would say this situation is even more annoying compared to the one when seat-1 consistently refuses to show up after resume. -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Oh sorry! I didn't catch your lightdm.conf above. When you restart lightdm service, all Xorg processes are killed and then restarted. That's why your seat-1 goes back to normal when you do that. I suspect your seat-1 Xorg may be killed when suspending. You can confirm it by running "ps -FC Xorg | less". Also take a look at lightdm and Xorg log files when your seat-1 fails to wake up. Em qua, 17 de dez de 2014 17:05, Andrzej Pietrasiewicz < andrzejtp2...@gmail.com> escreveu: > I have two discrete cards. So the difference is that your integrated > card is probably on the "platform bus", while both of my discrete cards > are PCI-E devices. > > I started testing multiseat setup described in this thread only last > Saturday and since then have always been using the lightdm version which > supports automatic multiseat; in one of my posts above (where I thought > that the multiseat setup didn't work) I enclosed my full lightdm.conf; > it only consisted of logind-load-seats and logind-check-graphical. > > # apt-cache policy lightdm > lightdm: > Zainstalowana: 1.10.4-0ubuntu2 # means: Installed > Kandydująca: 1.10.4-0ubuntu2 # means: Candidate > Tabela wersji: > *** 1.10.4-0ubuntu2 0 > 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main i386 > Packages > 100 /var/lib/dpkg/status > 1.10.3-0ubuntu2 0 > 500 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 > Packages > 1.10.0-0ubuntu3 0 > 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages > > The full lightdm.conf I'm using now: > > [LightDM] > logind-load-seats=true > logind-check-graphical=true > > [SeatDefaults] > allow-guest=false > > [Seat:seat-1] > xserver-command=/usr/bin/X -core -dpms -s 0 > > And with this setup the card assigned to seat0 in xorg.conf wakes up > correctly, but the other does not. I'm wandering which step of > restarting lightdm does the trick of waking it up fully? Because, as I > said before, the seat-1 is not completely lost after wakeup; if I > brutally restart lightdm it comes back, of course all graphical sessions > terminated and lightdm login screen displayed again at both seats. > > My random guess is that the problem is in the X server. Perhaps for > waking up there is some code path which works in a similar way to what > probing used to work, that is, it only searches for platform display > devices? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1209008 > > Title: > [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 > seats > > Status in X.Org X server: > Fix Released > Status in xorg-server package in Ubuntu: > Fix Released > Status in xorg-server source package in Trusty: > Fix Committed > > Bug description: > [Impact] > > * In Xorg-server versions older than 1.16, if Xorg is started as a > non-seat0 X server (i.e. if it was started with "-seat " option > where "" != "seat0"), it only probes platform bus for graphics > devices, leaving devices with non-KMS drivers (like NVIDIA proprietary > drivers and old ones like xf86-video-siliconmotion) unreachable. > > Patch "xfree86_allow_fallback_to_pci_bus_probe_for_non_seat0.patch" > from lp:~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. > > * systemd-logind has no intrinsic mechanism to assign non-KMS graphics > devices to seats. In this case, one should tag another seat device > (keyboard, USB hub, etc.) in udev as "master-of-seat", and provide a > suitable xorg.conf for that seat. In order to avoid that a given > xorg.conf affects other seats, it should be passed to Xorg via > "-config xorg.conf.custom" option, which requires X server command > line customization support in DM in use (GDM, for example, has no such > support). > > Patch "xfree86_add_matchseat_key_to_xorg_conf.patch" from lp:~ubuntu- > multiseat/xorg-server/trusty-matchseat introduces a new MatchSeat key > for xorg.conf sections "Device", "Screen", and "ServerLayout", which > will target a given seat only. Example file > /etc/X11/xorg.conf.d/90-seat-1.conf: > > Section "Device" > Identifier "card0" > Driver "nvidia" > Option "NoLogo" "True" > # This section will only apply for seat-1 > MatchSeat "seat-1" > EndSection > > * systemd-logind can't handle any VT switching for non-seat0 seats, > but Xorg-server older than 1.16 still opens VT even if it's started as > a non-seat0 X server. This may lead to a race condition between X > servers: if a non-seat0 one is started before a seat0 one, the former > "steals" VTs from the later. If a seat0 X server can't open VTs, > systemd-logind can't activate sessions for seat0, leaving user without > sound or usb input support, for example. > > Patch "xfree86_keep_non_seat0_from_touching_vts.patch" from lp > :~ubuntu-multiseat/xorg-server/trusty-matchseat fixes this. > > [Te
[Ubuntu-x-swat] [Bug 1402966] Re: libxcb new version 1.11
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1402966 Title: libxcb new version 1.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1402966/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
I have two discrete cards. So the difference is that your integrated card is probably on the "platform bus", while both of my discrete cards are PCI-E devices. I started testing multiseat setup described in this thread only last Saturday and since then have always been using the lightdm version which supports automatic multiseat; in one of my posts above (where I thought that the multiseat setup didn't work) I enclosed my full lightdm.conf; it only consisted of logind-load-seats and logind-check-graphical. # apt-cache policy lightdm lightdm: Zainstalowana: 1.10.4-0ubuntu2 # means: Installed Kandydująca: 1.10.4-0ubuntu2 # means: Candidate Tabela wersji: *** 1.10.4-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1.10.3-0ubuntu2 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 1.10.0-0ubuntu3 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages The full lightdm.conf I'm using now: [LightDM] logind-load-seats=true logind-check-graphical=true [SeatDefaults] allow-guest=false [Seat:seat-1] xserver-command=/usr/bin/X -core -dpms -s 0 And with this setup the card assigned to seat0 in xorg.conf wakes up correctly, but the other does not. I'm wandering which step of restarting lightdm does the trick of waking it up fully? Because, as I said before, the seat-1 is not completely lost after wakeup; if I brutally restart lightdm it comes back, of course all graphical sessions terminated and lightdm login screen displayed again at both seats. My random guess is that the problem is in the X server. Perhaps for waking up there is some code path which works in a similar way to what probing used to work, that is, it only searches for platform display devices? -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1305334] Re: Mesa 10 (9) do not work properly with Intel Ivy bridge / Sandy bridge
Is this still occurring on Ubuntu 14.10 "Utopic Unicorn"? ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1305334 Title: Mesa 10 (9) do not work properly with Intel Ivy bridge / Sandy bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1305334/+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 1390234] Re: Unity desktop misbehaves with applications that use direct rendering with the FGLRX driver
I woul like to update this issue to say that this problem still happens with the latest Catalyst 14.12. -- 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/1390234 Title: Unity desktop misbehaves with applications that use direct rendering with the FGLRX driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1390234/+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 1403008] Re: nvidia-331-updates wrongly installed by an upgrade prevent GNOME shell to start
** Summary changed: - nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME shell to start + nvidia-331-updates wrongly installed by an upgrade prevent GNOME shell to start ** No longer affects: xorg-server (Ubuntu) ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Invalid => Triaged -- 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/1403008 Title: nvidia-331-updates wrongly installed by an upgrade prevent GNOME shell to start To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1403008/+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 1401743] Re: HP Z210 workstation with nvidia Quadro 600 card thinks 32 inch sharp TV/monitor is 37 inch
Hello Christopher M. Penalver: The driver I previously tested, when I still was using the old 1.41 bios, was the : NVIDIA binary driver -version 331.113 from nvidia-331-updates (proprietary). tv/monitor (Sharp LC-32D62U) via a dvi/hdmi 10 foot cable to #4 hdmi connector (on tv/monitor which I believe only supports hdmi version 1.1 but I am unable to verify this)... a firmware update is available for the SHARP D62U TV series (at your own risk and may not apply to my model) which may or may not help. I am pleased at least to have finally successfully updated my HP Z210sff Workstation firmware bios (which I had failed several times in years past... perhaps because I did not reset my bios to factory defaults) and I understand a ME firmware update is also available. More personal trauma with firmware appears to lie ahead. Thank you for your efforts in accurate documentation which have helped me to focus and reassess (and search forums for similar, helpful and related issues). It becomes , once again, apparent that many elements come into play below the surface of what was hoped to be a simple configuration change. Ubuntu and open source John Ellis On 2014-12-17 12:13 AM, Christopher M. Penalver wrote: > John Ellis, could you please advise which NVIDIA driver version > specifically you tested with previously? > > ** Tags removed: bios-outdated-1.47 > ** Tags added: latest-bios-1.47 > > ** Changed in: xorg (Ubuntu) > Importance: Low => Medium > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1401743 Title: HP Z210 workstation with nvidia Quadro 600 card thinks 32 inch sharp TV/monitor is 37 inch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1401743/+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 1403008] Re: nvidia-331-updates installed by update prevent Gnome shell to start
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Critical ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Summary changed: - nvidia-331-updates installed by update prevent Gnome shell to start + nvidia-331-updates installed by an xserver-xorg-core upgrade prevent Gnome shell to start ** Changed in: xorg-server (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: Incomplete => Invalid ** Changed in: hundredpapercuts Importance: Undecided => Critical ** Changed in: hundredpapercuts Status: New => Triaged ** Summary changed: - nvidia-331-updates installed by an xserver-xorg-core upgrade prevent Gnome shell to start + nvidia-331-updates installed by an xserver-xorg-core upgrade prevent Gnome shell to start on Ubuntu GNOME 14.04 ** Summary changed: - nvidia-331-updates installed by an xserver-xorg-core upgrade prevent Gnome shell to start on Ubuntu GNOME 14.04 + nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME shell to start in Ubuntu GNOME 14.04 ** Summary changed: - nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME shell to start in Ubuntu GNOME 14.04 + nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME shell to start -- 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/1403008 Title: nvidia-331-updates installed by an xserver-xorg-core upgrade prevent GNOME shell to start To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1403008/+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 1403287] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1403287 Title: Missing Mouse-Cursor After Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403287/+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 1403287] Re: Missing Mouse-Cursor After Login
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Invalid ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1403287 Title: Missing Mouse-Cursor After Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403287/+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 1403474] [NEW] test in ubuntu 14.10
Public bug reported: using wine stn wrong in amd64 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Dec 17 19:36:00 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8550G] [1002:990d] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:21ad] InstallationDate: Installed on 2014-12-10 (7 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. X550DP ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-28-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550DP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd09/09/2013:svnASUSTeKCOMPUTERINC.:pnX550DP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550DP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550DP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Dec 17 14:31:18 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- 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/1403474 Title: test in ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1403474/+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 1209008] Re: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats
Unfortunately, I can't reproduce your error in my hardware. Both seats wake up correctly here. My hardware consists of an integrated Intel graphics device and a Silicon Motion SM501 PCI graphics card. I'm also using Xubuntu with lightdm 1.10.3 from trust-updates repo. BTW, did you upgrade your lightdm to 1.10.3? Dou you know this version has backported automatic multiseat feature introduced in 1.12 series? Although this is the default behaviour in 1.12 series, it must be enabled manually in 1.10.3. Just drop all your previous manual seat configurations ([Seat:0], [Seat:1], etc.) in lightdm.conf and put the following: [LightDM] logind-load-seats=true If you want to seat e.g. autologin user for each seat, just append the following sections: [Seat:seat0] autologin-user= [Seat:seat-1] autologin-user= Now you can test again that setting above for disabling DPMS for your seat-1 X server: [Seat:seat-1] xserver-command=/usr/bin/X -core -dpms -s 0 -- 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/1209008 Title: [SRU] X doesn't work for video cards with non-KMS drivers on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+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 1403448] [NEW] Kernel panic after fglrx update
Public bug reported: Hi This Friday i updated me system on laptop and rebooted. And system don't want to boot. I attached external keyboard to laptop and by boot saw kernel panic leds blinking. But i don't get any messages on my screen(external screen to). So i reinstalled my ubuntu 12.04(pure without updates to 12.04.*). Next step was installing fglrx driver from amd website(amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64). I choose install with package generation. After installing generated packages i whanted to install updates. Updater suggested to update my fglrx to version 13.3(or something similar). But i have Ati HD 5145(renamed HD4570). For this cards is only 13.1-legacy suitable! 13.3 is For Radeon HD 54** and higher(newer). To avoid wrong driver installation i fixed package version in synaptic. unim95@unim95-ThikpadEdge:~$ lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 Video: Ati HD5145 Driver: fglrx_8.970-0ubuntu1_amd64.deb ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New -- 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/1403448 Title: Kernel panic after fglrx update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1403448/+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 1323967] Re: No Unity 3D support with Radeon APU E2-4000 with R2 Graphics [1002:9853]
I can still reproduce this issue on the same system with linux-generic- lts-utopic 3.16.0.28.21 OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits) OpenGL version string: 2.1 Mesa 10.1.3 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes Compiz supported: no ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323967/+attachment/4282680/+files/Xorg.0.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/1323967 Title: No Unity 3D support with Radeon APU E2-4000 with R2 Graphics [1002:9853] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1323967/+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 1378744] Re: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash
I can confirm this problem for Ubuntu 14.10 with a radeon card. It might also be the problem in Lubuntu: http://forum.ubuntuusers.de/topic/nach-xorg-update-bildschirm-an-hdmi-fuehrt-zu-/ and https://bugs.launchpad.net/mythbuntu/+bug/1402605 ** Attachment added: "Xorg log.txt" https://bugs.launchpad.net/nouveau/+bug/1378744/+attachment/4282648/+files/Xorg%20log.txt -- 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/1378744 Title: nVidia GK106GLM [Quadro K2100M] [10de:11fc] Connect to HDMI / DP port with open-source driver will cause Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1378744/+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
