[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-08-21 Thread Dean Henrichsmeyer
Sorry, I mean there's no amd64 version in bionic-proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1886572

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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


Re: [Touch-packages] [Bug 1886572] Please test proposed package

2020-08-21 Thread Dean Henrichsmeyer
There's no amd64 version of this package as far as I can tell.

On Fri, Aug 21, 2020 at 6:21 AM Timo Aaltonen <1886...@bugs.launchpad.net>
wrote:

> Hello Dean, or anyone else affected,
>
> Accepted base-files into xenial-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/base-
> files/9.4ubuntu4.13 in a few hours, and then in the -proposed
> repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested, what testing has been
> performed on the package and change the tag from verification-needed-
> xenial to verification-done-xenial. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-xenial. In either case, without details of your testing we will
> not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1886572
>
> Title:
>   Remove uptime from the motd-news user agent
>
> Status in base-files package in Ubuntu:
>   Fix Released
> Status in base-files source package in Xenial:
>   Fix Committed
> Status in base-files source package in Bionic:
>   Fix Committed
> Status in base-files source package in Focal:
>   Fix Committed
>
> Bug description:
>   [Impact]
>   The uptime value in the user-agent string sent to the motd-news server
> is unused and not necessary. It should be removed.
>
>   [Test Case]
>   Inspect the /etc/update-motd.d/50-motd-news script and verify that
> uptime is no longer used.
>
>   Previous version:
>   $ grep uptime /etc/update-motd.d/50-motd-news
>   # Some messages may only be pertinent before or after some amount of
> uptime
>   read up idle < /proc/uptime
>   uptime="uptime/$up/$idle"
>   USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime
> cloud_id/$cloud_id"
>
>   Updated version:
>   $ grep uptime /etc/update-motd.d/50-motd-news
>(no output)
>
>
>   [Regression Potential]
>   The server side, if it were checking this value, could be surprised by
> this change.
>
>   [Other Info]
>   N/A
>
>   [Original Description]
>   I don't why that was included but it shouldn't be. Please remove it.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=base-files;
> component=main; status=Fix Released; importance=High; assignee=
> andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug-Tags: verification-needed verification-needed-bionic
> verification-needed-focal verification-needed-xenial
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: ahasenack dean janitor tjaalton
> Launchpad-Bug-Reporter: Dean Henrichsmeyer (dean)
> Launchpad-Bug-Modifier: Timo Aaltonen (tjaalton)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: dean
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1886572

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  F

[Touch-packages] [Bug 1886572] [NEW] Remove uptime from the motd-news user agent

2020-07-06 Thread Dean Henrichsmeyer
Public bug reported:

I don't why that was included but it shouldn't be. Please remove it.

** Affects: base-files (Ubuntu)
 Importance: High
 Assignee: Andreas Hasenack (ahasenack)
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1886572

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  New

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1845950] Re: Bug reporting doesn't work upon a crash

2019-10-01 Thread Dean Henrichsmeyer
Here it is.

** Attachment added: "crashdb.conf"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+attachment/5293314/+files/crashdb.conf

** Changed in: apport (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1845950

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+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 1845950] [NEW] Bug reporting doesn't work upon a crash

2019-09-30 Thread Dean Henrichsmeyer
Public bug reported:

On eoan, after an initial startup / login, if an application crashes and
I click "report", I get a prompt saying the crash is reported and to
check the web page open in the browser to see if I have any additional
information.. except it never opens a page. The dialog just disappears,
the crash log stays in /var/crash and nothing happens.

The only way to actually file it is to run ubuntu-bug  which does
work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu7
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, signal 
6, core limit 0, dump mode 1
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashReports:
 640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
 640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 30 07:34:38 2019
InstallationDate: Installed on 2018-07-24 (432 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

** Affects: apport (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1845950

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+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 1815509] Re: Shutdown hung by firmware update daemon

2019-04-05 Thread Dean Henrichsmeyer
It's the last thing seen on the console when it happens. The machine in
question has been updated to disco and I haven't seen the behavior.

-- 
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/1815509

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1822881] [NEW] Whenever an application accesses the audio device there's a loud pop

2019-04-02 Thread Dean Henrichsmeyer
Public bug reported:

Upon an upgrade to disco, now when anything access the audio output I
get a loud pop. Happens with a browser (firefox and chrome), spotify,
etc. It's independent of the application.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  dean   3841 F pulseaudio
 /dev/snd/controlC0:  dean   3841 F pulseaudio
 /dev/snd/controlC1:  dean   3841 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  2 15:45:32 2019
