[Desktop-packages] [Bug 1670494] Re: 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
This is still broken in Artful, but is fixed in Bionic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1670494
Title:
'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
Status in wpa package in Ubuntu:
Confirmed
Bug description:
init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach. init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.
When the nl80211 driver is used with some Intel cards, wpa_supplicant
automatically defines a second p2p_dev_${WPA_IFACE} interface. If
multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
will wait for multiple wpa_cli instances to attach. Since
init_wpa_supplicant() only attaches a single wpa_cli process, this
causes wpa_supplicant to hang, which ultimately leads to a timeout and
causes interface configuration to fail.
This has been fixed upstream:
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402
However, the updated wpa_supplicant has not made it to Ubuntu (not
even Zesty), and the "-m ''" workaround mentioned in the mailing list
thread associated with the upstream fix does not work with the version
of wpa_supplicant that comes with Ubuntu.
Could the P2P patches that were merged into Debian be merged into
Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1670494/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login
The problem is that Xfwm's built-in compositor and virgl don't play nice together. Work-around: Boot the VM with virgl=off (on the video device) or gl=off (on the display), run xfwm4-tweaks-settings in the VM, select the "Compositor" tab, and uncheck "Enable display compositing". Then shut down the VM and re-enable virgl. picom works with Xfwm and doesn't seem to have the same issues, so if you want a compositor, install/use picom instead of using Xfwm's built- in compositor: https://wiki.archlinux.org/index.php/Picom -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1868780 Title: [virtio] Xubuntu 20.04 - Blank screen after login Status in lightdm package in Ubuntu: New Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1868780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545302] [NEW] wpa-roam broken by fix for ifupdown #1337873
Public bug reported: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. ** Affects: wpa (Ubuntu) Importance: Undecided Status: Confirmed ** Patch added: "patch" https://bugs.launchpad.net/bugs/1545302/+attachment/4570963/+files/patch ** Description changed: - The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup: + The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in wpa package in Ubuntu: Confirmed Bug description: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545363] [NEW] wpa-roam does not support logical "master" interfaces
Public bug reported: There are situations where I have multiple APs (living on separate networks) in range simultaneously and I need to be able to manually choose between them (to manually move between those separate networks). To handle this, I have multiple wpa_supplicant config files for each of the APs, and I use logical interfaces in /etc/network/interfaces to select the appropriate config file. For example: iface public inet manual wpa-conf /etc/wpa_supplicant/public.conf iface private inet manual wpa-conf /etc/wpa_supplicant/private.conf To select the appropriate AP, I simply run `ifup wlan0=public` or `ifup wlan0=private`. This part works fine. However, I would like to change the "wpa-conf" lines in the above example to use "wpa-roam" instead, so I can also handle roaming in conjunction with multiple wpa_supplicant config files. Unfortunately this doesn't work. When the "master" interface is already using a logical interface in /etc/network/interfaces, wpa-roam fails to load the logical interface specified by id_str. The problem is that the ifup() function in functions.sh runs `grep -q "^$WPA_IFACE=$WPA_IFACE" "$IFSTATE_FILE"` to determine if the interface is already up, then runs /sbin/ifup either with or without '--force' depending on whether the interface is "up". If the "master" interface is defined in /etc/network/interfaces as a logical interface rather than a physical interface, then grep will not match, '--force' will not be used, and /sbin/ifup will fail because the interface is already configured and '--force' was not used. The attached patch fixes this issue by running `ifquery` to determine whether the physical interface is currently up and configured as a wpasupplicant "master" interface, and will run /sbin/ifup with '--force' even if the "master" interface is a logical interface in /etc/network/interfaces. If the physical interface is already up but is not configured as a "master" interface, then it is likely we received two "CONNECT" events without a "DISCONNECT" between them, so `ifdown` is run on the old logical interface before `ifup` is run on the new one. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Patch added: "patch" https://bugs.launchpad.net/bugs/1545363/+attachment/4571280/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545363 Title: wpa-roam does not support logical "master" interfaces Status in wpa package in Ubuntu: New Bug description: There are situations where I have multiple APs (living on separate networks) in range simultaneously and I need to be able to manually choose between them (to manually move between those separate networks). To handle this, I have multiple wpa_supplicant config files for each of the APs, and I use logical interfaces in /etc/network/interfaces to select the appropriate config file. For example: iface public inet manual wpa-conf /etc/wpa_supplicant/public.conf iface private inet manual wpa-conf /etc/wpa_supplicant/private.conf To select the appropriate AP, I simply run `ifup wlan0=public` or `ifup wlan0=private`. This part works fine. However, I would like to change the "wpa-conf" lines in the above example to use "wpa-roam" instead, so I can also handle roaming in conjunction with multiple wpa_supplicant config files. Unfortunately this doesn't work. When the "master" interface is already using a logical interface in /etc/network/interfaces, wpa-roam fails to load the logical interface specified by id_str. The problem is that the ifup() function in functions.sh runs `grep -q "^$WPA_IFACE=$WPA_IFACE" "$IFSTATE_FILE"` to determine if the interface is already up, then runs /sbin/ifup either with or without ' --force' depending on whether the interface is "up". If the "master" interface is defined in /etc/network/interfaces as a logical interface rather than a physical interface, then grep will not match, '--force' will not be used, and /sbin/ifup will fail because the interface is already configured and '--force' was not used. The attached patch fixes this issue by running `ifquery` to determine whether the physical interface is currently up and configured as a wpasupplicant "master" interface, and will run /sbin/ifup with '-- force' even if the "master" interface is a logical interface in /etc/network/interfaces. If the physical interface is already up but is not configured as a "master" interface, then it is likely we received two "CONNECT" events without a "DISCONNECT" between them, so `ifdown` is run on the old logical interface before `ifup` is run on the new one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists
[Desktop-packages] [Bug 1545302] Re: wpa-roam broken by fix for ifupdown #1337873
Updating my patch ... The environment variable also needs to be unset before calling ifdown. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4572496/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in wpa package in Ubuntu: Confirmed Bug description: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545302] Re: wpa-roam broken by fix for ifupdown #1337873
My configuration:
/etc/network/interfaces
auto wlan0
iface wlan0 inet manual
wpa-driver wext
wpa-roam /etc/wpa_supplicant/wpa.conf
wpa-roam-default-iface dhcp
iface dhcp inet dhcp
dns-nameservers 8.8.8.8 8.8.4.4
iface dhcp_dns
/etc/wpa_supplicant/wpa.conf
network={
ssid="x"
priority=10
key_mgmt=WPA-PSK
psk="..."
id_str="dhcp_dns"
}
network={
ssid="y"
priority=9
key_mgmt=WPA-PSK
psk="..."
}
After connecting to either the x or y networks, wpa_supplicant calls
`wpa_action connect` which calls `ifup wlan0=dhcp_dns` or `ifup
wlan0=dhcp`, which fails with "ifup: recursion detected for parent
interface wlan0 in post-up phase". Therefore, dhclient is never run, so
wlan0 never gets an IP address.
Note that the wpa_supplicant daemon is started by the /etc/network/if-
up.d/wpasupplicant script, and it inherits the environment from `ifup
wlan0` (including the environment variable used to detect recursion).
`wpa_action connect` then inherits the environment from wpa_supplicant,
and `ifup wlan0=dhcp` inherits it from wpa_action, hence the error from
ifup.
I understand that this variable is meant to avoid certain race
conditions, but I don't believe the type of race condition reported in
bug #1337873 is applicable to this situation. Because wpa_supplicant is
started by ifup itself (and not a boot script), there is no way for the
`ifup wlan0` and `ifup wlan0=dhcp` to be called out of order, so there
is no chance of a race condition. However, maybe I'm missing something
here. Could you explain how the wpa-roam implementation could play
along with ifupdown given that it is started by ifup itself and needs to
call ifup to reconfigure the interface?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1545302
Title:
wpa-roam broken by fix for ifupdown #1337873
Status in wpa package in Ubuntu:
Confirmed
Bug description:
The following versions of ifupdown introduced a recursion check using
"IFUPDOWN_" environment variables along with a new locking mechanism
for ifup (see #1337873):
0.7.47.2ubuntu4.2 (in Trusty)
0.7.54ubuntu1.1 (in Wily)
0.7.54ubuntu2 (in Xenial)
This recursion check breaks the wpa-roam feature of wpasupplicant,
preventing it from loading the logical interface specified by id_str
after associating with an AP. Specifically, after upgrading to one of
the above ifupdown versions, the '/sbin/ifup -v --force
"$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in
functions.sh fails with an "ifup: recursion detected for parent
interface wlan0 in post-up phase" error.
To fix the issue, functions.sh needs to run `unset
"IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from
detecting the recursion. The attached patch implements this change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545363] Re: wpa-roam does not support logical "master" interfaces
** Description changed: There are situations where I have multiple APs (living on separate networks) in range simultaneously and I need to be able to manually choose between them (to manually move between those separate networks). To handle this, I have multiple wpa_supplicant config files for each of the APs, and I use logical interfaces in /etc/network/interfaces to select the appropriate config file. For example: iface public inet manual - wpa-conf /etc/wpa_supplicant/public.conf + wpa-conf /etc/wpa_supplicant/public.conf iface private inet manual - wpa-conf /etc/wpa_supplicant/private.conf + wpa-conf /etc/wpa_supplicant/private.conf To select the appropriate AP, I simply run `ifup wlan0=public` or `ifup wlan0=private`. This part works fine. However, I would like to change the "wpa-conf" lines in the above example to use "wpa-roam" instead, so I can also handle roaming in conjunction with multiple wpa_supplicant config files. Unfortunately this doesn't work. When the "master" interface is already using a logical interface in /etc/network/interfaces, wpa-roam fails to load the logical interface specified by id_str. The problem is that the ifup() function in functions.sh runs `grep -q "^$WPA_IFACE=$WPA_IFACE" "$IFSTATE_FILE"` to determine if the interface is already up, then runs /sbin/ifup either with or without '--force' depending on whether the interface is "up". If the "master" interface is defined in /etc/network/interfaces as a logical interface rather than a physical interface, then grep will not match, '--force' will not be used, and /sbin/ifup will fail because the interface is already configured and '--force' was not used. The attached patch fixes this issue by running `ifquery` to determine - whether the physical interface is currently up and configured as a - wpasupplicant "master" interface, and will run /sbin/ifup with '--force' - even if the "master" interface is a logical interface in - /etc/network/interfaces. If the physical interface is already up but is - not configured as a "master" interface, then it is likely we received - two "CONNECT" events without a "DISCONNECT" between them, so `ifdown` is - run on the old logical interface before `ifup` is run on the new one. + whether the physical interface is currently configured as a + wpasupplicant "master" interface and needs the '--force' argument to + /sbin/ifup. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545363/+attachment/4572525/+files/patch ** Patch removed: "patch" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545363/+attachment/4571280/+files/patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545363 Title: wpa-roam does not support logical "master" interfaces Status in wpa package in Ubuntu: New Bug description: There are situations where I have multiple APs (living on separate networks) in range simultaneously and I need to be able to manually choose between them (to manually move between those separate networks). To handle this, I have multiple wpa_supplicant config files for each of the APs, and I use logical interfaces in /etc/network/interfaces to select the appropriate config file. For example: iface public inet manual wpa-conf /etc/wpa_supplicant/public.conf iface private inet manual wpa-conf /etc/wpa_supplicant/private.conf To select the appropriate AP, I simply run `ifup wlan0=public` or `ifup wlan0=private`. This part works fine. However, I would like to change the "wpa-conf" lines in the above example to use "wpa-roam" instead, so I can also handle roaming in conjunction with multiple wpa_supplicant config files. Unfortunately this doesn't work. When the "master" interface is already using a logical interface in /etc/network/interfaces, wpa-roam fails to load the logical interface specified by id_str. The problem is that the ifup() function in functions.sh runs `grep -q "^$WPA_IFACE=$WPA_IFACE" "$IFSTATE_FILE"` to determine if the interface is already up, then runs /sbin/ifup either with or without ' --force' depending on whether the interface is "up". If the "master" interface is defined in /etc/network/interfaces as a logical interface rather than a physical interface, then grep will not match, '--force' will not be used, and /sbin/ifup will fail because the interface is already configured and '--force' was not used. The attached patch fixes this issue by running `ifquery` to determine whether the physical interface is currently configured as a wpasupplicant "master" interface and needs the '--force' argument to /sbin/ifup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1545302] Re: wpa-roam broken by fix for ifupdown #1337873
Oops ... missed "inet dhcp" on the "iface dhcp_dns" line above. That line should be: iface dhcp_dns inet dhcp -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in wpa package in Ubuntu: Confirmed Bug description: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545302] Re: wpa-roam broken by fix for ifupdown #1337873
See bug #1545363 - my patch for that bug happens to remove the use of the ifstate file. However, fixing that does not solve the "ifup: recursion detected ..." issue. The environment variable still needs to be removed to fix the recursion issue. After thinking about it some more, I think it may make more sense to unset the variable in /etc/wpa_supplicant/ifupdown.sh rather than /etc/wpa_supplicant/functions.sh (so the variable is removed from the wpa_supplicant daemon's environment, rather than being removed each time wpa_action calls ifup or ifdown). This new attached patch file does this. Let me know when you have something for me to test. Thanks! ** Attachment added: "patch2" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+attachment/4572849/+files/patch2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in wpa package in Ubuntu: Confirmed Bug description: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545302] Re: wpa-roam broken by fix for ifupdown #1337873
@Dariusz: Works for me on Wily. Nice find, this is a much better fix than my proposed patch. Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545302 Title: wpa-roam broken by fix for ifupdown #1337873 Status in wpa package in Ubuntu: Confirmed Bug description: [Impact] * In some configurations recurrent ifup/down calls are broken due to a false-positive recursion detection. * In certain situations it leaves interfaces unconfigured (in this case: WLAN interface connected to WiFi network, but dhcp fails). [Test Case] * Setup wpa-roam configuration based on what is in comment #6 * Wait until wpa_supplicant connects to a wifi network * Run ifconfig to check if the WLAN interface received dhcp info * Expected result: WLAN is fully configured according to dhcp settings * Actual result: WLAN is connected to WiFi but not configured [Regression Potential] * Fixed upstream, fix present in Xenial. * Debdiffs contain a backport of an upstream fix. [Other Info] * Original bug description: The following versions of ifupdown introduced a recursion check using "IFUPDOWN_" environment variables along with a new locking mechanism for ifup (see #1337873): 0.7.47.2ubuntu4.2 (in Trusty) 0.7.54ubuntu1.1 (in Wily) 0.7.54ubuntu2 (in Xenial) This recursion check breaks the wpa-roam feature of wpasupplicant, preventing it from loading the logical interface specified by id_str after associating with an AP. Specifically, after upgrading to one of the above ifupdown versions, the '/sbin/ifup -v --force "$WPA_IFACE=$WPA_LOGICAL_IFACE"' command run by wpa_action in functions.sh fails with an "ifup: recursion detected for parent interface wlan0 in post-up phase" error. To fix the issue, functions.sh needs to run `unset "IFDOWN_$WPA_IFACE"` before calling /sbin/ifup to prevent ifup from detecting the recursion. The attached patch implements this change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545363] Re: wpa-roam does not support logical "master" interfaces
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545766 ** Bug watch added: Debian Bug tracker #545766 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545766 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1545363 Title: wpa-roam does not support logical "master" interfaces Status in wpa package in Ubuntu: Incomplete Bug description: There are situations where I have multiple APs (living on separate networks) in range simultaneously and I need to be able to manually choose between them (to manually move between those separate networks). To handle this, I have multiple wpa_supplicant config files for each of the APs, and I use logical interfaces in /etc/network/interfaces to select the appropriate config file. For example: iface public inet manual wpa-conf /etc/wpa_supplicant/public.conf iface private inet manual wpa-conf /etc/wpa_supplicant/private.conf To select the appropriate AP, I simply run `ifup wlan0=public` or `ifup wlan0=private`. This part works fine. However, I would like to change the "wpa-conf" lines in the above example to use "wpa-roam" instead, so I can also handle roaming in conjunction with multiple wpa_supplicant config files. Unfortunately this doesn't work. When the "master" interface is already using a logical interface in /etc/network/interfaces, wpa-roam fails to load the logical interface specified by id_str. The problem is that the ifup() function in functions.sh runs `grep -q "^$WPA_IFACE=$WPA_IFACE" "$IFSTATE_FILE"` to determine if the interface is already up, then runs /sbin/ifup either with or without ' --force' depending on whether the interface is "up". If the "master" interface is defined in /etc/network/interfaces as a logical interface rather than a physical interface, then grep will not match, '--force' will not be used, and /sbin/ifup will fail because the interface is already configured and '--force' was not used. The attached patch fixes this issue by running `ifquery` to determine whether the physical interface is currently configured as a wpasupplicant "master" interface and needs the '--force' argument to /sbin/ifup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1545363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1580123] Re: xrandr --scale (again) confines mouse to native solution
As noted in https://bugs.launchpad.net/xorg- server/+bug/883319/comments/62 , the fix for #883319 requires --panning to be specified with --scaling in order to disable the mouse constraints when scaling. Ideally, xorg should be modified such that the mouse constraints are calculated based on the --scaling and --panning settings, rather than being disabled when --panning is enabled. Short of that, it would be nice if xorg was modified to disable the mouse constraints when --scaling is enabled (in addition to when --panning is enabled). If neither of those can be accomplished, it would probably be sufficient to simply document (in the man page?) that --panning may be needed to disable the mouse constraints when using --scaling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1580123 Title: xrandr --scale (again) confines mouse to native solution Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Bug description: This might be a regression where the original issue is: https://bugs.launchpad.net/xorg-server/+bug/883319 It can be easily reproduced by doing something like: xrandr --output DP1 --scale 1.25x1.25 The mouse will be still constrained to the native solution (aka you can't move the mouse outside a box of whatever DP1 had as resolution before. $ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ xrandr --version xrandr program version 1.5.0 Server reports RandR version 1.5 $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1580123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1670494] [NEW] 'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
Public bug reported:
init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach. init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.
When the nl80211 driver is used with some Intel cards, wpa_supplicant
automatically defines a second p2p_dev_${WPA_IFACE} interface. If
multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
will wait for multiple wpa_cli instances to attach. Since
init_wpa_supplicant() only attaches a single wpa_cli process, this
causes wpa_supplicant to hang, which ultimately leads to a timeout and
causes interface configuration to fail.
This has been fixed upstream:
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402
However, the updated wpa_supplicant has not made it to Ubuntu (not even
Zesty), and the "-m ''" workaround mentioned in the mailing list thread
associated with the upstream fix does not work with the version of
wpa_supplicant that comes with Ubuntu.
Could the P2P patches that were merged into Debian be merged into
Ubuntu?
** Affects: wpa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1670494
Title:
'wpa_supplicant -D nl80211 -W' hangs with some Intel cards
Status in wpa package in Ubuntu:
New
Bug description:
init_wpa_supplicant() in /etc/wpa_supplicant/functions.sh runs
wpa_supplicant with the -W option, which causes it to wait for wpa_cli
to attach. init_wpa_supplicant() then attaches wpa_cli to
wpa_supplicant.
When the nl80211 driver is used with some Intel cards, wpa_supplicant
automatically defines a second p2p_dev_${WPA_IFACE} interface. If
multiple interfaces are defined in wpa_supplicant, then wpa_supplicant
will wait for multiple wpa_cli instances to attach. Since
init_wpa_supplicant() only attaches a single wpa_cli process, this
causes wpa_supplicant to hang, which ultimately leads to a timeout and
causes interface configuration to fail.
This has been fixed upstream:
http://lists.infradead.org/pipermail/hostap/2015-December/034410.html
And also in Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402
However, the updated wpa_supplicant has not made it to Ubuntu (not
even Zesty), and the "-m ''" workaround mentioned in the mailing list
thread associated with the upstream fix does not work with the version
of wpa_supplicant that comes with Ubuntu.
Could the P2P patches that were merged into Debian be merged into
Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1670494/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
A number of relevant bug fixes have been committed to the kernel since this
driver was backported. These fixes should probably be backported as well:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=864db9295b06837d11a260e5dacf99a3fdf6bce2
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7229c58c096ca08576cbcbf6669bfbdcae0b5d22
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23fce365c6a26e40d459ca97289dd18543fb6845
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=47e3a5edc6538d66e470aaed3b7c57255cb37ca1
https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?h=for-linus&id=e7348396c6d51b57c95c6646c390cd078e038e19
https://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git/commit/?h=for-linus&id=47e6fb4212d09f325c0847d05985dd3d71553095
I put the following in my xorg.conf to permanently fix the sensitivity issues
and disable edge scrolling:
Section "InputClass"
Identifier"PointStick"
MatchIsPointer"true"
MatchProduct "DualPoint Stick"
MatchDevicePath "/dev/input/event*"
# To display current settings:
# xinput list-props 'AlpsPS/2 ALPS DualPoint Stick'
# xinput get-feedbacks 'AlpsPS/2 ALPS DualPoint Stick'
# Scroll wheel emulation is configured by default in
# /usr/share/X11/xorg.conf.d/11-evdev-trackpoint.conf
# Default scroll is way too sensitive
Option"EmulateWheelInertia" "80"# Default 10
# Middle Button Emulation isn't needed since there is a physical button
Option"Emulate3Buttons" "false" # Default true
# Use the recommended "polynomial" acceleration profile
Option"AccelerationProfile" "2" # Default 0 ("classic")
# Default settings are way too sensitive
Option"ConstantDeceleration" "9" # Default 1.0
#Option "AdaptiveDeceleration" "1.0" # Default 1.0
# The Threshold/Numerator/Denominator set here are usually overridden by the
Desktop Manager,
# so you may also need to adjust these in the Desktop Manager's control
panel, or add
# `xinput set-ptr-feedback 'AlpsPS/2 ALPS DualPoint Stick' 0 7 2` to a
startup script run by your
# Desktop manager.
Option"AccelerationThreshold" "0" # Default 4 for use
with "classic" profile
Option"AccelerationNumerator" "7" # Default 2
Option"AccelerationDenominator" "2" # Default 1
#Option "VelocityScaling" "10.0" # Default 10.0
EndSection
Section "InputClass"
Identifier"TouchPad"
MatchIsTouchpad "true"
MatchDevicePath "/dev/input/event*"
# To display current settings:
# xinput list-props 'AlpsPS/2 ALPS DualPoint TouchPad'
# xinput get-feedbacks 'AlpsPS/2 ALPS DualPoint TouchPad'
# synclient
# Use multi-touch button emulation
Option"TapButton2""2" # Default 3 (right
click)
Option"TapButton3""3" # Default 0
# Button emulation isn't needed since there are physical buttons
# and multi-touch button emulation is easier to use than edge button emulation
Option"RTCornerButton""0" # Default 2 (middle
click)
Option"RBCornerButton""0" # Default 3 (right
click)
Option"LTCornerButton""0" # Default 0
Option"LBCornerButton""0" # Default 0
# Use multi-touch scroll emulation
Option"VertTwoFingerScroll" "true" # Default true
Option"HorizTwoFingerScroll" "true" # Default false
# Reverse multi-touch scroll direction
# (Emulate touch screen scroll)
#Option "VertScrollDelta" "-64" # Default 64
#Option "HorizScrollDelta" "-64" # Default 64
# Edge scroll emulation isn't needed since multi-touch scroll emulation is
supported
# (Multi-touch scroll emulation is easier to use than edge scroll emulation)
Option"VertEdgeScroll""false" # Default true
Option"HorizEdgeScroll" "false" # Default false
# Disable acceleration in the synaptics driver (use Xorg acceleration instead)
Option"MinSpeed" "1" # Default 1
Option"MaxSpeed" "1" # Default 1.75
# Use the recommended "polynomial" acceleration profile
Option"AccelerationProfile" "2" # Default 1
("device-dependent")
# Default settings are a bit too sensitive
Option"ConstantDeceleration" "5" # Default 2.5
#Option "AdaptiveDeceleration" "1.0" # Default 1.0
# The Threshold/Numerator/Denominator set here are usually overridden by the
Desktop Manager,
# so you may also need to adjust these in the Desktop Manager's control
panel, or add
# `xinput set-ptr-fee
[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
BTW, some Dell Precision 7510 systems (possibly only Xeon systems?) have a hardware issue where the trackstick or the touchpad or both will periodically get "stuck" (stop responding briefly) when on A/C power, when switchable graphics is enabled, when there is significant 2D or 3D video activity being rendered on the Intel video card, and when the Alps device is being run by an Alps driver (either this Linux driver or the standard Windows driver) instead of being run in PS/2 compatibility mode. However, Dell is not taking my complaints about this seriously, in part because they "have not received any other complaints about this issue". If anyone else is encountering this issue, please contact me directly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
No. If I monitor interrupts, the Alps device actually stops sending interrupts when the touchpad or trackstick stutters. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247484] [NEW] systemd-logind sessions are not set up properly if `startx` is used
Public bug reported:
In Raring and earlier, ConsoleKit was used for session management, and
/etc/X11/Xsession.d/90consolekit took care of preparing ConsoleKit
sessions via `ck-launch-session` when X was started via `startx` instead
of a graphical login manager.
In Saucy, ConsoleKit has been replaced with systemd-logind, which has no
equivalent for ck-launch-session and requires X to be started on the
same terminal as the console used to run `startx`.
Could /etc/X11/xinit/xserverrc be replaced with the following to
accommodate this and ensure that systemd-logind works properly with
`startx`?
#!/bin/bash
TTY="${TTY:-$(tty)}"
TTY="${TTY#/dev/}"
if [[ $TTY != tty* ]]; then
printf '==> ERROR: invalid TTY\n' >&2
exit 1
fi
printf -v VT 'vt%02d' "${TTY#tty}"
exec /usr/bin/X -nolisten tcp -dpi 100 "$VT" "$@"
This script comes from
http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html
Some additional references:
http://askubuntu.com/questions/362403/how-to-create-a-new-logind-session-while-running-xinit-from-the-console
https://bugzilla.redhat.com/show_bug.cgi?id=806491
https://bugs.freedesktop.org/show_bug.cgi?id=71171
** Affects: xinit (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1247484
Title:
systemd-logind sessions are not set up properly if `startx` is used
Status in “xinit” package in Ubuntu:
New
Bug description:
In Raring and earlier, ConsoleKit was used for session management, and
/etc/X11/Xsession.d/90consolekit took care of preparing ConsoleKit
sessions via `ck-launch-session` when X was started via `startx`
instead of a graphical login manager.
In Saucy, ConsoleKit has been replaced with systemd-logind, which has
no equivalent for ck-launch-session and requires X to be started on
the same terminal as the console used to run `startx`.
Could /etc/X11/xinit/xserverrc be replaced with the following to
accommodate this and ensure that systemd-logind works properly with
`startx`?
#!/bin/bash
TTY="${TTY:-$(tty)}"
TTY="${TTY#/dev/}"
if [[ $TTY != tty* ]]; then
printf '==> ERROR: invalid TTY\n' >&2
exit 1
fi
printf -v VT 'vt%02d' "${TTY#tty}"
exec /usr/bin/X -nolisten tcp -dpi 100 "$VT" "$@"
This script comes from
http://blog.falconindy.com/articles/back-to-basics-with-x-and-systemd.html
Some additional references:
http://askubuntu.com/questions/362403/how-to-create-a-new-logind-session-while-running-xinit-from-the-console
https://bugzilla.redhat.com/show_bug.cgi?id=806491
https://bugs.freedesktop.org/show_bug.cgi?id=71171
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xinit/+bug/1247484/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878997] Re: setting nopasswdlogin removes user password
*** This bug is a duplicate of bug 882255 *** https://bugs.launchpad.net/bugs/882255 I'm pretty sure this is a bug in gnome-control-center. I'm pretty sure that is where most users configure the 'nopasswdlogin' membership (via the 'Login without a password' setting under 'User Management') ** This bug has been marked a duplicate of bug 882255 No administrative actions possible (password refused) after enabling passwordless login -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/878997 Title: setting nopasswdlogin removes user password Status in “lightdm” package in Ubuntu: New Bug description: When user wants to setup login without password, user adds to nopasswdlogin group (it is fine), but actual password is removed as well. This makes impossible using the sudo or gksudo command if user was in adm group. Workaround is booting in recovery mode and manual setting password to the user. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 1.0.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Oct 20 22:03:52 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/878997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 906081] [NEW] Disabling 'Login without a password' does not remove user from the nopasswdlogin group
Public bug reported: Fresh install of Ubuntu Oneiric. Created a new user account using 'adduser' on the command line, then set 'Login without a password' via 'User Management' in gnome-control-center. After performing some additional initial configuration of the box, went back to 'User Management', disabled 'Login without a password', and configured a password for the user. On subsequent reboots, was still able to login without a password. Tried enabling and disabling 'Login without a password' several times via 'User Management', but eventually had to manually remove the user from the 'nopasswdlogin' group to disable this feature. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/906081 Title: Disabling 'Login without a password' does not remove user from the nopasswdlogin group Status in “gnome-control-center” package in Ubuntu: New Bug description: Fresh install of Ubuntu Oneiric. Created a new user account using 'adduser' on the command line, then set 'Login without a password' via 'User Management' in gnome-control-center. After performing some additional initial configuration of the box, went back to 'User Management', disabled 'Login without a password', and configured a password for the user. On subsequent reboots, was still able to login without a password. Tried enabling and disabling 'Login without a password' several times via 'User Management', but eventually had to manually remove the user from the 'nopasswdlogin' group to disable this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/906081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
