[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

2022-09-24 Thread James Lewis
Sorry, this answer has confused me even more... heres an example of what
we're currently using, perhaps you can speak to that,,, the user in this
case has no special rights, certainly not cap_sys_admin.

james@trinity:~$ grep james /etc/subuid
james:10:65536
james@trinity:~$ ls -asl .local/share/lxc/2004test/rootfs/ | head -8
total 68
4 drwxr-xr-x 17 10 10 4096 Aug 14  2020 .
4 drwxrwx---  3 10 james  4096 Aug 14  2020 ..
0 lrwxrwxrwx  1 10 107 Aug 14  2020 bin -> usr/bin
4 drwxr-xr-x  2 10 10 4096 Apr 15  2020 boot
4 drwxr-xr-x  3 10 10 4096 Aug 14  2020 dev
4 drwxr-xr-x 70 10 10 4096 Aug 14  2020 etc
4 drwxr-xr-x  3 10 10 4096 Aug 14  2020 home


james@trinity:~$ whoami
james
james@trinity:~$ lxc-start -n 2004test
james@trinity:~$ lxc-attach -n 2004test
root@2004test:/# exit
exit
james@trinity:~$ lxc-stop -n 2004test
james@trinity:~$

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990064

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

2022-09-24 Thread James Lewis
I'm still trying to understand the exact implications of this, since I
make extensive use of LXC containers, using subuid/subgid mapping, so
that users can create containers without needing access to UID 0.

Are we talking about blocking namespaces where UID 0 in the container is
mapped to the real UID 0, or will it also impact containers where UID 0
in the container is mapped to some other UID.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990064

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

2022-09-22 Thread James Lewis
NB, also broke Steam (from .deb).

Is there a link anywhere to some of this discussion, happy for security
to be improved, but I'd like to understand what is being disabled, and
what the specific issue is.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990064

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1990064] Re: unconfined profile denies userns_create for chromium based processes

2022-09-22 Thread James Lewis
It broke for me between 5.19.0-15 and 5.19.0-17, and breaks every
flatpak app I have installed.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990064

Title:
  unconfined profile denies userns_create for chromium based processes

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  For Ubuntu 22.10, since the last kernel update, i can´t launch any
  chromium based browser, due to apparmor denying userns_create

  dmesg shows:
  apparmor="DENIED" operation="userns_create" class="namespace" info="User 
namespace creation restricted" error=-13 profile="unconfined" pid=21323 
comm="steamwebhelper" requested="userns_create" denied="userns_create"

  This happens for every process which uses a chromium engine, like
  google chrome itself or in this case steamwebhelper.

  Might be related to this change?:
  
https://patchwork.kernel.org/project/netdevbpf/patch/20220801180146.1157914-5-f...@cloudflare.com/

  not sure if it got merged in this form though..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1990064/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1894234] Re: Bluetooth not working with Gnome in Groovy (20.10)

2020-09-14 Thread James Lewis
As of 14 Sep, this is working in groovy... looks like things are
progressing with groovy,

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1894234

Title:
  Bluetooth not working with Gnome in Groovy (20.10)

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Having plugged in a USB bluetooth dongle, the gnome-bluetooth settiogs
  report that I have no bluetooth adapter, and I should plug one in.

  At the same time, I can see the bluetooth adapter with hciconfig, and
  in fact, I can pair with remote bluetooth devices using a 3rd party
  bluetooth manager (blueman).

  Obviously this is not ideal, as it is not fully integrated with gnome,
  sound devices are not fully available etc..

  I'm not sure what else I can provide, but:-

  # hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: 24:4B:FE:3A:21:65  ACL MTU: 1021:6  SCO MTU: 255:12