InstallationDate: Installed on 2018-07-24 (252 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to disco on 2019-04-02 (0 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-406
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
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/1822881

Title:
  Whenever an application accesses the audio device there's a loud pop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upon an upgrade to disco, now when anything access the audio output I
  get a loud pop. Happens with a browser (firefox and chrome), spotify,
  etc. It's independent of the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   3841 F pulseaudio
   /dev/snd/controlC0:  dean   3841 F pulseaudio
   /dev/snd/controlC1:  dean   3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 15:45:32 2019
  InstallationDate: Installed on 2018-07-24 (252 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-04-02 (0 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822881/+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 1815509] Re: Shutdown hung by firmware update daemon

2019-03-27 Thread Dean Henrichsmeyer
This seems intermittent for me. I admit I don't reboot often but I've
been unable to reproduce it, even with leaving fwupd enabled.

-- 
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/1815509

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+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 1815509] [NEW] Shutdown hung by firmware update daemon

2019-02-11 Thread Dean Henrichsmeyer
Public bug reported:

When rebooting my desktop, the shutdown sequence hangs for a long time
on "Stopping firmware update daemon." It eventually will reboot but it
hangs there for quite some time before doing so.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.12
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 11 13:39:51 2019
InstallationDate: Installed on 2018-07-24 (202 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-406
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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/1815509

Title:
  Shutdown hung by firmware update daemon

Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815509/+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 1787460] [NEW] Unattended upgrades removed linux-image-generic

2018-08-16 Thread Dean Henrichsmeyer
Public bug reported:

On a fairly fresh install of 18.04 with no modifications whatsoever to
the unattended-upgrades configuration, it decided to remove linux-image-
generic which also removed linux-modules-extra which caused sound
drivers to disappear, etc.

The relative snippet from /var/log/unattended-upgrades/unattended-
upgrades.log is:

2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic
2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-08-15 06:18:39,238 INFO All upgrades installed
2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
2018-08-15 06:18:42,818 INFO Packages that are kept back:

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.5
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 13:17:30 2018
InstallationDate: Installed on 2018-07-24 (23 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1787460

Title:
  Unattended upgrades removed linux-image-generic

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

2018-02-22 Thread Dean Henrichsmeyer
Let's make sure this is fixed for bionic. The scope of nameservers has
changed and maas should do the right thing.

-- 
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/1750884

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host

2014-12-10 Thread Dean Henrichsmeyer
** Tags added: landscape

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1401148

Title:
  Re/starting an lxc container corrupts all network namespaces on the
  same physical host

Status in lxc package in Ubuntu:
  New

Bug description:
  Context: Neutron gateway north/south routing server which manages a
  large number of network namespaces; also hosts a few LXC containers
  for misc lightweight control plane services.

  Problem:  If I restart one of the lxc containers, all of the
  namespaces get corrupted in someway; attempting to exec anything in
  any namespace fails with:

  seting the network namespace qrouter-4b575c81-39bb-439f-81e1-e59e3759a287 
failed: Invalid argument
  seting the network namespace qrouter-1f5e26df-f8c5-4246-9485-3f9df8e39c40 
failed: Invalid argument
  seting the network namespace qrouter-c3bf179e-9532-43f9-88af-752b66592cd6 
failed: Invalid argument
  seting the network namespace qrouter-3d4550ca-4de6-44e3-90b5-1b60c3d58ed1 
failed: Invalid argument
  seting the network namespace qrouter-4fc4c3c2-68bf-4954-8b32-d47d8d84086e 
failed: Invalid argument
  seting the network namespace qrouter-0890d9ea-f0c8-4e69-bf1a-4896213a82a0 
failed: Invalid argument
  seting the network namespace qrouter-0f7e0655-f84b-4aaa-82aa-75f01a59411e 
failed: Invalid argument

  I also see:

  Dec 10 15:16:00 cofgod kernel: [ 4604.274359] type=1400 
audit(1418224560.675:132): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-0ba77ab2-b3ee-4752-88af-b19313c10f9d/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274405] type=1400 
audit(1418224560.675:134): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-25006453-2caa-4aa4-bdeb-e4822dc700d6/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274436] type=1400 
audit(1418224560.675:136): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-2fec74e8-d507-4650-beb4-8da459ea0039/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274451] type=1400 
audit(1418224560.675:137): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-33d8fa40-c158-4377-bc8f-d252e38d4943/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274466] type=1400 
audit(1418224560.675:138): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-394517c0-e48a-43e7-8778-96c601607733/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274482] type=1400 
audit(1418224560.675:139): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-41e21850-decf-49f8-97fb-cbb3aa5932e3/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274497] type=1400 
audit(1418224560.675:140): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qrouter-e9837293-c017-4d85-a601-cae5e83719a2/ pid=8790 
comm=lxc-start flags=rw, slave

  In the kern.log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Wed Dec 10 15:24:45 2014
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1401148/+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 1069802] Re: keyboard shortcut changes aren't preserved

2014-07-24 Thread Dean Henrichsmeyer
A bit of additional information. I *believe* if you
logout/restart/reboot by clicking the icon in the top right and using
the menu, the navigation shortcuts are preserved. If you restart by any
other method, IE, reboot, init 6, shutdown, etc then the navigational
shortcuts are wiped. I'll update this if I find out to the contrary but
so far that's what I've found.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1069802

Title:
  keyboard shortcut changes aren't preserved

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I change keyboard shortcuts (such as changing desktops) via the
  keyboard settings in system preferences, they are not preserved across
  restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct 22 15:09:29 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1069802/+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