[Desktop-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.
Bug fixed if I move pam_systemd.so below pam_fscrypt.so in /etc/pam.d /common-session. Need to fix /usr/share/pam-configs/systemd so that pam_systemd.so always end up after libpam_fscrypt (and potentially everything else...) ** Package changed: pulseaudio (Ubuntu) => systemd (Ubuntu) ** Also affects: fscrypt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in fscrypt package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.
The previous version (1:13.99.1-1ubuntu3.4) has the same problem with trying to create ~/.config/pulse before the home directory is available (in this case decrypted). The theory at the moment is that the new patch in 1:13.99.1-1ubuntu3.5 makes the code break earlier and therefor retry faster. We might want to make sure the service waits for ~/. to be available before trying to create ~/.config/pulse, at least that's my initial thinking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1889416/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.
For some reason the latest update (1:3.99.1-1ubuntu3.5) break if the user has an encrypted home directory, in my case ext4 encryption. $ journalctl -xe --user-unit pulseaudio ``` -- Reboot -- Jul 29 14:59:18 wendigo systemd[2664]: Starting Sound Service... -- Subject: A start job for unit UNIT has begun execution -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit UNIT has begun execution. -- -- The job identifier is 25. Jul 29 14:59:18 wendigo pulseaudio[2681]: Failed to create secure directory (/home/nafallo/.config/pulse): No such file or directory Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- An ExecStart= process belonging to unit UNIT has exited. -- -- The process' exit code is 'exited' and its exit status is 1. Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. -- Subject: Unit failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The unit UNIT has entered the 'failed' state with result 'exit-code'. Jul 29 14:59:18 wendigo systemd[2664]: Failed to start Sound Service. -- Subject: A start job for unit UNIT has failed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A start job for unit UNIT has finished with a failure. -- -- The job identifier is 25 and the job result is failed. Jul 29 14:59:18 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 1. -- Subject: Automatic restarting of a unit has been scheduled -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Automatic restarting of the unit UNIT has been scheduled, as the result for -- the configured Restart= setting for the unit. Jul 29 14:59:18 wendigo systemd[2664]: Stopped Sound Service. -- Subject: A stop job for unit UNIT has finished -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- A stop job for unit UNIT has finished. -- -- The job identifier is 94 and the job result is done. ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020
[Desktop-packages] [Bug 1889416] [NEW] pulseaudio.service: Start request repeated too quickly.
Public bug reported: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago TriggeredBy: ● pulseaudio.socket Main PID: 5675 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service... Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.5 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nafallo5675 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 15:11:28 2020 InstallationDate: Installed on 2018-06-27 (763 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0W970W dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1889416 Title: pulseaudio.service: Start request repeated too quickly. Status in pulseaudio package in Ubuntu: New Bug description: PA doesn't start on it's own after the latest update. ``` nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 11min ago TriggeredBy: ● pulseaudio.socket Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal (code=exited, status=1/FAILURE) Main PID: 2774 (code=exited, status=1/FAILURE) Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request repeated too quickly. Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 'exit-code'. Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service. ``` But works after starting it manually. ``` nafallo@wendigo:~$ systemctl --user start pulseaudio nafallo@wendigo:~$ systemctl --user status pulseaudio ● pulseaudio.service - Sound Service Loaded:
[Desktop-packages] [Bug 1116791] Re: xterm and gnome-terminal should not be dependencies
This bug has actually been fixed. At least in Bionic we now have: * xinit: Recommends: ... gnome-terminal | xterm | x-session-manager | x-window-manager | x-terminal-emulator * xorg: Depends: ... gnome-terminal | xterm | x-terminal-emulator, xinput -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1116791 Title: xterm and gnome-terminal should not be dependencies Status in ubuntu-meta package in Ubuntu: Fix Released Status in xinit package in Ubuntu: Won't Fix Status in xorg package in Ubuntu: Won't Fix Bug description: Hi, ubuntu-desktop depends on xterm and gnome-terminal. xorg is a dependency as well, and in turn depends on xterm | x-terminal- emulator. Something is wrong here. I'd say either removing the depends on the terminal emulators from ubuntu-desktop or, in case of xorg getting replaced at some point, depend on xterm | x-terminal-emulator here too... Best wishes, Nafallo ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-desktop 1.293 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic i686 NonfreeKernelModules: wl ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Tue Feb 5 23:58:17 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-09 (485 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20111007.1) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to raring on 2012-12-07 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1116791/+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 1773213] Re: U1 login dialog missing link to the privacy policy
nafallo@wendigo:~$ apt policy gnome-online-accounts gnome-online-accounts: Installed: 3.28.0-0ubuntu2.1 Candidate: 3.28.0-0ubuntu2.1 Version table: *** 3.28.0-0ubuntu2.1 400 400 http://se.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu2 500 500 http://se.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Same with the rest of the packages built from the source. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1773213] Re: U1 login dialog missing link to the privacy policy
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1773213] Re: U1 login dialog missing link to the privacy policy
I can confirm this is working as intended. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1773213 Title: U1 login dialog missing link to the privacy policy Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Bionic: Fix Committed Bug description: The U1 login for g-o-a is missing a link to the privacy policy. [Impact] * No way to view the privacy policy for Ubuntu One [Test Case] * Open gnome-control-center * Select "Online Accounts" on the left * Select "Ubuntu Single Sign-On" under "Add an account" * Not you should see a link to open the Privacy Policy on the bottom left of the dialog. * Verify when clicking the window a browser window opens with our data privacy page [Regression Potential] * None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+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 1771976] Re: Collect physical screen size
Before:
"Screens": [
{
"Resolution": "1920x1080",
"Frequency": "60.00"
}
],
After:
"Screens": [
{
"Size": "294mmx165mm",
"Resolution": "1920x1080",
"Frequency": "60.00"
}
],
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1771976
Title:
Collect physical screen size
Status in ubuntu-report:
Fix Released
Status in ubuntu-report package in Ubuntu:
Fix Released
Status in ubuntu-report source package in Bionic:
Fix Committed
Bug description:
[Impact]
* ubuntu-report collects the current resolution, it would be useful
to collect the physical screen size and be able to compute pixel
density for example.
[Test Case]
* Run ubuntu-report show
* Check that there is now a new field reporting the screen physical size
alongside the resolution.
[Regression Potential]
* Everything that isn't matched is just ignored ant not part of the finale
json report.
* We have an extensive testsuite covering the previous supported case and
now this one that was added.
ubuntu-report collects the current resolution, it would be useful to
collect the physical screen size and be able to compute pixel density
for example.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: ubuntu-report 1.0.11
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 18 11:17:10 2018
Dependencies:
gcc-8-base 8.1.0-2ubuntu1
libc6 2.27-3ubuntu1
libgcc1 1:8.1.0-2ubuntu1
InstallationDate: Installed on 2014-07-15 (1403 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubuntu-report
UpgradeStatus: Upgraded to cosmic on 2018-03-24 (54 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-report/+bug/1771976/+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 1730765] Re: Mounted external devices do not appear in dock
** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1730765 Title: Mounted external devices do not appear in dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Hi, when plugging a usb-thumb or external hard drive or any other storage media ( phone… ) I expected them to appear in the dock. Instead, they appear on desktop which forces - to leave current activity to look at the desktop, - or to open nautilus to find the new device. Dock is a very nice place for these plugged-in devices ;-) maybe at its bottom end, where trash used to be located in Unity dock ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730765/+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 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Hi, As discussed with duflu on irc, here are the steps I took to reproduce and produce a log: 1. Enable debug in /etc/gdm3/custom.conf 2. Reboot 3. From other laptop; ssh wendigo journalctl -f 4. Intentially login with a faulty password first, which made GDM just prompt as normal 5. Login with the correct password, which caused the purple screen + mouse 6. Copy the log up to this point 7. Press a bunch of ctrl+alt+fn+f-key combos until I got back to login screen 8. Login as normal, ctrl+c the SSH session and scp the file. ** Attachment added: "wendigo journalctl" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137/+attachment/5126446/+files/journalctl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Trying to log into my session (Gnome, Xorg), if I enter the wrong password before entering it correctly, the session doesn't load and I get a purple screen, a mouse cursor, and an invisible but clickable menu in the top right. If I enter it correctly the first time, there is no problem. I've replicated this from a fresh boot, after logging out and after 'sudo service gdm restart' from the Ctrl-Alt-F4 console. This is a fresh install, and didn't occur when I was using a previous install of 18.04 (until Friday). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 22 20:31:13 2018 InstallationDate: Installed on 2018-04-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137/+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 1054458] Re: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304'
This bug have popped up again in Bionic. nafallo@wendigo:~$ nvidia-detector Traceback (most recent call last): File "/usr/bin/nvidia-detector", line 8, in a = NvidiaDetection(printonly=True, verbose=False) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 68, in __init__ self.getData() File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 151, in getData driver_version = self.__get_value_from_name(stripped_package_name) File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line 87, in __get_value_from_name v = int(name) ValueError: invalid literal for int() with base 10: 'driver-390' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1054458 Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304' Status in nvidia-common package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-common source package in Precise: Fix Released Status in ubuntu-drivers-common source package in Precise: Invalid Status in nvidia-common source package in Quantal: Invalid Status in ubuntu-drivers-common source package in Quantal: Fix Released Bug description: If other people report this at the current level with xorg/nvidia it might be a bug. It is also possible the error stems from a bad combination of free and proprietary material. Further details will be provided as necessary/available. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: ubuntu-drivers-common 1:0.2.69 ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Fri Sep 21 22:48:18 2012 ExecutablePath: /usr/bin/nvidia-detector InterpreterPath: /usr/bin/python3.2mu ProcCmdline: /usr/bin/python3.2 /usr/bin/nvidia-detector ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=de_CH.UTF-8 LANGUAGE=de_CH:de PythonArgs: ['/usr/bin/nvidia-detector'] SourcePackage: ubuntu-drivers-common Title: nvidia-detector crashed with ValueError in __get_value_from_name(): invalid literal for int() with base 10: 'experimental-304' UpgradeStatus: Upgraded to quantal on 2012-07-31 (52 days ago) UserGroups: audio pulse pulse-access video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-common/+bug/1054458/+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 1753776] Re: Graphics corruption (or distortion?) in login animation to Xorg sessions
nafallo@wendigo:~$ lspci -nn|grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) This is on a Dell XPS 13 9370 (Development Edition), in case someone want to look at what the display can handle etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1753776 Title: Graphics corruption (or distortion?) in login animation to Xorg sessions Status in X.Org X server: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1576024] Re: Wifi "device not ready" after booting into OS for the 1st time
Any progress in seeing this fixed in Xenial? -- 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/1576024 Title: Wifi "device not ready" after booting into OS for the 1st time Status in network-manager package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Incomplete Status in wpa package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Invalid Status in ubiquity source package in Xenial: Confirmed Status in wpa source package in Xenial: Fix Committed Bug description: [Impact] Users booting from OEM setup may find that their wireless device is "not ready" as per NetworkManager, because wpasupplicant is not running. This is because the steps taken to start in OEM prepare, before moving to the real system runs systemctl isolate, and wpasupplicant gets caught in the crossfire. [Test case] * Steps to reproduce: 1. Install in OEM mode 2. Boot into OS 3. Check the wifi status in network-manager applet * Expected result: Available APs listed in network-manager applet, wifi connection can be established * Actual result: AP list replaced by a greyed-out "device not ready" wording Reboot system or do "$ sudo service network-manager restart" and wifi will then start working correctly. [Regression potential] The following are examples of possible regression scenarios from this stable update: - Failure to get the wireless device ready at session start - Driver loading issues for the wireless devices - Failure to complete OEM preparation steps, due to the oem user remaining connected while it's being removed by the last steps of the OEM preparation process. [Background information] * OS: Xenial * Network-manager: 1.1.93-0ubuntu4 * Wireless module: Marvell Technology Group Ltd. 88W8897 [AVASTAR] 802.11ac Wireless [11ab:2b38] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576024/+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 1729656] [NEW] changes to distribution.ini gets overwritten on upgrade
Public bug reported: Hi, I changed distribution.ini from Ubiquity late-command, and then as part of my customisation script upgrade all packages. My changes disappear, and the homepage in Firefox reverts to about:startpage instead of my corporations required intranet. Cheers, Nafallo ** Affects: ubufox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubufox in Ubuntu. https://bugs.launchpad.net/bugs/1729656 Title: changes to distribution.ini gets overwritten on upgrade Status in ubufox package in Ubuntu: New Bug description: Hi, I changed distribution.ini from Ubiquity late-command, and then as part of my customisation script upgrade all packages. My changes disappear, and the homepage in Firefox reverts to about:startpage instead of my corporations required intranet. Cheers, Nafallo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubufox/+bug/1729656/+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 840875] Re: Empathy sends a notification Password required without any supplementary info
I haven't got the issue mentioned in the last comment on any of my computers, fwiw. Not likely to be relevant to this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/840875 Title: Empathy sends a notification Password required without any supplementary info Status in “empathy” package in Ubuntu: Confirmed Bug description: Empaty has automatically re-imported my account from Natty (gmail/jabber). At startup, it now always displays a notification x...@jabber.org Password required (idem for gmail). It connects however successfully to my accounts. The notification should either be removed or give more details: which password is required, where, etc. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.1.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 Date: Sun Sep 4 12:10:32 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=fr:en PATH=(custom, no user) LANG=fr_FR.UTF-8 LC_MESSAGES=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-09-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/840875/+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 845470] [NEW] Notification bubble on every connect
Public bug reported: Hi, Every time I open empathy on my up-to-date oneiric laptop I get notifications that my password is required. After displaying that bubble it must realise it already have my password though, cause it goes ahead and connect. Let me know if any more info is needed. I'm Nafallo on IRC and try to keep up with my bugmail as well. Cheers, /N ** Affects: empathy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/845470 Title: Notification bubble on every connect Status in “empathy” package in Ubuntu: New Bug description: Hi, Every time I open empathy on my up-to-date oneiric laptop I get notifications that my password is required. After displaying that bubble it must realise it already have my password though, cause it goes ahead and connect. Let me know if any more info is needed. I'm Nafallo on IRC and try to keep up with my bugmail as well. Cheers, /N To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/845470/+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
