[Desktop-packages] [Bug 1685754]
This issue was fixed in systemd by
https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that
change into 245.4-3, so Debian bullseye and buster-backports have the
fix, as does Ubuntu 20.04 (focal).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
'systemd --user' unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
Invalid
Status in GNOME Terminal:
Confirmed
Status in Nautilus:
Invalid
Status in systemd:
Unknown
Status in dbus package in Ubuntu:
Invalid
Status in gnome-terminal package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Fix Released
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
First message in second seat greeter log file is logged after less than 1 second when I log in in first seat. At this moment greeter starts eating cpu. Please attach a debugger and get a stack trace when this happens. Does the greeter crash, exit, or move to the background? Greeter crashes. Please get a stack trace, either by looking at the core file or by attaching a debugger before it crashes. * Tried several times restart pc, but unity-greeter didn't start on my seat. Seat with autologin still worked fine. Than I edited /var/lib/lightdm/.cache/unity-greeter/seat0-state and changed last-user back to what I use on my first seat. unity-greeter runs some code whenever a user is selected (including selecting the last logged-in user when unity-greeter starts up). For example, it does some PAM stuff to see if a password is required for the user that was selected. Something in this code must be crashing. In addition to the stack traces, please collect the following information (before logging in via unity-greeter, so use Ctrl-Alt-F1 to log in via a VT or ssh into the machine): * unity-greeter environment variables: for pid in $(pidof unity-greeter); do printf '\n%s\n-\n' pid $pid sudo cat /proc/$pid/environ | tr '\0' '\n' done unity-greeter-environ.txt * unity-greeter session processes: For each session listed in 'loginctl list-sessions', do: loginctl --full --no-pager session-status $session_name sessions.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
In addition to the stack traces, please collect the following information (before logging in via unity-greeter, so use Ctrl-Alt-F1 to log in via a VT or ssh into the machine) Attached zip with files Nothing looks strange there. Please get a stack trace, either by looking at the core file or by attaching a debugger before it crashes. I don't know how to do it. There is no lightdm-dbg or unity-greeter-dbg packages. I'll upload debug packages later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
@a7x, I use Ubuntu 12.04.2.
Unfortunately, the multiseat PPA doesn't contain packages for 12.04
(precise). Multiseat requires logind, and that wasn't introduced to
Ubuntu until 13.04 (raring).
This PPA focuses only on support multiseat?
Yes.
Do it keeps sync with the mainstream in other issues?
The process is manual, so there may be some time between when Ubuntu
fixes a bug and when that fix makes it to the multiseat PPA, but I do
generally try to keep them in sync.
I try not to backport new features (only bug fixes).
With it I face much risk of having serious bugs in the system?
I run these packages on my personal system, so I try to be careful to
not introduce serious bugs. However, the packages in the PPA are
experimental. If you are concerned about security, stability, and
reliability, do not use the packages in the multiseat PPA.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
| `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions
[Desktop-packages] [Bug 1208473] Re: Xorg crashed with SIGABRT in mieqMoveToNewScreen()
** Bug watch added: Red Hat Bugzilla #902301 https://bugzilla.redhat.com/show_bug.cgi?id=902301 ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=902301 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1208473 Title: Xorg crashed with SIGABRT in mieqMoveToNewScreen() Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: apport showed up ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.2-0ubuntu7 Uname: Linux 3.11.0-rc1-custom i686 .tmp.unity.support.test.0: ApportVersion: 2.12-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Aug 5 15:32:06 2013 DistUpgraded: 2013-08-04 14:50:50,172 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.10.0-6-generic, i686: installed virtualbox, 4.2.16, 3.11.0-rc1-custom, i686: installed virtualbox-guest, 4.2.16: added ExecutablePath: /usr/bin/Xorg GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:844d] InstallationDate: Installed on 2011-11-11 (633 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-rc1-custom root=UUID=239a7bf6-c6d6-468d-90fb-5705e76c8def ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: mieqProcessDeviceEvent () mieqProcessInputEvents () ?? () DisableDevice () ?? () Title: Xorg crashed with SIGABRT in mieqProcessDeviceEvent() UpgradeStatus: Upgraded to saucy on 2013-08-04 (1 days ago) UserGroups: dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H67-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd07/15/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-M:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.libdrm2: libdrm2 2.4.46-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu7 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.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.12-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Mon Aug 5 15:32:10 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8954 vendor ACI xserver.version: 2:1.14.2-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1208473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1209008] Re: X fails to detect certain video cards on non-seat0 seats
Raring and saucy packages containing the patch have been uploaded to the multiseat PPA: https://launchpad.net/~ubuntu-multiseat/+archive/ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats Status in X.Org X server: Confirmed Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: From https://bugs.freedesktop.org/show_bug.cgi?id=66851: I have a multiseat setup with a primary on-board Intel graphics device and a secondary Silicon Motion SM501 graphics card. My SM501 is configured via custom xorg.conf with siliconmotion ddx driver, so it exposes no framebuffer devices to e.g. systemd-logind. The same situation is seen e.g. for a NVIDIA graphics card with proprietary drivers. Every time I configure my system to assign my SM501 card with a secondary seat, i.e. not seat0, my X server fails to start, returning a No devices detected error. Nevertheless, when I assign my SM501 card with seat0 and attach my Intel graphics device to secondary seat (via loginctl), both seats load successfully. Investigating the Xorg-server sources, I've found something related to platform bus. I don't know what is it at all, but whatever it means, my Intel graphics card with its open-source drivers implement it, but my siliconmotion driver doesn't. In its current form, Xorg-server probes for platform bus devices as well as legacy PCI bus ones only for seat0. For other seats, it only probes for platform bus devices, hence it never reaches my SM501 card, returning that No devices found error. I don't know if there's a good reason for probing only platform bus devices on non-seat0 seats, but this brings a problem for multiseat setups like mine. This same problem was encoutered by a user with two NVIDIA cards; see bug #976124. A patch was supplied to the upstream bug report, and this patch seems to fix the problem. Note that this bug only affects detection of cards when X is passed the '-seat' argument with a seat name OTHER than seat0. Thus, this only happens in multiseat setups. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201122] Re: Remember last logged in user for each seat
Raring and saucy packages containing the fix have been uploaded to the multiseat PPA: https://launchpad.net/~ubuntu-multiseat/+archive/ppa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1201122 Title: Remember last logged in user for each seat Status in Unity Greeter: New Status in “unity-greeter” package in Ubuntu: New Bug description: On my pc I am using two seats. Currently when I start pc on both seats automatically is selected last logged in user. Lightdm should remember last logged in user for each seat. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1201122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
But maybe you have some ideas where or what we need to fix? A potential conflict with PAM settings was my best idea, but that doesn't seem likely anymore. I was able to login in both seats two times today, but I have no idea what could caused that Interesting! That could indicate a race condition. Try delaying the start of X on your second seat to see if that helps. First, create a wrapper script around X that pauses before starting X: sudo tee /usr/bin/Xdelayed EOF /dev/null #!/bin/sh sleep 10 exec /usr/bin/X $@ EOF sudo chmod a+rx /usr/bin/Xdelayed Next, modify your second seat config in /etc/lightdm/lightdm.conf to use the wrapper script: [Seat:1] xserver-vt=0 xdg-seat=seat1 xserver-command=/usr/bin/Xdelayed whatever arguments you usually use Finally, restart lightdm (sudo service lightdm restart) or reboot and see what happens. (I know you know how to create scripts and restart lightdm and whatnot, I'm just trying to be detailed for the benefit of the lurkers reading this bug report.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
1) All greeters works fine until I login in one of all seats, it does not matter which one. 1.1) When it is done remaining unity-greeters starts eating cpu. Are any messages being logged over and over when it does this? Next time it enters an infinite loop, please see if you can attach gdb to the process and get a stack trace. (Please install debug symbols first; see the instructions at: https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages.) 2) When one seat is logged in there is two things that could happen: 2.1) Trying to select different user results in greeter crashing leaving with black screen with ugly cursor. Does the greeter crash, exit, or move to the background? Try attaching gdb to the greeter before selecting a different user. If it crashes, please post the stack trace. (again, please install debug symbols first) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201122] Re: Remember last logged in user for each seat
** Also affects: unity-greeter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1201122 Title: Remember last logged in user for each seat Status in Unity Greeter: New Status in “unity-greeter” package in Ubuntu: New Bug description: On my pc I am using two seats. Currently when I start pc on both seats automatically is selected last logged in user. Lightdm should remember last logged in user for each seat. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-greeter/+bug/1201122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
Patched xorg with this (https://bugzilla.redhat.com/attachment.cgi?id=751266action=diff) patch from this (https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=962907) bug report. And now lightdm shows up on second seat. Calvin Morrow says that fix probably even simplier, read comment #20. Good find! Perhaps I'll upload the patched X to my PPA. But multiseat still doesn't work. I can login only in one of two seats. Pasword field disappears when I want select other user for second seat. Or if correct user already is selected, I can write in password, but nothing happens when i try to login. So my multiseat changes don't appear to affect this particular bug. That's unfortunate. I know that when selecting a user, LightDM (or maybe it's unity-greeter, I can't remember) does some PAM stuff to see if it's possible to log in without a password. Perhaps you have an uncommon PAM setup that is confusing LightDM/unity-greeter? *) Tested with different seat names. First seat - seat01, second seat - seat1. Added udev rules to assign video card and usb hub for seat01. Both seats started up, i was able to login in first seat, but there was problems - huge memory leaks. In attached zip are log files for xorg and lightdm. My .xsession-errors was full of error lines: I'll take a look when I next have the time. loginctl list-seats lists only one seat. shouldn't it list two seats? Yes, it should. If I understand correctly, the 'master-of-seat' udev tag should cause logind to create the second seat. (To avoid starting an X server before a video card is detected, logind won't create a seat until a device tagged with 'master-of-seat' appears.) Does 'udevadmin info --export-db' show the 'master-of-seat' tag on your video card? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
If I try to change user on second seat when first seat user is already loged in, How were you able to get a user logged in to both seats? I thought that the password prompt issue only made it possible for one user to be logged in at a time. Are you doing auto-login? second seat turns black and has black cross instead of standard mouse pointer. With X, user switching is only supported on the main seat (seat0). LightDM currently doesn't ask logind if the current seat supports user switching; it just assumes that it does. So trying to switch users on the second seat will do weird things. Ideally you wouldn't even see the menu option to switch to another user if you're not logged in on seat0. I have a patch that partly fixes this, but breaks other things. I'll finish it up after basic multiseat support has been merged to LightDM. *) 'udevadmin info --export-db' showed only one record with 'master-of-seat' tag. So I added line 'TAG==seat, DEVPATH==/devices/pci:00/:00:1c.0/:02:00.0/*, TAG+=master-of-seat' back to 99-multiseat.rules. Now udevadm shows two records with 'master-of-seat' tag and loginctl lists both seats. Did this improve anything? (other than listing both seats) *) What is uncommon setup and what is common setup? I have two user accounts on my saucy install. Both requires password to login. The default setup is the common setup. It becomes uncommon the instant you add or remove a PAM module. There are PAM modules to do all sorts of stuff related to user authentication. For example, there are PAM modules to lock out users if they fail to enter their password more than X times in a row, PAM modules to require new passwords to match certain rules (e.g., not a variant of a dictionary word, more than X characters long), PAM modules to require two-factor authentication (e.g., https://code.google.com/p/google-authenticator/), etc. It may help to post the relevant PAM config files: * /etc/pam.conf * /etc/pam.d/lightdm* * /etc/pam.d/common-* * /etc/pam.d/other I can then compare them to my PAM config files to see if there's any difference. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1209008] [NEW] X fails to detect certain video cards on non-seat0 seats
Public bug reported: From https://bugs.freedesktop.org/show_bug.cgi?id=66851: I have a multiseat setup with a primary on-board Intel graphics device and a secondary Silicon Motion SM501 graphics card. My SM501 is configured via custom xorg.conf with siliconmotion ddx driver, so it exposes no framebuffer devices to e.g. systemd-logind. The same situation is seen e.g. for a NVIDIA graphics card with proprietary drivers. Every time I configure my system to assign my SM501 card with a secondary seat, i.e. not seat0, my X server fails to start, returning a No devices detected error. Nevertheless, when I assign my SM501 card with seat0 and attach my Intel graphics device to secondary seat (via loginctl), both seats load successfully. Investigating the Xorg-server sources, I've found something related to platform bus. I don't know what is it at all, but whatever it means, my Intel graphics card with its open-source drivers implement it, but my siliconmotion driver doesn't. In its current form, Xorg-server probes for platform bus devices as well as legacy PCI bus ones only for seat0. For other seats, it only probes for platform bus devices, hence it never reaches my SM501 card, returning that No devices found error. I don't know if there's a good reason for probing only platform bus devices on non-seat0 seats, but this brings a problem for multiseat setups like mine. This same problem was encoutered by a user with two NVIDIA cards; see bug #976124. A patch was supplied to the upstream bug report, and this patch seems to fix the problem. Note that this bug only affects detection of cards when X is passed the '-seat' argument with a seat name OTHER than seat0. Thus, this only happens in multiseat setups. ** Affects: xorg-server Importance: Unknown Status: Unknown ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: fedora Importance: Unknown Status: Unknown ** Tags: multiseat saucy ** Branch linked: lp:~albertsmuktupavels/xorg-server/fix-no-devices- detected-for-seats-other-than-seat0 ** Bug watch added: freedesktop.org Bugzilla #66851 https://bugs.freedesktop.org/show_bug.cgi?id=66851 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=66851 Importance: Unknown Status: Unknown ** Also affects: fedora via https://bugs.freedesktop.org/show_bug.cgi?id=66851 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #962907 https://bugzilla.redhat.com/show_bug.cgi?id=962907 ** Changed in: fedora Remote watch: freedesktop.org Bugzilla #66851 = Red Hat Bugzilla #962907 ** Tags added: multiseat ** Tags added: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: From https://bugs.freedesktop.org/show_bug.cgi?id=66851: I have a multiseat setup with a primary on-board Intel graphics device and a secondary Silicon Motion SM501 graphics card. My SM501 is configured via custom xorg.conf with siliconmotion ddx driver, so it exposes no framebuffer devices to e.g. systemd-logind. The same situation is seen e.g. for a NVIDIA graphics card with proprietary drivers. Every time I configure my system to assign my SM501 card with a secondary seat, i.e. not seat0, my X server fails to start, returning a No devices detected error. Nevertheless, when I assign my SM501 card with seat0 and attach my Intel graphics device to secondary seat (via loginctl), both seats load successfully. Investigating the Xorg-server sources, I've found something related to platform bus. I don't know what is it at all, but whatever it means, my Intel graphics card with its open-source drivers implement it, but my siliconmotion driver doesn't. In its current form, Xorg-server probes for platform bus devices as well as legacy PCI bus ones only for seat0. For other seats, it only probes for platform bus devices, hence it never reaches my SM501 card, returning that No devices found error. I don't know if there's a good reason for probing only platform bus devices on non-seat0 seats, but this brings a problem for multiseat setups like mine. This same problem was encoutered by a user with two NVIDIA cards; see bug #976124. A patch was supplied to the upstream bug report, and this patch seems to fix the problem. Note that this bug only affects detection of cards when X is passed the '-seat' argument with a seat name OTHER than seat0. Thus, this only happens in multiseat setups. To manage notifications about this bug go to:
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
I'm removing the related branches and I'm removing myself from 'assigned to' because I don't think my changes will fix this bug. The issue of getting X to detect NVIDIA cards on non-seat0 seats has been split off to bug #1209008. Attached zip with pam config files. This is the only difference I see: diff -uNr -w a/pam.d/common-session b/pam.d/common-session --- a/pam.d/common-session 2013-08-06 18:28:16.614914993 -0400 +++ b/pam.d/common-session 2013-08-05 15:42:00.0 -0400 @@ -28,5 +28,4 @@ # and here are more per-package modules (the Additional block) sessionrequiredpam_unix.so sessionoptionalpam_systemd.so -sessionoptionalpam_ck_connector.so nox11 # end of pam-auth-update config pam_ck_connector.so is from the libpam-ck-connector package. I have it installed because it's marked as required in raring (it's a dependency of ubuntu-desktop), but I'd rather not have it installed since everything should be using logind instead of consolekit. Perhaps something in lightdm is still using consolekit? You can try installing libpam-ck-connector, but I doubt it'll help (and it may cause problems). ** Changed in: lightdm Assignee: a7x (a7x) = (unassigned) ** Changed in: lightdm (Ubuntu) Assignee: a7x (a7x) = (unassigned) ** Changed in: lightdm Status: In Progress = Confirmed ** Changed in: lightdm (Ubuntu) Status: In Progress = Confirmed ** Branch unlinked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1209008] Re: X fails to detect certain video cards on non-seat0 seats
(continuing the conversation from bug #976124 here since this bug report seems more relevant) but there were problems - huge memory leaks. In attached zip are log files for xorg and lightdm. My .xsession-errors was full of error lines: dconf-CRITICAL **: unable to create file '/home/alberts/.cache/dconf/user': Permission denied. dconf will not work properly. And at least one line of this: WARNING: Could not get session id for session. Check that logind is properly installed and pam_systemd is getting used at login. These did not go away when you added the 'master-of-seat' udev tag? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: From https://bugs.freedesktop.org/show_bug.cgi?id=66851: I have a multiseat setup with a primary on-board Intel graphics device and a secondary Silicon Motion SM501 graphics card. My SM501 is configured via custom xorg.conf with siliconmotion ddx driver, so it exposes no framebuffer devices to e.g. systemd-logind. The same situation is seen e.g. for a NVIDIA graphics card with proprietary drivers. Every time I configure my system to assign my SM501 card with a secondary seat, i.e. not seat0, my X server fails to start, returning a No devices detected error. Nevertheless, when I assign my SM501 card with seat0 and attach my Intel graphics device to secondary seat (via loginctl), both seats load successfully. Investigating the Xorg-server sources, I've found something related to platform bus. I don't know what is it at all, but whatever it means, my Intel graphics card with its open-source drivers implement it, but my siliconmotion driver doesn't. In its current form, Xorg-server probes for platform bus devices as well as legacy PCI bus ones only for seat0. For other seats, it only probes for platform bus devices, hence it never reaches my SM501 card, returning that No devices found error. I don't know if there's a good reason for probing only platform bus devices on non-seat0 seats, but this brings a problem for multiseat setups like mine. This same problem was encoutered by a user with two NVIDIA cards; see bug #976124. A patch was supplied to the upstream bug report, and this patch seems to fix the problem. Note that this bug only affects detection of cards when X is passed the '-seat' argument with a seat name OTHER than seat0. Thus, this only happens in multiseat setups. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977547] Re: doesn't switch to graphical VT when auto login is turned on, (multiseat)
** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: I have a working multiseat system with the 2nd seat Displaylink-based USB touchscreen. the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine to lightdm. If i set autologinup, then the 2nd seat starts fine, but the first seat is blank until i ctrl-alt-f7 at which it logs in. is it this in my Xorg, does it need to VT switch agressively like lightdm usually does, or is it this in my Xorg: Section ServerLayout Option AllowEmptyInput true EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/977547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that getting session list timeout, which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add basic systemd-logind multiseat support
** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075125] Re: Multiseat: only first seat session is marked as active in ConsoleKit
** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1075125 Title: Multiseat: only first seat session is marked as active in ConsoleKit Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: Is there a way LightDM could deal with ConsoleKit so that all LightDM seats can have active sessions as seen by ConsoleKit? Currently, when I set two or more seats with LightDM, only the first one is marked as active in ConsoleKit (as you can see in the output of command ck-list-sessions). The olher seats, once marked as inactive, are not allowed by default to e.g. mount removable media. Just for comparison, a patched GDM[1]+ConsoleKit[2] combination maintained by Huo Cameron at Oracle, available in a7x's multiseat PPA, can give an active CK session for each seat. [1] http://git.gnome.org/browse/gdm/log/?h=wip/multi-seat [2] http://cgit.freedesktop.org/ConsoleKit/log/?h=wip/multi-seat To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1075125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
| `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201124] Re: when second seat user log out, first seat switches to virtual terminal
*** This bug is a duplicate of bug 977547 *** https://bugs.launchpad.net/bugs/977547 ** Branch linked: lp:~a7x/lightdm/multiseat ** Branch unlinked: lp:~a7x/lightdm/multiseat-bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: On multiseat configuration when second seat user logout, first seat switches to virtual terminal. I should press ctrl + alt + f7 to switch back. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
Sounds to me like there's a bug in your udev rules. Does: udevadm info --export-db show the tags and ID_SEAT variable set like you expect? Other comments: * You don't need a udev rule to assign something to seat0. Everything is assigned to seat0 by default. * Probably unrelated but you may need to enable 'user-authority-in-system-dir' in your lightdm.conf: [SeatDefaults] user-authority-in-system-dir=true * I recommend against setting xserver-vt=7 for seat0 -- let LightDM choose the VT number for you. * You don't need to pass -sharevts to X for seat1 -- LightDM will do that for you. If you are still unable to get it to work, please post additional information: * output of 'udevadm info --export-db' * X logs * LightDM logs with debugging turned on (edit /etc/init/lightdm.conf and change 'exec lightdm' to 'exec lightdm -d') -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
Also tried to start x:
sudo X -core -config xorg-seat1.conf -sharevts :1 -auth
/var/run/lightdm/root/:1 -nolisten tcp -novtswitch -seat seat1
X server dosn't start - Fatal server error: (EE) no screens
found(EE)
After that:
sudo X -core -config xorg-seat1.conf -sharevts :1 -auth
/var/run/lightdm/root/:1 -nolisten tcp -novtswitch -seat seat0
X server started, I was able open gedit on second seat screen from
terminal (DISPLAY=:1 gedit)
Except for no keyboard and no mouse, your udevadm output looks OK.
That's unexpected, because this really sounds like a udev rules issue
to me (X finds the card when it's looking for seat0 cards, but not
when it's looking for seat1 cards).
It could be an X problem. I just noticed that you're running saucy
(or at least X from saucy). I've never tried saucy; I'm currently
running xserver-xorg-core from the xorg-edgers PPA on raring. I know
there have been some changes with hardware detection between 1.13.3
and 1.14.2 (specifically with nVidia cards; see bug #1190546), so
maybe X is to blame.
You can try the following, but I doubt they will help:
* tag the video cards with 'master-of-seat' (see
http://www.freedesktop.org/wiki/Software/systemd/multiseat/):
TAG==seat, DEVPATH==/devices/pci:00/:00:01.0/:01:00.0/*,
TAG+=master-of-seat
TAG==seat, DEVPATH==/devices/pci:00/:00:1c.0/:02:00.0/*,
TAG+=master-of-seat
* relax your multiseat rules to include the HDMI audio on the video
card in seat1:
TAG==seat, DEVPATH==/devices/pci:00/:00:1c.0/*,
ENV{ID_SEAT}=seat1, TAG+=seat1
Unfortunately, the following might be your best options for figuring
this out:
* downgrade X to the raring build in xorg-edgers
* switch to non-proprietary nVidia drivers
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/976124
Title:
lightdm multiseat: no login possible
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “lightdm” source package in Precise:
Confirmed
Bug description:
I am testing a multiseat setup with precise:
One XServer is running on intel graphics card, a second one is running
on a DisplayLink (usb video) device.
The two greeters are displayed, but without password fields shown so
it is not possible to login. If auto-login is enabled in lightdm.conf
multiseat works fine.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sat Apr 7 20:35:52 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
Another thing you could try is assign everything to seat1 and see
if you can get just seat 1 to start:
99-multiseat.rules:
TAG==seat, ENV{ID_SEAT}=seat1, TAG+=seat1
TAG==seat, DEVPATH==/devices/pci:00/:00:1c.0/:02:00.0/*,
TAG+=master-of-seat
lightdm.conf:
[SeatDefaults]
user-session=ubuntu
greeter-session=unity-greeter
user-authority-in-system-dir=true
[Seat:1]
xdg-seat=seat1
xserver-command=/usr/bin/X -core -config xorg-seat1.conf -layout Seat1 -s
120 -isolateDevice PCI:2:0:0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/976124
Title:
lightdm multiseat: no login possible
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “lightdm” source package in Precise:
Confirmed
Bug description:
I am testing a multiseat setup with precise:
One XServer is running on intel graphics card, a second one is running
on a DisplayLink (usb video) device.
The two greeters are displayed, but without password fields shown so
it is not possible to login. If auto-login is enabled in lightdm.conf
multiseat works fine.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lightdm 1.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
Uname: Linux 3.2.0-22-generic x86_64
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sat Apr 7 20:35:52 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328)
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add basic systemd-logind multiseat support
1. [...] The common solution, found in proprietary solutions like Userful Multiseat and Windows Multipoint Server, to do the right seat assignment for input devices is an interface of kind Please press Fx key in the keyboard in front of this display, where x is 1 for the first seat, 2 for the second seat, etc. If the keyboard is connected to a hub, all other devices connected to the same hub are automatically assigned to that seat. It would be nice if LightDM could implement such an interface for seat assignment. That is way down the road, and should be the topic of another bug report. This bug report should only be about adding *basic* multiseat support. We must learn how to walk before we can run. 2. Before systemd-logind, all multiseat settings were DISPLAY-oriented, That is incorrect; the :0 in [Seat:0] has nothing to do with the DISPLAY. The part after the colon is an arbitrary string. You can use [Seat:Bob] if you want to; it makes no difference (other than for logging, and only if you install the version of LightDM from my PPA which has some logging improvements). but now IMHO it makes more sense to write these settings in a more seat id-oriented fashion. In lightdm.conf, instead of having [Seat:1] (...) xserver-seat=seat-1 (...) I propose something like [seat-1] (...) xserver-display=:1 (...) Due to user switching, it does not make sense to have an 'xserver-display' setting for a seat -- a single LightDM seat might be associated with multiple X displays. This approach is specially useful for autologin. It make more sense to assign autologin users to seat ids than DISPLAY values. I want, for example, user bob loggind automatically in seat-1, regardless of which is the value of DISPLAY environment variable on that seat. That is currently possible with the version of LightDM in my PPA: [Seat:foo] xserver-seat=seat-1 autologin-user=bob Note that it is important to keep the LightDM seat name and the X seat name independent because LightDM isn't just for launching X. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
** Tags added: multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: In Progress Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Invalid Bug description: [Impact] * A user tries to shut down their machine. They get confused because nothing happens when they click shutdown. * If someone else is logged in, they will have to ask that person to Switch User to log in and log out * If someone else is logged in and you don't know the password of the account, you can't shut down [Test Case] * Have two login accounts * Log both people in, via power cog-lock screen-switch user * lock the screen on current account, via power cog-lock screen * get back to lightdm via switch user * log in to an already logged in account, and try to power off the machine [Regression Potential] * It wasn't possible to shutdown at all before * I can't see a case for a regression, since it never worked to begin with [Original Report] Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown.s To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add compatibility with systemd-logind (for better multiseat support)
I don't think this is a duplicate of bug #930488. That bug was about adding basic logind support, and I view this bug as a request to take it further and add basic multiseat support. For LightDM to completely support multiseat, it should follow the protocol outlined here: http://www.freedesktop.org/wiki/Software/systemd/writing-display-managers/ Just performing steps 3 and 4 under complete porting would get us 90% of the way there. Automatically discovering and reacting to seats appearing and disappearing (steps 1 and 2) would be nice, but that's a fancy feature that can come later (see bug #1190581). ** Summary changed: - Add compatibility with systemd-logind (for better multiseat support) + Add basic systemd-logind multiseat support ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = a7x (a7x) ** Branch linked: lp:~a7x/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: New Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add basic systemd-logind multiseat support
** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: New Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add basic systemd-logind multiseat support
I have uploaded the package in the linked bazaar branch to my PPA (https://launchpad.net/~a7x/+archive/multiseat) along with some backported saucy packages for improved logind support in raring. To install: sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: New Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201124] Re: when second seat user log out, first seat switches to virtual terminal
This is because LightDM assigns each seat a different virtual terminal, and switches to that virtual terminal whenever X is restarted. I have some changes to LightDM in progress to add more complete multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat): sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade More complete instructions can be found by visiting the PPA page. ** Branch linked: lp:~a7x/lightdm/multiseat ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = a7x (a7x) ** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat ** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: On multiseat configuration when second seat user logout, first seat switches to virtual terminal. I should press ctrl + alt + f7 to switch back. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085841] Re: Add basic systemd-logind multiseat support
** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: systemd-logind is arrising to replace ConsoleKit in several Linux distributions (Fedora, Archlinux, Mageia, etc.). It fills the lack of proper multiseat support in ConsoleKit, which is being slowly deprecated. At the moment, only GDM 3.4+ is fully compatible with systemd-logind, which makes it difficult to configure multiseat for other desktop environments than GNOME, specially those suitable for non-accelerated graphics, like XFCE and LXDE. LightDM is becoming the default login manager for such lightweight DEs, and it will improve greatly the multiseat support in these systems when it's fully systemd-logind compliant. I believe that, for the moment, both ConsoleKit and systemd-logind support could coexist in LightDM code. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1075125] Re: Multiseat: only first seat session is marked as active in ConsoleKit
ConsoleKit is going away, and will be completely replaced by systemd's logind in saucy. Partial support for logind is already in raring. I have some changes to LightDM in progress to add more complete logind multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat): sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade More complete instructions can be found by visiting the PPA page. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: New = In Progress ** Branch linked: lp:~a7x/lightdm/multiseat ** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1075125 Title: Multiseat: only first seat session is marked as active in ConsoleKit Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: Is there a way LightDM could deal with ConsoleKit so that all LightDM seats can have active sessions as seen by ConsoleKit? Currently, when I set two or more seats with LightDM, only the first one is marked as active in ConsoleKit (as you can see in the output of command ck-list-sessions). The olher seats, once marked as inactive, are not allowed by default to e.g. mount removable media. Just for comparison, a patched GDM[1]+ConsoleKit[2] combination maintained by Huo Cameron at Oracle, available in a7x's multiseat PPA, can give an active CK session for each seat. [1] http://git.gnome.org/browse/gdm/log/?h=wip/multi-seat [2] http://cgit.freedesktop.org/ConsoleKit/log/?h=wip/multi-seat To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1075125/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
LightDM currently assigns each seat a different VT, and each seat tries to switch to its own VT when starting X. If I understand correctly, these switches compete with each other, causing the problem. The proper solution is to have only the primary seat switch VTs, then have all other seats share that VT. LightDM doesn't currently support this, but I have some changes to LightDM in progress to add more complete multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat): sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade More complete instructions can be found by visiting the PPA page. ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) = a7x (a7x) ** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: Confirmed = In Progress ** Branch linked: lp:~a7x/lightdm/multiseat ** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that getting session list timeout, which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
LightDM currently assigns each seat a different VT and switches to that
VT when starting X. This is why hitting Ctrl-Alt-F7 and Ctrl-Alt-F8
switch between the two seats.
The proper way to handle multiseat is to have only the primary seat
switch to a VT, then have all other seats share that VT with the
-sharevts argument. LightDM doesn't currently support this, but I have
some changes to LightDM in progress to add more complete multiseat
support. If you are using Ubuntu, please try installing the version of
LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt-get upgrade
More complete instructions can be found by visiting the PPA page.
** Changed in: lightdm
Assignee: (unassigned) = a7x (a7x)
** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) = a7x (a7x)
** Changed in: lightdm (Ubuntu)
Status: Confirmed = In Progress
** Changed in: lightdm
Status: New = In Progress
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
[Desktop-packages] [Bug 812170] Re: Request support for unhandled (no greeter) sessions
** Tags added: multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/812170 Title: Request support for unhandled (no greeter) sessions Status in Light Display Manager: Triaged Status in “lightdm” package in Ubuntu: Triaged Bug description: There is a particular approach of multiseat in which there is only one video card with multiple outputs (some authors refer to that variant as Zaphod multiseat). In this case, to obtain several seats there is just one X session running on the extended desktop with no greeter at all. Over that X session, there are several Xephyr instances which provide the various seats. Every xephyr instance is adjusted to fit the its output device and one greeter instance runs over every Xephyr session. Previously the parameter handled allowed to decide if the greeter should be executed for a given session. The two Xephyr sessions were handled but no the base X session. This feature seems to be currently missing in lightdm. Additional information on this multiseat type: http://netpatia.blogspot.com/2006/09/multiseat-computer-with-ubuntu.html To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/812170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976124] Re: lightdm multiseat: no login possible
I have some changes to LightDM in progress to add more complete multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat): sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade More complete instructions can be found by visiting the PPA page. Related bugs: * bug #903194: multiseat not set up correctly * bug #997483: VT_WAITACTIVE does not work well with a multiseat setup * bug #1075125: Multiseat: only first seat session is marked as active in ConsoleKit * bug #1085841: Add basic systemd-logind multiseat support * bug #1171680: Add option if LightDM can use VTs * bug #1201124: when second seat user log out, first seat switches to virtual terminal ** Also affects: lightdm Importance: Undecided Status: New ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: Robert Ancell (robert-ancell) = a7x (a7x) ** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: Confirmed = In Progress ** Branch linked: lp:~a7x/lightdm/multiseat ** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing a multiseat setup with precise: One XServer is running on intel graphics card, a second one is running on a DisplayLink (usb video) device. The two greeters are displayed, but without password fields shown so it is not possible to login. If auto-login is enabled in lightdm.conf multiseat works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 20:35:52 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201124] Re: when second seat user log out, first seat switches to virtual terminal
*** This bug is a duplicate of bug 977547 *** https://bugs.launchpad.net/bugs/977547 ** This bug has been marked a duplicate of bug 977547 doesn't switch to graphical VT when auto login is turned on, (multiseat) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: On multiseat configuration when second seat user logout, first seat switches to virtual terminal. I should press ctrl + alt + f7 to switch back. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977547] Re: doesn't switch to graphical VT when auto login is turned on, (multiseat)
This is because LightDM assigns each seat a different virtual terminal, and switches to that virtual terminal whenever X is (re)started. I have some changes to LightDM in progress to add more complete multiseat support. If you are using Ubuntu, please try installing the version of LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat): sudo apt-add-repository ppa:a7x/multiseat sudo apt-get update sudo apt-get upgrade More complete instructions can be found by visiting the PPA page. ** Also affects: lightdm Importance: Undecided Status: New ** Changed in: lightdm Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = a7x (a7x) ** Changed in: lightdm Status: New = In Progress ** Changed in: lightdm (Ubuntu) Status: Confirmed = In Progress ** Branch linked: lp:~a7x/lightdm/multiseat ** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: I have a working multiseat system with the 2nd seat Displaylink-based USB touchscreen. the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine to lightdm. If i set autologinup, then the 2nd seat starts fine, but the first seat is blank until i ctrl-alt-f7 at which it logs in. is it this in my Xorg, does it need to VT switch agressively like lightdm usually does, or is it this in my Xorg: Section ServerLayout Option AllowEmptyInput true EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/977547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1114198] Re: [power]: gnome-settings-daemon crashed with signal 5 in _XReply()
** Tags added: badwindow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1114198 Title: [power]: gnome-settings-daemon crashed with signal 5 in _XReply() Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Don't know details ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: gnome-settings-daemon 3.6.4-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sun Feb 3 10:57:57 2013 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationDate: Installed on 2013-01-30 (3 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130129) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XSyncQueryCounter () from /usr/lib/i386-linux-gnu/libXext.so.6 gpm_idletime_get_time () from /usr/lib/gnome-settings-daemon-3.0/libpower.so Title: [power]: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: (gnome-settings-daemon:1829): Gdk-ERROR **: The program 'gnome-settings-daemon' received an X Window System error. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 599 error_code 3 request_code 18 minor_code 0) gnome-session[1754]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1114198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 949126] Re: [Regression] X resources take no effect
also affects emacs24 ** Also affects: emacs24 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs23 in Ubuntu. https://bugs.launchpad.net/bugs/949126 Title: [Regression] X resources take no effect Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: New Bug description: Ubuntu 12.04 Emacs 23.3+1-1ubuntu8 I'm setting Emacs*useXIM: false in ~/.Xresources file to use Emacs' internal input method, but Emacs on Precise ignores this setting, so I cannot use the internal input method. It's very annoying that XIM unwantedly handles the key events! Also, all of the other X resources are ignored and the settings are not working at all. == Regression details == Discovered in version: emacs23 23.3+1-1ubuntu8 Last known good version: emacs23 23.3+1-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/949126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
@bradleydsmith: Sounds like you're experiencing a different bug. You may want to file a new bug report for it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version: 2:1.13.0-0ubuntu5 Last known good version: 2:1.11.4-0ubuntu10.8 To manage notifications
[Desktop-packages] [Bug 430981] Re: keybindings not remembered on reboot
@unwrecker and @alexandervolfman: This bug has been fixed and so this bug report won't be reopened. However, a regression with similar symptoms has appeared in 12.10 (Quantal). See bug #1063617. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/430981 Title: keybindings not remembered on reboot Status in “gnome-session” package in Ubuntu: Fix Released Status in “gnome-session” source package in Karmic: Fix Released Bug description: Hi, after recent upgrades, changes to the keybindings in compiz or in SystemPreferencesKeyboard Shortcuts are not remembered anymore after logging in. I tried adding a shortcut key to open a terminal, and it works fine, but I expect it to be saved after I reboot, as it used to be. Now, upon reboot, the keyboard shortcut no longer works. Same problem with CCSM; changing keybindings for Ring Switcher doesn't last after reboot. Using Karmic AMD 64 with latest updates this morning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/430981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Looks OK to me, except for a minor issue in debian/changelog: LP: 1041063 should be LP: #1041063 (notice the missing #). ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version:
[Desktop-packages] [Bug 570151] Re: mouse stuck jumping between screens
@Dan: I believe you are experiencing a different but similar bug -- please open a new bug report. (Even if it is the same bug, it is likely caused by a regression and should thus have a new bug report. But either way, this bug is marked as fixed and will therefore be ignored by Ubuntu developers. So no matter what, your best chance of getting the issue resolved is to open a new bug report.) Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/570151 Title: mouse stuck jumping between screens Status in “xorg-server” package in Ubuntu: Fix Released Bug description: This url pretty much has the exact description of the problem I have http://forums.gentoo.org/viewtopic-t-818488-start-0.html and their solution was to downgrade to xserver 1.6 but I don't see how to do that with ubuntu. I have two 8800GTS video cards and two monitors on each card. With Xinerama enabled and moving the mouse between screens the mouse will get stuck. At that point Xorg will increase in memory usage very quickly it looks like a hundred megs every couple seconds. I can go to another machine and kill Xorg then it will restart and I can use the system again but this is very frustrating. This setup has been working fine for a long time now but it seems that Xinerama is xorg 1.7 is just kind of broken. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-core 2:1.7.6-2ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 26 07:06:11 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.31-20-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg Lsusb: Bus 002 Device 073: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 002 Device 093: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Tyan Computer Corporation MCP55 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=d907ccb1-3f8e-4f38-9ebe-7bec483ed266 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: xorg-server Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension RANDR missing on display :0.0. RandR extension missing dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 2.05.2915 dmi.board.name: S2915 dmi.board.vendor: Tyan Computer Corporation dmi.board.version: REFERENCE dmi.chassis.type: 17 dmi.chassis.vendor: NVIDIA dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr2.05.2915:bd04/04/2008:svnTyanComputerCorporation:pnMCP55:pvrREFERENCE:rvnTyanComputerCorporation:rnS2915:rvrREFERENCE:cvnNVIDIA:ct17:cvr: dmi.product.name: MCP55 dmi.product.version: REFERENCE dmi.sys.vendor: Tyan Computer Corporation system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1091976] [NEW] fix uploaded to precise-proposed for a bug that doesn't exist
Public bug reported: http://launchpad.net/ubuntu/+source/xorg-server/2:1.11.4-0ubuntu10.10 was uploaded to precise-proposed supposedly to fix bug #1041063. However, the version of xorg-server in precise is unaffected by that bug so the change should not be necessary. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: regression-proposed ** Summary changed: - fix uploaded for a bug that doesn't exist + fix uploaded to precise-proposed for a bug that doesn't exist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1091976 Title: fix uploaded to precise-proposed for a bug that doesn't exist Status in “xorg-server” package in Ubuntu: New Bug description: http://launchpad.net/ubuntu/+source/xorg-server/2:1.11.4-0ubuntu10.10 was uploaded to precise-proposed supposedly to fix bug #1041063. However, the version of xorg-server in precise is unaffected by that bug so the change should not be necessary. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1091976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
filed regression-proposed bug #1091976 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version: 2:1.13.0-0ubuntu5 Last known good version: 2:1.11.4-0ubuntu10.8 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
As I noted before in comment #25, this bug was introduced upstream in 1.13. Precise has version 1.11.4, so it should not be affected. How can something be fixed if it is not broken? ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
Attached is a debdiff for cairo (against the quantal version) that I believe partially fixes this problem. The other part is a change to gnome-control-center, and I will upload that debdiff shortly. For cairo, I applied the following patches: http://cgit.freedesktop.org/cairo/commit/?id=83759e7d592c5d7b12b2341574fd584fe5e0fb5a http://cgit.freedesktop.org/cairo/commit/?id=df6780442feba5c0c9404353177f24913b58bd32 http://cgit.freedesktop.org/cairo/commit/?id=f34b87f6d76cbea93acd4a8c73c8c6a6b412a302 The above patches are in cairo versions 1.12.4 and later, so raring is not affected. I uploaded the modified cairo package to my PPA (https://launchpad.net/~a7x/+archive/bug1043769) and it has finished building. To install: sudo apt-add-repository ppa:a7x/bug1043769 sudo apt-get update sudo apt-get upgrade ** Patch added: debdiff for cairo (quantal) https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043769/+attachment/3460897/+files/quantal-cairo-debdiff.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Fix Released Status in GNOME Control Center: Fix Released Status in “cairo” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
And here is the debdiff for gnome-control-center (against the quantal version). For gnome-control-center, I applied the following patches: http://git.gnome.org/browse/gnome-control-center/commit/?id=c1857b0f9c80434890679ace83865db5d2565fa6 http://git.gnome.org/browse/gnome-control-center/commit/?id=a61f0654b98357283ef68bea6d827aabc0a2779e The above patches are in gnome-control-center versions 3.6.0 and later, so raring is not affected. I uploaded the modified gnome-control-center package to my PPA and it has finished building. Please try these packages and let me know if they work for you. ** Patch added: debdiff for gnome-control-center (quantal) https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043769/+attachment/3460903/+files/quantal-gnome-control-center-debdiff.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Fix Released Status in GNOME Control Center: Fix Released Status in “cairo” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
** Description changed: + [Impact] + + Users with multiple displays are unable to change display settings + (arrange displays, change resolutions, change the primary display, etc.) + with 'gnome-control-center display' unless they happen to know to switch + focus to another window and switch back again between every mouse click. + + [Test Case] + + 1. Have a multi monitor setup with 2 (or more) monitors + 2. Open the display settings applet in the control center + 3. Click on the monitor that is not currently selected + 4. Try to select the originally selected monitor by clicking on it + + [Regression Potential] + + The patches in the attached debdiffs are from the upstream git + repositories and are in the latest upstream releases. Raring has been + using these upstream releases for some time now; any regressions likely + would have showed up in Raring. + + That being said, the cairo change is potentially risky, as it alters + some low-level behaviors and many packages depend on cairo. The changes + to gnome-control-center are limited to the Displays panel; any + regressions should only affect that panel (and that panel is already + severely broken with multiple displays). + + [Original Bug Report] + Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: - TERM=xterm - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: - activity-log-manager-control-center 0.9.4-0ubuntu3 - deja-dup23.90-0ubuntu1 - gnome-control-center-signon 0.0.13-0ubuntu1 - indicator-datetime 12.10.0-0ubuntu1 + activity-log-manager-control-center 0.9.4-0ubuntu3 + deja-dup23.90-0ubuntu1 + gnome-control-center-signon 0.0.13-0ubuntu1 + indicator-datetime 12.10.0-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Fix Released Status in GNOME Control Center: Fix Released Status in “cairo” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: [Impact] Users with multiple displays are unable to change display settings (arrange displays, change resolutions, change the primary display, etc.) with 'gnome-control-center display' unless they happen to know to switch focus to another window and switch back again between every mouse click. [Test Case] 1. Have a multi monitor setup with 2 (or more) monitors 2. Open the display settings applet in the control center 3. Click on the monitor that is not currently selected 4. Try to select the originally selected monitor by clicking on it [Regression Potential] The patches in the attached debdiffs are from the upstream git repositories and are in the latest upstream releases. Raring has been using these upstream releases for some time now; any regressions likely would have showed up in Raring. That being said, the cairo change is potentially risky, as it alters some low-level behaviors and many packages depend on cairo. The changes to gnome-control-center are limited to the Displays panel; any regressions should only affect that panel (and that panel is already severely broken with multiple displays). [Original Bug Report] Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should
[Desktop-packages] [Bug 1076955] Re: Display options stuck on only one screen icon
*** This bug is a duplicate of bug 1043769 *** https://bugs.launchpad.net/bugs/1043769 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #1043769, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1043769 Monitor image not clickable in display settings after the first time -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1076955 Title: Display options stuck on only one screen icon Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: When editing display settings for multiple monitors, the selection is stuck on only one monitor. I usually have to go back to the settings categories and re-enter display settings to select another screen icon. Expected behaviour - freely select screens. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu19 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Fri Nov 9 11:42:24 2012 InstallationDate: Installed on 2012-10-19 (20 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu4 deja-dup24.0-0ubuntu1 gnome-control-center-signon 0.0.18-0ubuntu1 indicator-datetime 12.10.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1076955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
** Bug watch added: GNOME Bug Tracker #681475 https://bugzilla.gnome.org/show_bug.cgi?id=681475 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=681475 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in GNOME Control Center: Unknown Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
I believe the following upstream patches will fix this (I have not tried them yet): http://git.gnome.org/browse/gnome-control-center/commit/?id=c1857b0f9c80434890679ace83865db5d2565fa6 http://git.gnome.org/browse/gnome-control-center/commit/?id=a61f0654b98357283ef68bea6d827aabc0a2779e http://cgit.freedesktop.org/cairo/commit/?id=f34b87f6d76cbea93acd4a8c73c8c6a6b412a302 ** Bug watch added: freedesktop.org Bugzilla #54732 https://bugs.freedesktop.org/show_bug.cgi?id=54732 ** Also affects: cairo via https://bugs.freedesktop.org/show_bug.cgi?id=54732 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Unknown Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
The cairo bug report is linked because apparently the fix for the gnome- control-center bug exposed a bug in cairo. I'm not sure if quantal already has that cairo fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Unknown Status in GNOME Control Center: Fix Released Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
The quantal version of cairo does not have the fix referenced above, so I'm marking this bug report as also affecting the cairo package. ** Also affects: cairo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Unknown Status in GNOME Control Center: Fix Released Status in “cairo” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1043769] Re: Monitor image not clickable in display settings after the first time
Additional cairo patches needed: http://cgit.freedesktop.org/cairo/commit/?id=df6780442feba5c0c9404353177f24913b58bd32 http://cgit.freedesktop.org/cairo/commit/?id=08e3f4614b688331534d72f46c9c3e9f292d0216 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time Status in Cairo Graphics Library: Fix Released Status in GNOME Control Center: Fix Released Status in “cairo” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Have a multi monitor setup with 2 monitors * Open the display settings applet in the control center * Click on the monitor that is not currently selected * Click on the monitor that was initially selected Expected result: * The second click should select again the clicked monitor Actual result: * The second click fails to select the clicked monitor, selection remains where it is If you focus another application and focus back to the display settings window, then you can move the selection again for one single time, then the bug appears again until you switch focus again. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu13 ProcVersionSignature: Ubuntu 3.5.0-13.13-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu3 Architecture: i386 Date: Thu Aug 30 13:14:48 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-08-29 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.13-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082952] Re: Lightdm does not display correct resolution in multimonitor setup
Changing affected package to unity-greeter (the login screen launched by lightdm) since lightdm itself doesn't do anything graphical. ** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1082952 Title: Lightdm does not display correct resolution in multimonitor setup Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: When a second Monitor is connected, lightdm displays wrong resolution (the one from the smaller) on the primary monitor. I have one display with 1900x1200 and a secondary monitor with 1280x1024. When lightdm starts it gets displayed on both monitors with 1280x1024 which looks terrible on the primary instead of using the native resolution on both or only displaying on the primary. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 25 20:17:10 2012 MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1082952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082952] Re: Lightdm does not display correct resolution in multimonitor setup
Workaround: 1. log in 2. use xrandr or the Displays control utility to configure your monitors how you'd like them to be configured in the login screen 3. copy ~/.config/monitors.xml to /var/lib/lightdm/.config -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1082952 Title: Lightdm does not display correct resolution in multimonitor setup Status in “unity-greeter” package in Ubuntu: Confirmed Bug description: When a second Monitor is connected, lightdm displays wrong resolution (the one from the smaller) on the primary monitor. I have one display with 1900x1200 and a secondary monitor with 1280x1024. When lightdm starts it gets displayed on both monitors with 1280x1024 which looks terrible on the primary instead of using the native resolution on both or only displaying on the primary. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Nov 25 20:17:10 2012 MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1082952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1082211] Re: restart impossible when a remote ssh session is running
Added consolekit to the affected packages because I believe this is the package responsible (maybe with policykit?) for denying shut down or restart based on who's logged in. ** Also affects: consolekit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1082211 Title: restart impossible when a remote ssh session is running Status in “consolekit” package in Ubuntu: Confirmed Status in “lightdm” package in Ubuntu: Confirmed Bug description: (assigning to lightdm, although it's broader than that. Not clear which component is to blame exactly). Let X be a laptop running ubuntu 12.10. It's an x86-64 cpu for that matter, but no one cares. Assume an ssh server is running on X, and someone is logged in via ssh from another machine Y to machine X. Now if X is showing a lightdm login screen, there is no way the ``restart'' button (from the top-right menu) can work. It is simply ignored. There is no message either. If some user is logged on X, and he opens up the top-right menu and goes to ``restart'', one of two things may happen. - If the remote session is under this very user, then the session is killed, and the computer restarts. - If the remote session is under another user (root, for the situation I tried), then the user's session is nuked, but the computer does not restart, and returns back to the lightdm login screen. I find this quite irritating. Ssh sessions to my laptop may happen. When I have physical access to it, I would like to be able to restart/shut down the machine without having to either do a dirty shutdown (5s press) or hunt manually for ssh session and kill -9 them, or ctrl-alt-f1, root login, and reboot. I would conceive it if someone considers it's ''dangerous'' to kill incoming ssh sessions. Not that I share this opinion, but I imagine it may exist. If so, would it be possible, please, to have a dialog box like ``yes, I mean it'' if the system decides it's perhaps unwise to proceed to reboot ? Best, E. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/consolekit/+bug/1082211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Now that the fix has been published to quantal-updates, I have removed the version from my PPA. If you installed the version from my PPA, please downgrade from 2:1.13.0-0ubuntu7~12.10 to 2:1.13.0-0ubuntu6.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Released Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Yes, the proposed package fixes this bug. I booted off of the Quantal live CD, upgraded xserver-xorg-core and xserver-common to the proposed version, used 'gnome-session-quit' to cause X to exit and respawn, then logged in again as the ubuntu user to test it out. ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Fix Committed Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] While using virtualbox, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1086132] [NEW] x11vnc -solid or -xrefresh options cause unity-greeter to segfault in gdk_window_get_type_hint()
Public bug reported: Running x11vnc with either the -solid or -xrefresh options causes unity- greeter to segfault once the VNC client connects. To reproduce (assuming two machines named 'local-machine' and 'remote- machine'): 1. ensure that nobody is logged in to 'remote-machine' (unity-greeter should be displayed) 2. on 'local-machine' run: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -solid black' or: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -xrefresh 5.0' 3. on 'local-machine', use a VNC client to connect to localhost:5900 unity-greeter on 'remote-machine' will then crash (causing lightdm to respawn it), and the x11vnc program will print caught XIO error and exit with a non-zero return code. Neither of these options cause any problems when connecting via VNC when a user is already logged in. Additional details: $ lsb_release -rdc Description:Ubuntu 12.10 Release:12.10 Codename: quantal unity-greeter version: 12.10.4-0ubuntu5 x11vnc version: 0.9.13-1ubuntu1 libvncserver0 version: 0.9.9+dfsg-1 lightdm version: 1.4.0-0ubuntu2 ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Attachment added: backtrace.log https://bugs.launchpad.net/bugs/1086132/+attachment/3450844/+files/backtrace.log ** Package changed: lightdm (Ubuntu) = unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1086132 Title: x11vnc -solid or -xrefresh options cause unity-greeter to segfault in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: New Bug description: Running x11vnc with either the -solid or -xrefresh options causes unity-greeter to segfault once the VNC client connects. To reproduce (assuming two machines named 'local-machine' and 'remote- machine'): 1. ensure that nobody is logged in to 'remote-machine' (unity-greeter should be displayed) 2. on 'local-machine' run: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -solid black' or: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -xrefresh 5.0' 3. on 'local-machine', use a VNC client to connect to localhost:5900 unity-greeter on 'remote-machine' will then crash (causing lightdm to respawn it), and the x11vnc program will print caught XIO error and exit with a non-zero return code. Neither of these options cause any problems when connecting via VNC when a user is already logged in. Additional details: $ lsb_release -rdc Description:Ubuntu 12.10 Release:12.10 Codename: quantal unity-greeter version: 12.10.4-0ubuntu5 x11vnc version: 0.9.13-1ubuntu1 libvncserver0 version: 0.9.9+dfsg-1 lightdm version: 1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1086132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086132] Re: x11vnc -solid or -xrefresh options cause unity-greeter to segfault in gdk_window_get_type_hint()
this may or may not be related to bug #1048131 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1086132 Title: x11vnc -solid or -xrefresh options cause unity-greeter to segfault in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: New Bug description: Running x11vnc with either the -solid or -xrefresh options causes unity-greeter to segfault once the VNC client connects. To reproduce (assuming two machines named 'local-machine' and 'remote- machine'): 1. ensure that nobody is logged in to 'remote-machine' (unity-greeter should be displayed) 2. on 'local-machine' run: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -solid black' or: ssh -L 5900:localhost:5900 remote-machine 'sudo \ x11vnc -localhost -auth /var/lib/lightdm/.Xauthority \ -display :0 -rfbport 5900 -nopw -xrefresh 5.0' 3. on 'local-machine', use a VNC client to connect to localhost:5900 unity-greeter on 'remote-machine' will then crash (causing lightdm to respawn it), and the x11vnc program will print caught XIO error and exit with a non-zero return code. Neither of these options cause any problems when connecting via VNC when a user is already logged in. Additional details: $ lsb_release -rdc Description:Ubuntu 12.10 Release:12.10 Codename: quantal unity-greeter version: 12.10.4-0ubuntu5 x11vnc version: 0.9.13-1ubuntu1 libvncserver0 version: 0.9.9+dfsg-1 lightdm version: 1.4.0-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1086132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
this may or may not be related to bug #1086132 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: Incomplete Status in “unity-greeter” source package in Quantal: Won't Fix Status in “unity-greeter” source package in Raring: Incomplete Bug description: This happened after the upgrade from precise to quantal and a reboot. Once unity loaded, this error happened. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: unity-greeter 12.10.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 03:46:17 2012 ExecutablePath: /usr/sbin/unity-greeter InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /usr/sbin/unity-greeter ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fbd0a2ceb80 gdk_window_get_type_hint: mov 0x18(%rdi),%rax PC (0x7fbd0a2ceb80) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity-greeter StacktraceTop: gdk_window_get_type_hint () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() UpgradeStatus: Upgraded to quantal on 2012-09-08 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
** Tags added: multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that getting session list timeout, which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977547] Re: doesn't switch to graphical VT when auto login is turned on, (multiseat)
** Tags added: multiseat -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) Status in “lightdm” package in Ubuntu: Confirmed Bug description: I have a working multiseat system with the 2nd seat Displaylink-based USB touchscreen. the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine to lightdm. If i set autologinup, then the 2nd seat starts fine, but the first seat is blank until i ctrl-alt-f7 at which it logs in. is it this in my Xorg, does it need to VT switch agressively like lightdm usually does, or is it this in my Xorg: Section ServerLayout Option AllowEmptyInput true EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/977547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
This bug was introduced upstream in xorg-server 1.13 (Git commit 749a593), so unless that particular commit was backported to the xorg- server package for precise, this bug does not affect precise. ** Changed in: xorg-server (Ubuntu Precise) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Triaged Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] On affected hardware, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
I backported xorg-server-2:1.13.0-0ubuntu7 to quantal and uploaded it to my PPA (https://launchpad.net/~a7x/+archive/bug1041063). It has finished building. To install: sudo apt-add-repository ppa:a7x/bug1041063 sudo apt-get update sudo apt-get upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Precise: Invalid Status in “xorg-server” source package in Quantal: Triaged Status in “xorg-server” source package in Raring: Fix Released Status in Fedora: Unknown Bug description: [Impact] When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. [Fix] Patch cherrypicked from upstream [Test Case] On affected hardware, move mouse around. Expected: Smooth mouse movement Actual: Jerky movement with mouse jumping to 0,0 periodically [Regression Potential] Low. No known issues, and test has received review and testing upstream, and so is not expected to show regressions. Things to watch for include X server crashes, and strange mouse behaviors, both of which should be pretty obvious. [Recommended Validation] * Confirmation from a couple affected users * 1-week minimum time in -proposed to identify regressions [Original Report] I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
Also a problem in Ubuntu.
** Tags added: multiseat
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
New
Status in “lightdm” package in Ubuntu:
New
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
| `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
In general X behaves poorly with Linux virtual terminals, but in Natty I
was able to get gdm+consolekit (patched with the multiseat patches; see
https://launchpad.net/~a7x/+archive/multiseat) to handle multiseat
properly. I had it configured with the -sharevts flag set only on the
second of two seats and both seats came up properly. So either
something has changed in X to break this or it's a bug/limitation in
lightdm.
I'm seeing this problem in Quantal (haven't tried Oneiric or Precise).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
New
Status in “lightdm” package in Ubuntu:
New
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
| `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Attached is an updated debdiff for quantal. I've uploaded this version to my PPA and it should finish building in a few hours. To install: sudo apt-add-repository ppa:a7x/bug1041063 sudo apt-get update sudo apt-get upgrade ** Patch removed: debdiff for quantal https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1041063/+attachment/3380689/+files/debdiff.patch ** Patch added: debdiff for quantal https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1041063/+attachment/3412425/+files/debdiff-quantal.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version: 2:1.13.0-0ubuntu5 Last known good version: 2:1.11.4-0ubuntu10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
And here is the debdiff for raring. This version has also been uploaded to my PPA and has already finished building. ** Patch added: debdiff for raring https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1041063/+attachment/3412426/+files/debdiff-raring.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version: 2:1.13.0-0ubuntu5 Last known good version: 2:1.11.4-0ubuntu10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 570151] Re: mouse stuck jumping between screens
@andrew: I may be wrong, but I think you are experiencing a different bug. Does your mouse cursor behave like the video in comment #15? Nobody has reported seeing this bug since Oneiric, and it went away for me when I upgraded my Natty X server to the version used in Oneiric. So, I believe this bug was fixed in Oneiric. If you are experiencing this exact same bug, that's unfortunate and surprising news. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/570151 Title: mouse stuck jumping between screens Status in “xorg-server” package in Ubuntu: Incomplete Bug description: This url pretty much has the exact description of the problem I have http://forums.gentoo.org/viewtopic-t-818488-start-0.html and their solution was to downgrade to xserver 1.6 but I don't see how to do that with ubuntu. I have two 8800GTS video cards and two monitors on each card. With Xinerama enabled and moving the mouse between screens the mouse will get stuck. At that point Xorg will increase in memory usage very quickly it looks like a hundred megs every couple seconds. I can go to another machine and kill Xorg then it will restart and I can use the system again but this is very frustrating. This setup has been working fine for a long time now but it seems that Xinerama is xorg 1.7 is just kind of broken. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-core 2:1.7.6-2ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 26 07:06:11 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.31-20-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg Lsusb: Bus 002 Device 073: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 002 Device 093: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Tyan Computer Corporation MCP55 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=d907ccb1-3f8e-4f38-9ebe-7bec483ed266 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: xorg-server Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension RANDR missing on display :0.0. RandR extension missing dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 2.05.2915 dmi.board.name: S2915 dmi.board.vendor: Tyan Computer Corporation dmi.board.version: REFERENCE dmi.chassis.type: 17 dmi.chassis.vendor: NVIDIA dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr2.05.2915:bd04/04/2008:svnTyanComputerCorporation:pnMCP55:pvrREFERENCE:rvnTyanComputerCorporation:rnS2915:rvrREFERENCE:cvnNVIDIA:ct17:cvr: dmi.product.name: MCP55 dmi.product.version: REFERENCE dmi.sys.vendor: Tyan Computer Corporation system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 570151] Re: mouse stuck jumping between screens
@andrew: I'm certain you are experiencing a different bug -- you should open a new bug report. This bug is not limited to nVidia (at least two people here have ATI/AMD video cards, myself included), wrapping around was never a symptom, and this bug was fixed in Oneiric. ** Changed in: xorg-server (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/570151 Title: mouse stuck jumping between screens Status in “xorg-server” package in Ubuntu: Fix Released Bug description: This url pretty much has the exact description of the problem I have http://forums.gentoo.org/viewtopic-t-818488-start-0.html and their solution was to downgrade to xserver 1.6 but I don't see how to do that with ubuntu. I have two 8800GTS video cards and two monitors on each card. With Xinerama enabled and moving the mouse between screens the mouse will get stuck. At that point Xorg will increase in memory usage very quickly it looks like a hundred megs every couple seconds. I can go to another machine and kill Xorg then it will restart and I can use the system again but this is very frustrating. This setup has been working fine for a long time now but it seems that Xinerama is xorg 1.7 is just kind of broken. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-core 2:1.7.6-2ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 26 07:06:11 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.31-20-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg Lsusb: Bus 002 Device 073: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 002 Device 093: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Tyan Computer Corporation MCP55 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=d907ccb1-3f8e-4f38-9ebe-7bec483ed266 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: xorg-server Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension RANDR missing on display :0.0. RandR extension missing dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 2.05.2915 dmi.board.name: S2915 dmi.board.vendor: Tyan Computer Corporation dmi.board.version: REFERENCE dmi.chassis.type: 17 dmi.chassis.vendor: NVIDIA dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr2.05.2915:bd04/04/2008:svnTyanComputerCorporation:pnMCP55:pvrREFERENCE:rvnTyanComputerCorporation:rnS2915:rvrREFERENCE:cvnNVIDIA:ct17:cvr: dmi.product.name: MCP55 dmi.product.version: REFERENCE dmi.sys.vendor: Tyan Computer Corporation system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 570151] Re: mouse stuck jumping between screens
Since nobody has reported seeing this bug since Oneiric, and now that Natty has reached end-of-life, I'm closing this as fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/570151 Title: mouse stuck jumping between screens Status in “xorg-server” package in Ubuntu: Fix Released Bug description: This url pretty much has the exact description of the problem I have http://forums.gentoo.org/viewtopic-t-818488-start-0.html and their solution was to downgrade to xserver 1.6 but I don't see how to do that with ubuntu. I have two 8800GTS video cards and two monitors on each card. With Xinerama enabled and moving the mouse between screens the mouse will get stuck. At that point Xorg will increase in memory usage very quickly it looks like a hundred megs every couple seconds. I can go to another machine and kill Xorg then it will restart and I can use the system again but this is very frustrating. This setup has been working fine for a long time now but it seems that Xinerama is xorg 1.7 is just kind of broken. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-core 2:1.7.6-2ubuntu7 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Apr 26 07:06:11 2010 DkmsStatus: nvidia-current, 195.36.15, 2.6.31-20-generic, x86_64: installed nvidia-current, 195.36.15, 2.6.32-21-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg Lsusb: Bus 002 Device 073: ID 1532:0101 Razer USA, Ltd Copperhead Mouse Bus 002 Device 093: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0 Bus 002 Device 002: ID 0557:8021 ATEN International Co., Ltd Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Tyan Computer Corporation MCP55 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=d907ccb1-3f8e-4f38-9ebe-7bec483ed266 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: xorg-server Xrandr: Error: command ['xrandr', '--verbose'] failed with exit code 1: Xlib: extension RANDR missing on display :0.0. RandR extension missing dmi.bios.date: 04/04/2008 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 2.05.2915 dmi.board.name: S2915 dmi.board.vendor: Tyan Computer Corporation dmi.board.version: REFERENCE dmi.chassis.type: 17 dmi.chassis.vendor: NVIDIA dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr2.05.2915:bd04/04/2008:svnTyanComputerCorporation:pnMCP55:pvrREFERENCE:rvnTyanComputerCorporation:rnS2915:rvrREFERENCE:cvnNVIDIA:ct17:cvr: dmi.product.name: MCP55 dmi.product.version: REFERENCE dmi.sys.vendor: Tyan Computer Corporation system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen in llvmpipe session
According to the upstream bug report, this is a bug in the X server, not VirtualBox. It just happens to be that the bug is very noticeable in VirtualBox. ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=54353 Importance: Unknown Status: Unknown ** Package changed: virtualbox-guest-additions (Ubuntu) = xorg-server (Ubuntu) ** Summary changed: - mouse pointer periodically leaps to left and top of screen in llvmpipe session + mouse pointer periodically leaps to left and top of screen with absolute pointing devices -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Regression caused by http://cgit.freedesktop.org/xorg/xserver/commit/?id=749a593e49adccdf1225be28a521412ec85333f4 in xorg-xserver 1.13, fixed upstream in http://cgit.freedesktop.org/xorg/xserver/commit/?id=3d1051aecbb1955084804133cacd12c7f696833a (not yet released) ** Tags added: regression-release ** Description changed: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: - vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed - vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed + vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed + vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: - Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: - LANGUAGE=en_AU:en - TERM=xterm - PATH=(custom, no user) - LANG=en_AU.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_AU:en + TERM=xterm + PATH=(custom, no user) + LANG=en_AU.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 + + == Regression details == + Discovered in version: 2:1.13.0-0ubuntu5 + Last known good version: 2:1.11.4-0ubuntu10.8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more
[Desktop-packages] [Bug 1041063] Re: mouse pointer periodically leaps to left and top of screen with absolute pointing devices
Attached is a debdiff for quantal that should fix this bug. I have uploaded the patched package to my PPA (https://launchpad.net/~a7x/+archive/bug1041063) and it has finished building. To install: sudo apt-add-repository ppa:a7x/bug1041063 sudo apt-get update sudo apt-get upgrade ** Patch added: debdiff for quantal https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1041063/+attachment/3380689/+files/debdiff.patch ** Tags added: patch ** Also affects: fedora via https://bugzilla.redhat.com/show_bug.cgi?id=852841 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices Status in Compiz: Invalid Status in X.Org X server: Unknown Status in “xorg-server” package in Ubuntu: Confirmed Status in Fedora: Unknown Bug description: I'm running Ubuntu 12.10 inside a VirtualBox 4.2RC2 VM, and Ubuntu doesn't recognise the 3d drivers so it is falling back to llvmpipe. When I move the mouse around, it sometimes vanishes completely, and sometimes jumps over to the left or top left of the screen. If I'm moving a window with the mouse at the time, the window vanishes or jumps over to the left or top left as well. With 'force complete redraw on initial damage' turned on, it seems that glitch happens much more frequently. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.2.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:53:04 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: vboxguest, 4.2.0_RC2, 3.5.0-10-generic, x86_64: installed vboxguest, 4.2.0_RC2, 3.5.0-11-generic, x86_64: installed GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) Lsusb: Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=198f31f9-0b98-4ab4-998c-f779750d2fc9 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 == Regression details == Discovered in version: 2:1.13.0-0ubuntu5 Last known good version: 2:1.11.4-0ubuntu10.8 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 847464] Re: libwnck-3-0 gnome-panel SIGFPE in wnck_tasklist_size_allocate
According to a comment in the linked Debian bug report, this is caused by 03_tasklist_orientation.patch in gnome-panel. ** Also affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/847464 Title: libwnck-3-0 gnome-panel SIGFPE in wnck_tasklist_size_allocate Status in The Window Navigator Construction Kit: libwnck: Unknown Status in “gnome-panel” package in Ubuntu: New Status in “libwnck3” package in Ubuntu: Confirmed Status in “gnome-panel” package in Debian: Unknown Bug description: Set bottom-panel orientation to left. Gnome panel will no longer start. Set the orientation to bottom and gnome-panel starts ok again. $ gnome-panel (gnome-panel:2796): GLib-GObject-WARNING **: /build/buildd/glib2.0-2.29.90/./gobject/gsignal.c:2295: signal `size_request' is invalid for instance `0xc76a20' Floating point exception (core dumped) dmesg shows: gnome-panel[2343] trap divide error ip:7ffd3812c8dc sp:7fff765a3e60 error:0 in libwnck-3.so.0.1.0[7ffd3810d000+3c000] ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-panel 1:3.1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 ApportVersion: 1.22.1-0ubuntu2 Architecture: amd64 Date: Mon Sep 12 00:46:21 2011 SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libwnck/+bug/847464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
