[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: 'systemd --user' unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903194 Title: multiseat not set up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208473 Title: Xorg crashed with SIGABRT in mieqMoveToNewScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1208473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201122 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 902557] Re: Wireless not working in 12.04 for rtl8192ce (RTL8188CE)
No joy for me, Pauli. I tried simply copying the firmware included with the new driver into /lib/firmware/rtlwifi and verified the SHA1 sum matched the one you listed. I rebooted the machine (to avoid dealing with any rmmod/modprobe shenanigans) and continue to see ~10% packet loss due to repeated Reason 6 deauthentication. The firmware might be loaded from initramfs; if so you'll need to update your initramfs to embed the new firmware image. Try running 'sudo update-initramfs -u' after copying over the firmware to /lib/firmware/rtlwifi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/902557 Title: Wireless not working in 12.04 for rtl8192ce (RTL8188CE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/902557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201122 Title: 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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1209008 Title: X fails to detect certain video cards on non-seat0 seats To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1209008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/977547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903194 Title: multiseat not set up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075125 Title: Multiseat: only first seat session is marked as active in ConsoleKit To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1075125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/976124
Title:
lightdm multiseat: no login possible
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/976124
Title:
lightdm multiseat: no login possible
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085841 Title: Add basic systemd-logind multiseat support To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1085841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075125 Title: Multiseat: only first seat session is marked as active in ConsoleKit To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1075125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903194 Title: multiseat not set up correctly To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 812170] Re: Request support for unhandled (no greeter) sessions
** Tags added: multiseat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/812170 Title: Request support for unhandled (no greeter) sessions To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/812170/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1201124 Title: when second seat user log out, first seat switches to virtual terminal To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1201124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/977547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/976124 Title: lightdm multiseat: no login possible To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/976124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175044] Re: udevd[491]: IMPORT{builtin}: 'uaccess' unknown /lib/udev/rules.d/73-seat-late.rules:15
I believe 73-seat-late.rules is from the systemd-services package, so
adding the systemd source package to the 'affects' list.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175044
Title:
udevd[491]: IMPORT{builtin}: 'uaccess' unknown /lib/udev/rules.d/73
-seat-late.rules:15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1175044/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1175044] Re: udevd[491]: IMPORT{builtin}: 'uaccess' unknown /lib/udev/rules.d/73-seat-late.rules:15
Oops, didn't see that it was changed from systemd to udev. Sorry for
the noise.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175044
Title:
udevd[491]: IMPORT{builtin}: 'uaccess' unknown /lib/udev/rules.d/73
-seat-late.rules:15
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1175044/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178843] Re: kdevelop won't start
I just noticed that some of my gnome-settings-daemon crashes (~2 or 3 per day) have been BadWindow errors. I doubt gnome-settings-daemon uses any KDE libraries. Could this bug be unrelated to KDE? (If so, it looks like KDE apps tickle the bug more reliably than other apps.) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdevelop in Ubuntu. https://bugs.launchpad.net/bugs/1178843 Title: kdevelop won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1178843/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1198080] Re: Krusader crashes after pressing F5 or ESC
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198080 Title: Krusader crashes after pressing F5 or ESC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/1198080/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197879] Re: krusader crashes with BadWindow - invalid Window parameter
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197879 Title: krusader crashes with BadWindow - invalid Window parameter To manage notifications about this bug go to: https://bugs.launchpad.net/amarok/+bug/1197879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197679] Re: Krusader crashes when closing certain popups with embedded terminal emulator open
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197679 Title: Krusader crashes when closing certain popups with embedded terminal emulator open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/1197679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1197937] Re: Krusader crashes after latest KDE updates around 1 juli
*** This bug is a duplicate of bug 1197879 *** https://bugs.launchpad.net/bugs/1197879 ** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1197937 Title: Krusader crashes after latest KDE updates around 1 juli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krusader/+bug/1197937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195007] Re: kile crashes when click on file new + save
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195007 Title: kile crashes when click on file new + save To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1195007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1114198 Title: [power]: gnome-settings-daemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1114198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176862] Re: awesome crashes when using awful.util.spawn() on startup
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176862 Title: awesome crashes when using awful.util.spawn() on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awesome/+bug/1176862/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1107926] Re: bamfdaemon crashed with signal 5 in _XReply()
** Tags added: badwindow -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1107926 Title: bamfdaemon crashed with signal 5 in _XReply() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1107926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192842] Re: logind loses track of sessions when multiple sessions share a VT
What do you mean by losing track of sessions? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192842 Title: logind loses track of sessions when multiple sessions share a VT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1192842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1178843] Re: kdevelop won't start
About a month ago I started getting BadWindow errors with konsole and amarok, so I think it's a problem with some KDE library, not kdevelop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178843 Title: kdevelop won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1178843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1158267] Re: Regression: Broken (click-through) window decoration on some maximized windows
Attached is a debdiff for Raring that is based on https://bazaar.launchpad.net/~mar-kolya/compiz/fix- for-1158267/revision/3734 (from the bzr branch lp:~mar-kolya/compiz /fix-for-1158267). I have uploaded the patched package to my PPA (https://launchpad.net/~a7x/+archive/bug1158267). To install: sudo apt-add-repository ppa:a7x/bug1158267 sudo apt-get update sudo apt-get upgrade The patch is known to have issues; see https://code.launchpad.net/~mar- kolya/compiz/fix-for-1158267/+merge/167596. ** Patch added: debdiff for raring https://bugs.launchpad.net/compiz/+bug/1158267/+attachment/3727696/+files/raring.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1158267 Title: Regression: Broken (click-through) window decoration on some maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1158267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1195384] Re: problem with layouts in dash search
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1195384 Title: problem with layouts in dash search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1195384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1100871] Re: BASH program output not functioning
wrong package (dash is the Debian Almquist Shell, not the Bourne-Again Shell) ** Package changed: dash (Ubuntu) = bash (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100871 Title: BASH program output not functioning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1100871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176394] Re: dash working correctly on the bottom left corner
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176394 Title: dash working correctly on the bottom left corner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1176394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1194800] Re: cd flibbleflob/.. works when it shouldn't
See http://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html, specifically step 8.b.ii. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1194800 Title: cd flibbleflob/.. works when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1194800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191567] Re: UX - click on Dash preview image should trigger 'launch' action too
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191567 Title: UX - click on Dash preview image should trigger 'launch' action too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1191567/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089747] Re: Need setting to disable Display-Recent-Files for Dash's File-Lens
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089747 Title: Need setting to disable Display-Recent-Files for Dash's File-Lens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1089747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007501] Re: Applications fail to open
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007501 Title: Applications fail to open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1007501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020218] Re: keyboard not responding in dash home search
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020218 Title: keyboard not responding in dash home search To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1020218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 972635] Re: Firefox downloads listed under 'Recent Files'
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/972635 Title: Firefox downloads listed under 'Recent Files' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/972635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078532] Re: Dash does not play local music file previews
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078532 Title: Dash does not play local music file previews To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1078532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1002677] Re: Dash finds but doesn't load files with filenames with German special characters
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1002677 Title: Dash finds but doesn't load files with filenames with German special characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1002677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019488] Re: cannot drag and drop app to launcher
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019488 Title: cannot drag and drop app to launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1019488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 970357] Re: Dash scope bars have different sizes
wrong package (dash is the Debian Almquist Shell, not the Unity Dash) ** Package changed: dash (Ubuntu) = unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/970357 Title: Dash scope bars have different sizes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/970357/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 165042] Re: dash shell stdin handling not POSIX
Still a problem in raring. ** Changed in: dash (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/165042 Title: dash shell stdin handling not POSIX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/165042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 259671] Re: dash: echo builtin interprets backslash escape sequences
This is not a bug -- http://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html says that echo should process the backslashes. It would be a bug if echo did not process the backslashes. If you don't want backslashes processed, use printf: printf %s\\n '\\' ** Changed in: dash (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/259671 Title: dash: echo builtin interprets backslash escape sequences To manage notifications about this bug go to: https://bugs.launchpad.net/bash/+bug/259671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1196127] [NEW] dash -i -c may prompt for input from stdin/terminal
Public bug reported: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sh.html#tag_20_117_06 says: The standard input shall be used only if one of the following is true: * The -s option is specified. * The -c option is not specified and no operands are specified. * The script executes one or more commands that require input from standard input (such as a read command that does not redirect its input). However, if you run: dash -i -c 'if' then dash will drop to a prompt waiting for input from the terminal/stdin (after printing an error message for the legitimate syntax error. It should simply exit. Another way to test this: dash -i -c 'read foo' and then hit Ctrl-C. It will drop to a prompt when it should exit. ** Affects: dash (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1196127 Title: dash -i -c may prompt for input from stdin/terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1196127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/949126 Title: [Regression] X resources take no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs23/+bug/949126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595648] Re: Remote unlocking not possible if plymouth is active (Bug or Feature?)
Attached is a script I wrote to make it easier to unlock systems from remote. It works on precise and quantal even with the original plymouth. I haven't tried the script on raring yet. ** Attachment added: script to automate unlocking of a system from remote https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/595648/+attachment/3662930/+files/unlock-cryptroot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/595648 Title: Remote unlocking not possible if plymouth is active (Bug or Feature?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/595648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
It has not yet been fixed in Raring. Precise, Quantal, and Raring are all at 2.1.10, so the attached upstream patch should apply cleanly to Raring. I will edit the bug description according to the SRU procedure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097366 Title: Pidgin client digest-uri checks fail with multiple virtual hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
** Description changed:
+ [Impact]
+
Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
There is another bug where Pidgin users won't be able to log in if there
are multiple virtual hosts and the hostnames in the SRV records for the
two XMPP hosts are different.
- For example, suppose ejabberd.cnf contains:
-
- {hosts, [foo.example, bar.example]}.
- {fqdn, xmpp.foo.example}.
-
- and DNS lookups return the following:
-
- dig -t SRV _xmpp-client._tcp.foo.example. - xmpp.foo.example:5222
- dig -t SRV _xmpp-client._tcp.bar.example. - xmpp.bar.example:5222
- dig -t A xmpp.foo.example. - 192.0.2.123
- dig -t A xmpp.bar.example. - 192.0.2.123
-
- then Pidgin clients with *@bar.example Jabber IDs are NOT able to log
- in. The digest-uri sent by these clients – xmpp/xmpp.bar.example –
- doesn't pass ejabberd's digest-uri checking logic. Pidgin clients with
- *@foo.example Jabber IDs do work, however.
-
This particular bug has already been fixed upstream:
https://github.com/processone/ejabberd/commit/2bf8125abfeec9e1176ea7ab9793b8947f9c09b6
+ as part of this upstream bug report:
+ https://support.process-one.net/browse/EJAB-1578
+
+ The upstream commit is not yet available in an official upstream
+ release. Presumably the patch will be included in ejabberd 2.1.12 when
+ it is released.
+
+ [Test Case]
+
+ 1. Put these lines in /etc/ejabberd/ejabberd.cfg:
+
+ {hosts, [example.com, example.net]}.
+ {fqdn, example.com}.
+
+ 2. Configure DNS with the following example records:
+
+ _xmpp-server._tcp.example.com. 86400 IN SRV 0 0 5269 xmpp.example.com.
+ _xmpp-client._tcp.example.com. 86400 IN SRV 0 0 5222 xmpp.example.com.
+ xmpp.example.com. 86400 IN A 127.0.0.1
+ _xmpp-server._tcp.example.net. 86400 IN SRV 0 0 5269 xmpp.example.net.
+ _xmpp-client._tcp.example.net. 86400 IN SRV 0 0 5222 xmpp.example.net.
+ xmpp.example.net. 86400 IN CNAME xmpp.example.com.
+
+The above example records assume the ejabberd server and Pidgin
+ client are both running on the same system (notice the 127.0.0.1).
+ Change as appropriate.
+
+ 3. Create two ejabberd users:
+
+- exam...@example.com
+- exam...@example.net
+
+ 4. Configure Pidgin with both XMPP accounts
+
+ With the patch, both accounts can successfully log in. Without the
+ patch, only the exam...@example.com account can log in because the
+ exam...@example.net account will fail ejabberd's digest-uri checking
+ logic.
+
+ [Regression Potential]
+
+ This change extends the syntax of the ejabberd config file. Existing
+ configuration files should remain compatible, but if there was a
+ regression, it might manifest itself as an inability to correctly parse
+ previously-valid configuration files.
+
+ The change also affects the digest-uri checking logic. A regression may
+ result in users being unable to log in or overly permissive checks.
+
+ The patch has been in the upstream repository since 2012-06-27, and I
+ have been running it locally for almost as long without any problems.
+ No subsequent changes to the affected region of code have been made
+ upstream since this patch.
** Description changed:
[Impact]
Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
There is another bug where Pidgin users won't be able to log in if there
are multiple virtual hosts and the hostnames in the SRV records for the
two XMPP hosts are different.
This particular bug has already been fixed upstream:
https://github.com/processone/ejabberd/commit/2bf8125abfeec9e1176ea7ab9793b8947f9c09b6
as part of this upstream bug report:
https://support.process-one.net/browse/EJAB-1578
The upstream commit is not yet available in an official upstream
release. Presumably the patch will be included in ejabberd 2.1.12 when
it is released.
+ This bug is known to affect precise, quantal, and raring.
+
[Test Case]
1. Put these lines in /etc/ejabberd/ejabberd.cfg:
- {hosts, [example.com, example.net]}.
- {fqdn, example.com}.
+ {hosts, [example.com, example.net]}.
+ {fqdn, example.com}.
2. Configure DNS with the following example records:
- _xmpp-server._tcp.example.com. 86400 IN SRV 0 0 5269 xmpp.example.com.
- _xmpp-client._tcp.example.com. 86400 IN SRV 0 0 5222 xmpp.example.com.
- xmpp.example.com. 86400 IN A 127.0.0.1
- _xmpp-server._tcp.example.net. 86400 IN SRV 0 0 5269 xmpp.example.net.
- _xmpp-client._tcp.example.net. 86400 IN SRV 0 0 5222 xmpp.example.net.
- xmpp.example.net. 86400 IN CNAME xmpp.example.com.
+ _xmpp-server._tcp.example.com. 86400 IN SRV 0 0 5269 xmpp.example.com.
+ _xmpp-client._tcp.example.com. 86400 IN SRV 0 0 5222 xmpp.example.com.
+ xmpp.example.com. 86400 IN A 127.0.0.1
+ _xmpp-server._tcp.example.net. 86400 IN SRV 0 0 5269 xmpp.example.net.
+ _xmpp-client._tcp.example.net. 86400 IN SRV 0 0 5222 xmpp.example.net.
+ xmpp.example.net. 86400 IN
[Bug 1048142] Re: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build [Error! Application of patch fix-build-issue-on-i386-where-TS_USEDFPU-is-no-longe.patch failed.]
I have removed the version I made from my PPA. Please downgrade to the officially supported version now that a fix has been released. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1048142 Title: fglrx-updates 2:8.982-0ubuntu0.1: fglrx-updates kernel module failed to build [Error! Application of patch fix-build-issue-on-i386-where- TS_USEDFPU-is-no-longe.patch failed.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1048142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/430981 Title: keybindings not remembered on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/430981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1029723] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()
** Package changed: ubuntu = mythtv (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1029723 Title: mythlogserver crashed with SIGSEGV in QObject::disconnect() To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1029723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] [NEW] Pidgin client digest-uri checks fail with multiple virtual hosts
Public bug reported:
Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
There is another bug where Pidgin users won't be able to log in if there
are multiple virtual hosts and the hostnames in the SRV records for the
two XMPP hosts are different.
For example, suppose ejabberd.cnf contains:
{hosts, [foo.example, bar.example]}.
{fqdn, xmpp.foo.example}.
and DNS lookups return the following:
dig -t SRV _xmpp-client._tcp.foo.example. - xmpp.foo.example:5222
dig -t SRV _xmpp-client._tcp.bar.example. - xmpp.bar.example:5222
dig -t A xmpp.foo.example. - 192.0.2.123
dig -t A xmpp.bar.example. - 192.0.2.123
then Pidgin clients with *@bar.example Jabber IDs are NOT able to log
in. The digest-uri sent by these clients – xmpp/xmpp.bar.example –
doesn't pass ejabberd's digest-uri checking logic. Pidgin clients with
*@foo.example Jabber IDs do work, however.
This particular bug has already been fixed upstream:
https://github.com/processone/ejabberd/commit/2bf8125abfeec9e1176ea7ab9793b8947f9c09b6
** Affects: ejabberd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097366
Title:
Pidgin client digest-uri checks fail with multiple virtual hosts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
Upstream bug report (launchpad doesn't recognize it, so I can't use Also affects project): https://support.process-one.net/browse/EJAB-1578 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097366 Title: Pidgin client digest-uri checks fail with multiple virtual hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
Attached is a debdiff that includes the upstream patch. I've been running with the upstream patch for months now without any problems. ** Patch added: debdiff for precise https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+attachment/3477236/+files/debdiff-precise.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097366 Title: Pidgin client digest-uri checks fail with multiple virtual hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097366] Re: Pidgin client digest-uri checks fail with multiple virtual hosts
** Patch added: upstream patch https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+attachment/3477243/+files/ejab-1578.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097366 Title: Pidgin client digest-uri checks fail with multiple virtual hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/570151 Title: mouse stuck jumping between screens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/570151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088081] Re: udev rules make it impossible to deactivate lvm volume group with vgchange -an
Tagging with regression-release because this works in 12.04. Thanks to @Dr_Jekyll for testing! ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088081 Title: udev rules make it impossible to deactivate lvm volume group with vgchange -an To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1088081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091976 Title: fix uploaded to precise-proposed for a bug that doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1091976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993101] Re: atftpd does not install correctly
** Changed in: rlinetd (Ubuntu) Status: Confirmed = Invalid ** Summary changed: - atftpd does not install correctly + atftpd fails to install -- update-inetd doesn't like udp4 ** Summary changed: - atftpd fails to install -- update-inetd doesn't like udp4 + atftpd postinst should pass udp to update-inetd (not udp4) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993101 Title: atftpd postinst should pass udp to update-inetd (not udp4) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/atftp/+bug/993101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1041063 Title: mouse pointer periodically leaps to left and top of screen with absolute pointing devices To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1041063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076955 Title: Display options stuck on only one screen icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1076955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1043769 Title: Monitor image not clickable in display settings after the first time To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1043769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088081] [NEW] udev rules make it impossible to deactivate lvm volume group with vgchange -an
Public bug reported: Running 'vgchange -a n volume_group_name' generates udev events that are matched by /lib/udev/rules.d/85-lvm2.rules, causing it to run 'vgchange -a y'. This defeats the initial 'vgchange -a n' and makes it impossible to: * run 'cryptsetup luksClose' on the underlying encrypted device * safely remove a removable drive containing an LVM physical volume * safely use dd to copy the LVM partition to another device (LVM might be writing data) I turned up logging and it looks like the following happened to the instance I was watching: 1. 'vgchange -a n vgname' caused LVM to close /dev/dm-5 (the LUKS dm device holding the LVM physical volume) 2. udev logged this: device /dev/dm-5 closed, synthesising 'change' 3. a new 'change' 'block' udev event was enqueued for the LUKS dm device 4. udev started processing the new 'change' event 5. the event matched /lib/udev/rules.d/60-persistent-storage-dm.rules:16 so blkid was run and set ID_FS_TYPE=LVM2_member 6. all of the conditions for /lib/udev/rules.d/85-lvm2.rules matched, so 'vgchange -a y' was run Brainstorming ideas for fixing this: * I'm not sure why udev synthesizes a change event when a dm device is closed, but disabling that bit of code should fix this bug (and probably cause many worse bugs). * Maybe the lvm udev rule should condition on ACTION==add instead of ACTION=add|change (just tried this and unfortunately it doesn't work -- unlocking a LUKS device causes two back-to-back udev events: one 'add' event that only appears to match /lib/udev/rules.d/50-udev-default.rules:67 and a second 'change' event that matches much more). Other info: $ lsb_release -rdc Description:Ubuntu 12.10 Release:12.10 Codename: quantal lvm2 version: 2.02.95-4ubuntu1 udev version: 175-0ubuntu13 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Package changed: udev (Ubuntu) = lvm2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088081 Title: udev rules make it impossible to deactivate lvm volume group with vgchange -an To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1088081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1088081] Re: udev rules make it impossible to deactivate lvm volume group with vgchange -an
** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1088081 Title: udev rules make it impossible to deactivate lvm volume group with vgchange -an To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1088081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