UP RUNNING PSCAN 
RX bytes:1117 acl:0 sco:0 events:72 errors:0
TX bytes:4973 acl:0 sco:0 commands:72 errors:0
Features: 0xff 0xff 0xff 0xfe 0xdb 0xfd 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF PARK 
Link mode: SLAVE ACCEPT 
Name: 'morpheous'
Class: 0x1c0104
Service Classes: Rendering, Capturing, Object Transfer
Device Class: Computer, Desktop workstation
HCI Version: 5.1 (0xa)  Revision: 0xb
LMP Version: 5.1 (0xa)  Subversion: 0x8761
Manufacturer: Realtek Semiconductor Corporation (93)

  root@morpheous:~#

  When I got to settings, it tells me I have no bluetooth devices
  plugged in!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894234/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1662187] Re: apt-get upgrade hung when it comes to update initramfs

2017-03-14 Thread James Lewis
This appears to be related to something peculiar happening to LVM, I'm
not using LVM, but /usr/share/initramfs-tools/hooks/cryptroot appears to
be trying to read a bunch of volume group data after reading
/etc/crypttab (which is empty!)...

+ grep -s ^[^#] /etc/crypttab
+ read target source key options
+ candidates=
+ devices=
+ count=0
+ [ 0 -gt 0 ]
+ return 0
+ initramfsdevs=
+ add_device 04f31c0c-8ee4--a571-9c798b0f1022
+ local node nodes opts lastopts i count
+ nodes=04f31c0c-8ee4--a571-9c798b0f1022
+ opts=
+ lastopts=
+ [ -z 04f31c0c-8ee4--a571-9c798b0f1022 ]
+ echo   
+ grep -q \b04f31c0c-8ee4--a571-9c798b0f1022\b
+ node_is_in_crypttab 04f31c0c-8ee4--a571-9c798b0f1022
+ local node
+ node=04f31c0c-8ee4--a571-9c798b0f1022
+ grep -q ^04f31c0c-8ee4--a571-9c798b0f1022\b /etc/crypttab
+ return 1
+ get_lvm_deps 04f31c0c-8ee4--a571-9c798b0f1022
+ local node deps maj min depnode
+ node=04f31c0c-8ee4--a571-9c798b0f1022
+ [ -z 04f31c0c-8ee4--a571-9c798b0f1022 ]
+ dmsetup --noheadings splitname 04f31c0c-8ee4--a571-9c798b0f1022
+ cut -d: -f1
+ vgs --noheadings -o pv_name 04f31c0c

Running any LVM command hangs...

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1662187

Title:
  apt-get upgrade hung when it comes to update initramfs

Status in Ubuntu on IBM z Systems:
  Invalid
Status in linux package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  apt-get upgrade process is hung when it comes to update the initramfs and it 
never finishes with any error messages.  So I have to kill the process and 
restart it. But the system asks run 'sudo dpkg --configure -a' to correct the 
problem if I run 'apt-get upgrade' again. I got the same problem with running 
'dpkg --configure -a'. 

  root@ub01:~# apt-get upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
linux-generic linux-headers-generic linux-image-generic python-glance-store
  0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.122ubuntu8.8) ...
  update-initramfs: Generating /boot/initrd.img-4.4.0-45-generic
  W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

  ---uname output---
  Linux ub01 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:14:35 UTC 2016 s390x 
s390x s390x GNU/Linux
   
  Machine Type = z13 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   apt-get update
  apt-get upgrade
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  -Attach sysctl -a output output to the bug.

  Below is what I have in the /boot directory

  -rw---  1 root root  2552549 Oct 19 10:23 System.map-4.4.0-45-generic
  -rw-r--r--  1 root root   535651 Oct 19 10:23 abi-4.4.0-45-generic
  -rw---  1 root root13824 Nov 21 20:12 bootmap
  -rw-r--r--  1 root root65205 Oct 19 10:23 config-4.4.0-45-generic
  lrwxrwxrwx  1 root root   27 Oct 26 16:52 initrd.img -> 
initrd.img-4.4.0-45-generic
  -rw-r--r--  2 root root 13325095 Nov 21 20:12 initrd.img-4.4.0-45-generic
  -rw-r--r--  2 root root 13325095 Nov 21 20:12 
