[Touch-packages] [Bug 1879090] Re: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Thank you for responding. I wonder if it's intended by design. I used to logout via `dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 'org.freedesktop.login1.Manager.TerminateSession' string:$XDG_SESSION_ID` or `loginctl kill-session $XDG_SESSION_ID` in my scripts. I can live without them. Did developers drop those environment variables? Another question: Is that issue related to `lightdm` or `systemd`? Regards. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: Incomplete Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879090] [NEW] XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set
Public bug reported: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1879090 Title: XDG_SEAT, XDG_VTNR, XDG_SESSION_ID not set Status in lightdm package in Ubuntu: New Bug description: I installed Ubuntu 20.04, it is running well. I switched display manager to lightdm. I noticed that it fails to set environment variables XDG_SEAT, XDG_VTNR, XDG_SESSION_ID. I also tested gdm3, it's the same. I also tried liveiso to no vail. apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu3.1 Candidate: 1.30.0-0ubuntu3.1 Version table: *** 1.30.0-0ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1879090/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350393] Re: Recent accountsservice update causes login window to hang
I am still suffering from this bug. I am on Ubuntu 16.04 32 bit platform. I installed libvirt-qemu and it adds itself to user group as ` libvirt-qemu:x:64055:128:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false`. Since its user id > 1000 it hangs the lightdm over one minute due to above bug. How can I work around this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 411688]
I noticed the same bug in my system ( Ubuntu 14.04.5) while I was trying to set up pulseaudio server in Windows 10 over the local network. In my case network flooding occurs whenever I launch pavucontrol, upload traffics reaches up to 200kb/s and it reduced the local network unusable. When I close it the network attack diminishes. I added `unload-module module-rtp-send` into `/etc/pulse/default.pa` to workaround the bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Arch Linux: Unknown Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 efee 800a ee96 0x0020: 0071 b380 ed51 a42b 000
[Touch-packages] [Bug 1773517] Re: lightdm takes too long to show up
I found the two bugs below may be related to my bug report. Removing the accountsservice check of lightdm will fix the issue. This bug is fixed, if it's not a regression, that fix doesn't work on the slow greeter problem. https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1443178 This one is still pending. https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1773517 Title: lightdm takes too long to show up Status in lightdm package in Ubuntu: Confirmed Bug description: I am running Ubuntu 16.04.4 with multiarch support. When I start the laptop it boots well till it reaches the lightdm screen. When the login text appears, screen goes black about 1.5-2 minutes then lightdm screen shows up. I have three users, I noticed that each user takes 25 seconds timeout to complete the process. journalctl -b0 _SYSTEMD_UNIT=lightdm.service -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 MSK. -- May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1001: Timeout was reached May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1000: Timeout was reached May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User64055: Timeout was reached May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error getting user list from org.freedesktop.Accounts: Timeout was reached May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "****" May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened for user by (uid=0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 996791] Re: Xubuntu 12.04 extremely slow login
I am running Ubuntu 16.04.04, I am suffering from the same bug. I issued a new bug here https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517 I tried the patch at #17 but it's not applicable to new code, I don't know how to remove accountservice check. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/996791 Title: Xubuntu 12.04 extremely slow login Status in accountsservice package in Ubuntu: Confirmed Bug description: The core issue is that /usr/lib/accountsservice/accounts-daemon doesn't accept dbus messages on boot. The symptom to this problem is that, after successfulling entering your login information, the system takes about 85 seconds to boot. The real issue occuring is that /usr/lib/accountsservice/accounts- daemon isn't being started correctly by ligthdm. The accounts-daemon wont accept dbus requests, and so the dbus timeout is hit during boot. Before I start, here is a run down on my machine/setup: Intel I7. Xubuntu 12.04. Encrypted home drive. Running compiz. Enabling the log files on lightdm, the follow warnings are displayed (Notice the times): [+11.58s] DEBUG: Greeter quit [+36.60s] WARNING: Could not call SetXSession: Timeout was reached [+61.63s] WARNING: Could not call FindUserByName: Timeout was reached [+61.63s] DEBUG: Dropping privileges to uid 1000 [+61.63s] DEBUG: Restoring privileges [+86.65s] WARNING: Could not call FindUserByName: Timeout was reached If the /usr/lib/accountsservices/accounts-daemon is restarted, after the lightdm login screen is displayed, but before a login, then xfce will start immediately. Otherwise boot times take about 87 seconds. Also, it was found that the program d-feet, is unable to retrive valid methods from /usr/lib/accountsservices/accounts-daemon before it is restarted. After the deamon is restarted, all dbus methods are visuable and communicate correctly. For descussion on the problem, and a temporary fix, see the following thread: http://ubuntuforums.org/showthread.php?t=1970326 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773517] [NEW] lightdm takes too long to show up
Public bug reported: I am running Ubuntu 16.04.4 with multiarch support. When I start the laptop it boots well till it reaches the lightdm screen. When the login text appears, screen goes black about 1.5-2 minutes then lightdm screen shows up. I have three users, I noticed that each user takes 25 seconds timeout to complete the process. journalctl -b0 _SYSTEMD_UNIT=lightdm.service -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 MSK. -- May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1001: Timeout was reached May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1000: Timeout was reached May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User64055: Timeout was reached May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error getting user list from org.freedesktop.Accounts: Timeout was reached May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "" May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened for user by (uid=0) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1773517 Title: lightdm takes too long to show up Status in lightdm package in Ubuntu: New Bug description: I am running Ubuntu 16.04.4 with multiarch support. When I start the laptop it boots well till it reaches the lightdm screen. When the login text appears, screen goes black about 1.5-2 minutes then lightdm screen shows up. I have three users, I noticed that each user takes 25 seconds timeout to complete the process. journalctl -b0 _SYSTEMD_UNIT=lightdm.service -- Logs begin at Sat 2018-05-05 23:07:44 MSK, end at Sat 2018-05-26 12:29:35 MSK. -- May 26 12:20:28 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1001: Timeout was reached May 26 12:20:53 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User1000: Timeout was reached May 26 12:21:18 kenn lightdm[1967]: ** (lightdm:1967): WARNING **: Error updating user /org/freedesktop/Accounts/User64055: Timeout was reached May 26 12:22:33 kenn lightdm[1967]: ** (process:5081): WARNING **: Error getting user list from org.freedesktop.Accounts: Timeout was reached May 26 12:22:33 kenn lightdm[5081]: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) May 26 12:23:41 kenn lightdm[9749]: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" was met by user "" May 26 12:24:06 kenn lightdm[9749]: pam_unix(lightdm:session): session opened for user by (uid=0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1773517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688933] Re: systemd restart-loops logind
I just noticed that I have the same exact issue. I am running Ubuntu 16.04 Desktop, I enabled multiarch support and I am running 32 bit installation with 64 bit kernel. May 24 12:59:13 kenn systemd-logind[1680]: Failed to send delayed message: Unit suspend-to-hibernate.service not found. May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Unit entered failed state. May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Failed with result 'exit-code'. May 24 12:59:13 kenn systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 24 12:59:13 kenn systemd[1]: Stopped Login Service. May 24 12:59:13 kenn systemd[1]: Starting Login Service... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1688933 Title: systemd restart-loops logind Status in systemd package in Ubuntu: Confirmed Bug description: Syslog logs systemd trying to restart logind every few seconds: May 7 00:51:29 server systemd[1]: Starting Login Service... May 7 00:51:54 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE May 7 00:51:54 server systemd[1]: Failed to start Login Service. May 7 00:51:54 server systemd[1]: systemd-logind.service: Unit entered failed state. May 7 00:51:54 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'. May 7 00:51:54 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 7 00:51:54 server systemd[1]: Stopped Login Service. May 7 00:51:54 server systemd[1]: Starting Login Service... May 7 00:52:19 server systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE May 7 00:52:19 server systemd[1]: Failed to start Login Service. May 7 00:52:19 server systemd[1]: systemd-logind.service: Unit entered failed state. May 7 00:52:19 server systemd[1]: systemd-logind.service: Failed with result 'exit-code'. May 7 00:52:19 server systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. May 7 00:52:19 server systemd[1]: Stopped Login Service. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu17 ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-51-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun May 7 00:51:07 2017 InstallationDate: Installed on 2013-08-21 (1353 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130423.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-51-generic root=UUID=16120d81-8cde-4e81-87cd-f55f65a4923b ro rootflags=subvol=@ SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-10-24 (193 days ago) dmi.bios.date: 03/13/2014 dmi.bios.vendor: Intel Corp. dmi.bios.version: SWQ6710H.86A.0067.2014.0313.1347 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ67OW dmi.board.vendor: Intel Corporation dmi.board.version: AAG12528-309 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSWQ6710H.86A.0067.2014.0313.1347:bd03/13/2014:svn:pn:pvr:rvnIntelCorporation:rnDQ67OW:rvrAAG12528-309:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1688933/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289047] Re: [Trusty] hostapd package is broken
It's unbelievable to see that the buggy package ist still in repo and no fix has proposed yet! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1289047 Title: [Trusty] hostapd package is broken Status in One Hundred Papercuts: Triaged Status in wpa package in Ubuntu: Triaged Bug description: When trying to create an access point, I am met with a fatal error with hostapd: nl80211: Could not configure driver mode nl80211 driver initialization failed. hostapd_free_hapd_data: Interface wlan0 wasn't started What worked before no longer works today after a package upgrade. After installing hostapd deb from Ubuntu 13.10, it works. WORKAROUND: For this to persist through reboots, execute the following in a terminal: sudo nano /etc/NetworkManager/NetworkManager.conf Add the following entry where the x's are replaced with your WiFi MAC address, save, and then reboot: [keyfile] unmanaged-devices=mac:xx:xx:xx:xx:xx:xx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hostapd 1:2.1-0ubuntu1 Uname: Linux 3.14.0-031400rc5-lowlatency x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Thu Mar 6 16:57:20 2014 InstallationDate: Installed on 2014-02-01 (33 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140121.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_CA.UTF-8 LANGUAGE=en_CA:en SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1289047/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 411688] Re: pulseaudio floods network with multicast packets
I am on Ubuntu 14.04.5 platform. I came across the same bug yesterday while trying to set up pulseaudio server on Windows to send audio from my Ubuntu laptop in local network and it rendered the home network unusable. It costed me hours to locate the pest. Dos attack triggered by pavucontrol, when I close it flooding diminishes. I implemented the following workaround `pactl unload-module module-rtp- send` Nobody's patched it for 8 years, so we have to live with this bug and no RTP server until my learning curve reaches a higher level to overcome it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/411688 Title: pulseaudio floods network with multicast packets Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Debian: Fix Released Bug description: Binary package hint: pulseaudio Since a karmic update last week, when pulseaudio is running it floods the network with multicast packets, to the point where the wireless interface I'm using is so flooded that no other network traffic can be transfered. Here is a snippet of tcpdump -i wlan 0 -n: ---8<--- 01:10:36.532748 IP (tos 0x10, ttl 1, id 23823, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d0f 4000 0111 2d6d 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f9f6 800a ee8e 0x0020: 0071 a980 ed51 a42b 0x0030: 0x0040: 01:10:36.53 IP (tos 0x10, ttl 1, id 23824, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d10 4000 0111 2d6c 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f8b5 800a ee8f 0x0020: 0071 aac0 ed51 a42b 0x0030: 0x0040: 01:10:36.547289 IP (tos 0x10, ttl 1, id 23825, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d11 4000 0111 2d6b 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f774 800a ee90 0x0020: 0071 ac00 ed51 a42b 0x0030: 0x0040: 01:10:36.556725 IP (tos 0x10, ttl 1, id 23826, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d12 4000 0111 2d6a 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f633 800a ee91 0x0020: 0071 ad40 ed51 a42b 0x0030: 0x0040: 01:10:36.561680 IP (tos 0x10, ttl 1, id 23827, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d13 4000 0111 2d69 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f4f2 800a ee92 0x0020: 0071 ae80 ed51 a42b 0x0030: 0x0040: 01:10:36.568984 IP (tos 0x10, ttl 1, id 23828, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d14 4000 0111 2d68 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f3b1 800a ee93 0x0020: 0071 afc0 ed51 a42b 0x0030: 0x0040: 01:10:36.576212 IP (tos 0x10, ttl 1, id 23829, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d15 4000 0111 2d67 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f270 800a ee94 0x0020: 0071 b100 ed51 a42b 0x0030: 0x0040: 01:10:36.588095 IP (tos 0x10, ttl 1, id 23830, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d16 4000 0111 2d66 0a00 0001 0x0010: e000 0038 b0b0 b6dc 0514 f12f 800a ee95 0x0020: 0071 b240 ed51 a42b 0x0030: 0x0040: 01:10:36.590645 IP (tos 0x10, ttl 1, id 23831, offset 0, flags [DF], proto UDP (17), length 1320) 10.0.0.1.45232 > 224.0.0.56.46812: UDP, length 1292 0x: 4510 0528 5d17 4000 0111 2d65 0a00 0001 0x0010: e000 0038 b0b
[Touch-packages] [Bug 1020512] Re: Assistive Technologies is spamming .cache with many folders like at-spi2-AYBRGW for example
I have the same problem on Ubuntu 14.04.3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1020512 Title: Assistive Technologies is spamming .cache with many folders like at- spi2-AYBRGW for example Status in at-spi2-atk package in Ubuntu: Fix Released Bug description: Two processes are running, at-spi2-registryd and at-spi-bus-launcher, even though I've unticked AT-SPI D-Bus instartup apps. I've uninstalled all but at-spi2-core and the spamming continues. Even after killing the above to processes. So I'm guessing dbus must be involved. Please feel free to change the package for the bug. The contents of all the folders contain 1 file named socket of 0 bytes. This file cant be opened. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: at-spi2-core 2.5.3-1 ProcVersionSignature: Ubuntu 3.5.0-3.3-generic 3.5.0-rc5 Uname: Linux 3.5.0-3-generic x86_64 ApportVersion: 2.2.5-0ubuntu2 Architecture: amd64 Date: Tue Jul 3 12:14:29 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120609.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: at-spi2-core UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 2012-06-25T13:25:47.813621 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1020512/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