initrd.img-4.4.0-45-generic.dpkg-bak
  -rw-r--r--  1 root root0 Feb  4 01:47 initrd.img-4.4.0-45-generic.new
  drwx--  2 root root12288 Oct 26 16:50 lost+found
  lrwxrwxrwx  1 root root   24 Oct 26 16:52 vmlinuz -> 
vmlinuz-4.4.0-45-generic
  -rw---  1 root root  3690376 Oct 19 10:23 vmlinuz-4.4.0-45-generic

  Below is the disk space, /boot has enough space.

  Filesystem Size  Used Avail Use% Mounted on
  udev   126G 0  126G   0% /dev
  tmpfs   26G  2.6G   23G  11% /run
  /dev/mapper/ub01--vg-root  101G  9.9G   87G  11% /
  tmpfs  126G 0  126G   0% /dev/shm
  tmpfs  5.0M 0  5.0M   0% /run/lock
  tmpfs  126G 0  126G   0% /sys/fs/cgroup
  /dev/mapper/mpatha-part1   472M   22M  426M   5% /boot
  cgmfs  100K 0  100K   0% /run/cgmanager/fs
  tmpfs   26G 0   26G   0% /run/user/1000
  tmpfs   26G 0   26G   0% /run/user/1002

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1662187/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : 

[Kernel-packages] [Bug 1389275] [NEW] Updating from 14.04 to 14.10 created a snapshot, but it did so AFTER updating the sources.

2014-11-04 Thread James Lewis
Public bug reported:

Using BTRFS to allow snapshot rollback from version updates actually
worked... I updated from 14.04 to 14.10 on Nov 1st, and encountered a
problem, I saw that update-manager had taken a snapshot before
completing the update, but after rollback I found that the snapshot was
taken AFTER the 14.10 sources had been put in place.

Clearly the snapshot should be taken before changes are made to the
package configuration, or rollback will not be complete.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: utopic

** Description changed:

  Using BTRFS to allow snapshot rollback from version updates actually
- worked... I updated from 14.04 to 14.10 on Nov 10th, and encountered a
+ worked... I updated from 14.04 to 14.10 on Nov 1st, and encountered a
  problem, I saw that update-manager had taken a snapshot before
  completing the update, but after rollback I found that the snapshot was
  taken AFTER the 14.10 sources had been put in place.
  
  Clearly the snapshot should be taken before changes are made to the
  package configuration, or rollback will not be complete.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1389275

Title:
  Updating from 14.04 to 14.10 created a snapshot, but it did so AFTER
  updating the sources.

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Using BTRFS to allow snapshot rollback from version updates actually
  worked... I updated from 14.04 to 14.10 on Nov 1st, and encountered a
  problem, I saw that update-manager had taken a snapshot before
  completing the update, but after rollback I found that the snapshot
  was taken AFTER the 14.10 sources had been put in place.

  Clearly the snapshot should be taken before changes are made to the
  package configuration, or rollback will not be complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389275/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1389275] Re: Updating from 14.04 to 14.10 created a snapshot, but it did so AFTER updating the sources.

2014-11-04 Thread James Lewis
I cannot provide the output of apport since the issue occurred before
the upgrade process which is now complete... however I think it's fairly
obvious, this is a procedural issue, not a crash... the BTRFS snapshot
needs to happen before it starts making changes to perform the update.

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1389275

Title:
  Updating from 14.04 to 14.10 created a snapshot, but it did so AFTER
  updating the sources.

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Using BTRFS to allow snapshot rollback from version updates actually
  worked... I updated from 14.04 to 14.10 on Nov 1st, and encountered a
  problem, I saw that update-manager had taken a snapshot before
  completing the update, but after rollback I found that the snapshot
  was taken AFTER the 14.10 sources had been put in place.

  Clearly the snapshot should be taken before changes are made to the
  package configuration, or rollback will not be complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1389275/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] Re: cryptswap can fail if random data matches a filesystem magic number

2014-10-28 Thread James Lewis
apport information

** Tags added: apport-collected utopic

** Description changed:

  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data that
  had the magic number of a filesystem type, and hence ever more it
  refused to start...
  
  Eg:-
  
  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256
  
  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 
  
  Obviosuly this is not a filesystem:-
  
  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error
  
  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-
  
  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s
  
  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
+ --- 
+ ApportVersion: 2.14.7-0ubuntu8
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  james  3650 F pulseaudio
+  /dev/snd/controlC1:  james  3650 F pulseaudio
+ DistroRelease: Ubuntu 14.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2014-04-28 (182 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
+ MachineType: LENOVO 20266
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-3.16.0-23-generic N/A
+  linux-backports-modules-3.16.0-23-generic  N/A
+  linux-firmware 1.138
+ Tags:  utopic
+ Uname: Linux 3.16.0-23-generic x86_64
+ UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 10/31/2013
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 76CN31WW
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: Yoga2
+ dmi.board.vendor: LENOVO
+ dmi.board.version: 31900058STD
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo Yoga 2 Pro
+ dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
+ dmi.product.name: 20266
+ dmi.product.version: Lenovo Yoga 2 Pro
+ dmi.sys.vendor: LENOVO

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247003/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I 

[Kernel-packages] [Bug 1386339] CurrentDmesg.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247006/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] CRDA.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1386339/+attachment/4247005/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] ProcCpuinfo.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247010/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] BootDmesg.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247004/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] IwConfig.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247007/+files/IwConfig.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] Lspci.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1386339/+attachment/4247008/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] Lsusb.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1386339/+attachment/4247009/+files/Lsusb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] UdevLog.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247015/+files/UdevLog.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] RfKill.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1386339/+attachment/4247013/+files/RfKill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] UdevDb.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1386339/+attachment/4247014/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] ProcInterrupts.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247011/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] ProcModules.txt

2014-10-28 Thread James Lewis
apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1386339/+attachment/4247012/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  james  3650 F pulseaudio
   /dev/snd/controlC1:  james  3650 F pulseaudio
  DistroRelease: Ubuntu 14.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-04-28 (182 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: LENOVO 20266
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic.efi.signed 
root=UUID=1cbc95ee-97a4-4869-b1a2-135f351313eb ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-23-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-14 (13 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 76CN31WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Yoga2
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 Pro
  dmi.modalias: 
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
  dmi.product.name: 20266
  dmi.product.version: Lenovo Yoga 2 Pro
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1386339] [NEW] cryptswap can fail if random data matches a filesystem magic number

2014-10-27 Thread James Lewis
Public bug reported:

I noticed that my encrypted swap was not working, and I found that the
randomly generated encrypted filesystem had randomly generated data that
had the magic number of a filesystem type, and hence ever more it
refused to start...

Eg:-

root@hardline:/etc# more /etc/crypttab
cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

root@hardline:/etc# cryptdisks_start cryptswap1
 * Starting crypto disk...  
 * cryptswap1 (starting)..
 * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
 * cryptswap1 (failed)...[fail] 

Obviosuly this is not a filesystem:-

root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
mount: wrong fs type, bad option, bad superblock on /dev/sda3,
   missing codepage or helper program, or other error

So I blanked it and restarted, all is now well... perhaps if there's a
force option on cryptsetup this should be used in the setup scripts:-

root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
^C684121+0 records in
684121+0 records out
350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

root@hardline:/etc# cryptdisks_start cryptswap1
 * Starting crypto disk...  
 * cryptswap1 (starting)..
 * cryptswap1 (started)...   [ OK ]

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386339

Title:
  cryptswap can fail if random data matches a filesystem magic number

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I noticed that my encrypted swap was not working, and I found that the
  randomly generated encrypted filesystem had randomly generated data
  that had the magic number of a filesystem type, and hence ever more it
  refused to start...

  Eg:-

  root@hardline:/etc# more /etc/crypttab
  cryptswap1 /dev/sda3 /dev/urandom swap,cipher=aes-cbc-essiv:sha256

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1: the precheck for '/dev/sda3' failed:  - The device /dev/sda3 
contains a filesystem type hfsplus.
   * cryptswap1 (failed)...
[fail] 

  Obviosuly this is not a filesystem:-

  root@hardline:/etc# mount -t hfsplus /dev/sda3 /mnt
  mount: wrong fs type, bad option, bad superblock on /dev/sda3,
 missing codepage or helper program, or other error

  So I blanked it and restarted, all is now well... perhaps if there's a
  force option on cryptsetup this should be used in the setup scripts:-

  root@hardline:/etc# dd if=/dev/zero of=/dev/sda3
  ^C684121+0 records in
  684121+0 records out
  350269952 bytes (350 MB) copied, 5.96378 s, 58.7 MB/s

  root@hardline:/etc# cryptdisks_start cryptswap1
   * Starting crypto disk...
   * cryptswap1 (starting)..
   * cryptswap1 (started)...   [ OK 
]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386339/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1252032] [NEW] hard hang when using l2tpd/pppd with IPv6

2013-11-17 Thread James Lewis
Public bug reported:

I'm not completely sure how to summarise this bug, but it's obviously
potentially fatal and related to the kernel components of either xl2tpd,
pppd or IPv6.

I have an IPv6 connection using xl2tpd to make a ppp connection and then
route IPv6 over that... this works fine, but if I stress it using heavy
traffic such as bittorrent, the entire system will lock up at the kernel
level after a time, between 10 minutes and 1 hour approximately.

This is using Trusty with the 3.12 kernel as of 17/Nov 2013...   I'm
really not sure how to go about debugging this, the only clue I can find
is this:-

Nov 16 23:32:17 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
Nov 16 23:32:17 trinity xl2tpd[2849]: handle_packet: bad control packet!
Nov 16 23:32:18 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
Nov 16 23:32:18 trinity xl2tpd[2849]: handle_packet: bad control packet!
Nov 16 23:32:19 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
Nov 16 23:32:19 trinity xl2tpd[2849]: handle_packet: bad control packet!
Nov 16 23:32:20 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
Nov 16 23:32:20 trinity xl2tpd[2849]: handle_packet: bad control packet!
Nov 16 23:32:21 trinity xl2tpd[2849]: control_finish: Connection closed to 
85.119.84.18, port 1701 (Timeout), Local: 25286, Remote: 35506
Nov 16 23:32:21 trinity xl2tpd[2849]: Terminating pppd: sending TERM signal to 
pid 7386

The connection is then re-established..

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1252032

Title:
  hard hang when using l2tpd/pppd with IPv6

Status in “linux-firmware” package in Ubuntu:
  New

Bug description:
  I'm not completely sure how to summarise this bug, but it's obviously
  potentially fatal and related to the kernel components of either
  xl2tpd, pppd or IPv6.

  I have an IPv6 connection using xl2tpd to make a ppp connection and
  then route IPv6 over that... this works fine, but if I stress it using
  heavy traffic such as bittorrent, the entire system will lock up at
  the kernel level after a time, between 10 minutes and 1 hour
  approximately.

  This is using Trusty with the 3.12 kernel as of 17/Nov 2013...   I'm
  really not sure how to go about debugging this, the only clue I can
  find is this:-

  Nov 16 23:32:17 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
  Nov 16 23:32:17 trinity xl2tpd[2849]: handle_packet: bad control packet!
  Nov 16 23:32:18 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
  Nov 16 23:32:18 trinity xl2tpd[2849]: handle_packet: bad control packet!
  Nov 16 23:32:19 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
  Nov 16 23:32:19 trinity xl2tpd[2849]: handle_packet: bad control packet!
  Nov 16 23:32:20 trinity xl2tpd[2849]: check_control: Received out of order 
control packet on tunnel 35506 (got 4, expected 5)
  Nov 16 23:32:20 trinity xl2tpd[2849]: handle_packet: bad control packet!
  Nov 16 23:32:21 trinity xl2tpd[2849]: control_finish: Connection closed to 
85.119.84.18, port 1701 (Timeout), Local: 25286, Remote: 35506
  Nov 16 23:32:21 trinity xl2tpd[2849]: Terminating pppd: sending TERM signal 
to pid 7386

  The connection is then re-established..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1252032/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp