[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-21 Thread Hadmut Danisch
Oh yeah, that helps! :-)


Uldis, can you confirm?

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Hadmut Danisch
BTW: what would pulseaudio / ubuntu pass out on HDMI if I do play two
audio sources, one with 44.1 and one with 48 kHz, at the same time?

Any tool or method to check what's going out to HDMI?

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Hadmut Danisch
I think I've found the problem.

@Uldis: please check and verify


It doesn't work with a video with 

Channel(s)   : 1 channel
Channel layout   : C
Sampling rate: 44.1 kHz


but it works when playing a video with

Channel(s)   : 2 channels
Sampling rate: 48.0 kHz


So maybe it's the sampling rate. Probably Linux outputs a sampling rate 
conforming with the current source, and the ATEM seems to expect 48kHz, while 
accepting everything on HDMI1, but getting it scrambled and distorted, since 
there's not enough data (8% missing), while the input on HDMI2-4 simply doesn't 
match the expectations.

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Hadmut Danisch
BTW, same with the older ATEM Mini (non-Pro)

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-20 Thread Hadmut Danisch
Confirmed:

distorted sound on HDMI1

no sound on HDMI2-4

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-14 Thread Hadmut Danisch
Pretty good hint, interesting.

However, the ATEM is definitely able to take audio in on all four HDMI
ports, since it has level indicators and buttons to turn it on and off
(and AFV=Audio follows Video) and adjust the level on all four HDMI
ports.

And I do have a camera with a builtin Mic (GoPro 4) on HDMI 2, which
perfectly takes the Audio from the camera mic.

So there must be some difference in the HDMI signal coming from a camera
(I had a Sony A6300, a Z-Cam e2c, and a GoPro 4 connected, all passing
audio properly to the ATEM) and the HDMI signal coming from a
Linux/Ubuntu notebook.

The cheap chinese LCD screen I used for testing doesn't care about the
difference, it just plays the sound, while the ATEM obviously bothers
about that difference, but, as Uldis figured out, only on Ports 2,3,4.

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  

[Touch-packages] [Bug 1910537] Re: HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video mixer)

2021-01-13 Thread Hadmut Danisch
> Please try running this command:

>  xrandr --output HDMI-1 --set audio on

> If it still doesn't work then try logging in again after that.


Neither did help...

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

Title:
  HDMI audio not working on Blackmagic Design ATEM Mini Pro ISO (video
  mixer)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  This is a complicated thing. I have a very specific problem with audio
  output on HDMI.

  I want to use an older notebook with Lubuntu 20.04 as a video source
  for libreoffice slides, videos etc. to feed them over HDMI into a
  Blackmagic Design ATEM Mini Pro ISO (video mixer) as one input.
  Configured on the desktop just like a second screen or beamer.

  Video works well and rock-stable, no problem at all.

  But not audio.

  Although I carefully configured audio with pavucontrol to be directed
  to the HDMI output, the ATEM switcher does not recognize it as an
  audio source (like when connecting a digital camera) and does not
  receive or indicate any audio input.

  Note:

  But when I use the very same computer, same HDMI cable, same video
  with a cheap chinese portable LCD screen with speakers (i.e. pull the
  cable from the ATEM and plug it into the screen) it immediately starts
  playing both video and audio. So there is evidence that the ubuntu
  notebook definitely passes it's sound to HDMI and there's really an
  audio signal on the HDMI.

  I've opened a bug at Blackmagic Design, and got their reply that they
  can't help and have never heard of such a problem before. Their guess
  is that the linux notebook is not setting EDID configuration correctly
  and thus not recognized by the ATEM, while the cheap LCD screen
  propably does not care about EDID and just plays everything, therefore
  a wrong EDID information would not matter.

  Although I have decades of experience with Linux, I am not too
  familiar with details of HDMI and the internals of the X11 driver, so
  I'm not sure where to start debugging, not even, whether this is a
  problem of Xorg/X11 or pulseaudio.


  I've checked this with another notebook with much more recent (intel)
  hardware, which offers dozens of HDMI audio options in the pavucontrol
  selection menu, but same problem: Video works, but the ATEM does not
  recognize it as a audio source.

  
  Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Thu Jan  7 13:16:26 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
  InstallationDate: Installed on 2020-05-16 (235 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer AO756
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Mimic
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Type1Family
  dmi.product.name: AO756
  dmi.product.sku: Type1Sku0
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer
  version.compiz: 

[Touch-packages] [Bug 1910537] [NEW] incorrect audio-EDID on HDMI, blocking audio transmission over HDMI

2021-01-07 Thread Hadmut Danisch
Public bug reported:

This is a complicated thing. I have a very specific problem with audio
output on HDMI.

I want to use an older notebook with Lubuntu 20.04 as a video source for
libreoffice slides, videos etc. to feed them over HDMI into a Blackmagic
Design ATEM Mini Pro ISO (video mixer) as one input. Configured on the
desktop just like a second screen or beamer.

Video works well and rock-stable, no problem at all.

But not audio.

Although I carefully configured audio with pavucontrol to be directed to
the HDMI output, the ATEM switcher does not recognize it as an audio
source (like when connecting a digital camera) and does not receive or
indicate any audio input.

Note:

But when I use the very same computer, same HDMI cable, same video with
a cheap chinese portable LCD screen with speakers (i.e. pull the cable
from the ATEM and plug it into the screen) it immediately starts playing
both video and audio. So there is evidence that the ubuntu notebook
definitely passes it's sound to HDMI and there's really an audio signal
on the HDMI.

I've opened a bug at Blackmagic Design, and got their reply that they
can't help and have never heard of such a problem before. Their guess is
that the linux notebook is not setting EDID configuration correctly and
thus not recognized by the ATEM, while the cheap LCD screen propably
does not care about EDID and just plays everything, therefore a wrong
EDID information would not matter.

Although I have decades of experience with Linux, I am not too familiar
with details of HDMI and the internals of the X11 driver, so I'm not
sure where to start debugging, not even, whether this is a problem of
Xorg/X11 or pulseaudio.


I've checked this with another notebook with much more recent (intel)
hardware, which offers dozens of HDMI audio options in the pavucontrol
selection menu, but same problem: Video works, but the ATEM does not
recognize it as a audio source.


Blackmagic Design (they're good in Windows and MacOS, but not Linux) 
recommended to use an edid manager, whatever this means.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: LXQt
Date: Thu Jan  7 13:16:26 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0742]
InstallationDate: Installed on 2020-05-16 (235 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 04f2:b336 Chicony Electronics Co., Ltd 
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer AO756
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=a69345e2-b61e-4d25-baab-b23f75273af6 ro quiet 
cryptdevice=UUID=d132b97b-f47a-4432-88b5-42aca187b9ff:luks-d132b97b-f47a-4432-88b5-42aca187b9ff
 root=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff 
resume=/dev/mapper/luks-d132b97b-f47a-4432-88b5-42aca187b9ff splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2012
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Mimic
dmi.board.vendor: Acer
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.05
dmi.modalias: 
dmi:bvnAcer:bvrV1.05:bd07/19/2012:svnAcer:pnAO756:pvrV1.05:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV1.05:
dmi.product.family: Type1Family
dmi.product.name: AO756
dmi.product.sku: Type1Sku0
dmi.product.version: V1.05
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

-- 
You received this bug 

[Touch-packages] [Bug 1863447] [NEW] openssh outdated by 8.2

2020-02-15 Thread Hadmut Danisch
Public bug reported:

Hi,

yeah, it's not yet a bug, but it will become a (security) bug within
lifetime of 20.04 if not 'fixed'.

Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream the
version 8.2 has just been released:

https://lists.mindrot.org/pipermail/openssh-unix-
announce/2020-February/000138.html

It comes with important security updates, e.g. not accepting SHA-1 for
key generation/signature anymore, and using FIDO2/U2F-tokens as a second
factor. Especially the latter significantly improves security and helps
against stealing keys and hijacking machines.

It would be important (and nice) to have these improvements of security
in Ubuntu 20.04.


It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

Thanks

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

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

Title:
  openssh outdated by 8.2

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi,

  yeah, it's not yet a bug, but it will become a (security) bug within
  lifetime of 20.04 if not 'fixed'.

  Currently openssh for Ubuntu 20.04 is still on 8.1p1, while upstream
  the version 8.2 has just been released:

  https://lists.mindrot.org/pipermail/openssh-unix-
  announce/2020-February/000138.html

  It comes with important security updates, e.g. not accepting SHA-1 for
  key generation/signature anymore, and using FIDO2/U2F-tokens as a
  second factor. Especially the latter significantly improves security
  and helps against stealing keys and hijacking machines.

  It would be important (and nice) to have these improvements of
  security in Ubuntu 20.04.

  
  It might not yet be seen as a security vulnerability, but it will probably 
become one soon. 

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863447/+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 1845627] Re: Network Manager doesn't deal with one time passwords for vpn connections

2019-09-27 Thread Hadmut Danisch
Network-Manager just sabotaged my VPN connection.

It used the (expired one-time-)password it stored in the keyring several
times again to try to login, until the server blocked the account due to
too many login failures.

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

Title:
  Network Manager doesn't deal with one time passwords for vpn
  connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  when configuring a VPN connection (openvpn) with the Network-Manager
  applet (LXDE) even when leaving the password empty Network Manager
  insists on putting the password into the keyring and to reuse it, even
  if this does not make sense and causes an error message on the server
  side, if it's a one-time-password (state of the art).

  NM needs a One-Time-Password-Option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1845627/+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 1845627] [NEW] Network Manager doesn't deal with one time passwords for vpn connections

2019-09-27 Thread Hadmut Danisch
Public bug reported:

Hi,

when configuring a VPN connection (openvpn) with the Network-Manager
applet (LXDE) even when leaving the password empty Network Manager
insists on putting the password into the keyring and to reuse it, even
if this does not make sense and causes an error message on the server
side, if it's a one-time-password (state of the art).

NM needs a One-Time-Password-Option.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network Manager doesn't deal with one time passwords for vpn
  connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  when configuring a VPN connection (openvpn) with the Network-Manager
  applet (LXDE) even when leaving the password empty Network Manager
  insists on putting the password into the keyring and to reuse it, even
  if this does not make sense and causes an error message on the server
  side, if it's a one-time-password (state of the art).

  NM needs a One-Time-Password-Option.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1845627/+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 1841798] [NEW] rsyslog debian build scripts ignoring rabbitmq module

2019-08-28 Thread Hadmut Danisch
Public bug reported:

Hi,

rsyslog comes with a rabbitmq output module included in the source, but
although the debian build scripts do create lots of packages and
modules, they do not create the rabbitmq module. See

https://www.rsyslog.com/doc/v8-stable/configuration/modules/omrabbitmq.html

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: rsyslog 8.32.0-1ubuntu4
ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
Uname: Linux 4.15.0-55-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Aug 28 17:03:01 2019
InstallationDate: Installed on 2018-04-30 (485 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: rsyslog (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 rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1841798

Title:
  rsyslog  debian build scripts ignoring rabbitmq module

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Hi,

  rsyslog comes with a rabbitmq output module included in the source,
  but although the debian build scripts do create lots of packages and
  modules, they do not create the rabbitmq module. See

  https://www.rsyslog.com/doc/v8-stable/configuration/modules/omrabbitmq.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rsyslog 8.32.0-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
  Uname: Linux 4.15.0-55-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 28 17:03:01 2019
  InstallationDate: Installed on 2018-04-30 (485 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1841798/+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 1830538] [NEW] Can't get HIDP connection info

2019-05-26 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in keyboard
emulation mode) with a USB bluetooth dongle in an 18.04 machine, which
used to work some months ago.

Now I can still pair them, the ubuntu machine sees the devices and lists
as paired, but can't connect with human interface device service (HID).
/var/log/syslog says

May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info
May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange (52)

Since the scanner and the usb dongle are unchanged, it must be a problem
of the ubuntu machine.

regards

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun May 26 14:48:12 2019
InstallationDate: Installed on 2018-06-09 (350 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3400 acl:0 sco:0 events:192 errors:0
TX bytes:5012 acl:0 sco:0 commands:142 errors:0
mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1830538

Title:
  Can't get HIDP connection info

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  I'm trying to use a Teemi TMSL-50 bluetooth barcode scanner (in
  keyboard emulation mode) with a USB bluetooth dongle in an 18.04
  machine, which used to work some months ago.

  Now I can still pair them, the ubuntu machine sees the devices and
  lists as paired, but can't connect with human interface device service
  (HID). /var/log/syslog says

  May 26 14:44:49 machine1 bluetoothd[1272]: Can't get HIDP connection info
  May 26 14:44:51 machine1 bluetoothd[1272]: connect error: Invalid exchange 
(52)

  Since the scanner and the usb dongle are unchanged, it must be a
  problem of the ubuntu machine.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun May 26 14:48:12 2019
  InstallationDate: Installed on 2018-06-09 (350 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:3400 acl:0 sco:0 events:192 errors:0
TX bytes:5012 acl:0 

[Touch-packages] [Bug 1830537] [NEW] missing max_match_rules_per_connection

2019-05-26 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm currently trying to debug why my Bluetooth Barcode scanner
(emulating a keyboard) with a USB bluetooth dongle does not work anymore
with my 18.04, can't connect it anoymore (it used to work at lease
occasionally months ago.) It pairs, but can't be connected as a HID.

One of the problems was that error message in /var/log/syslog:


Connection ":1.182" is not allowed to add more match rules (increase
limits in configuration file if required;
max_match_rules_per_connection=2048)


After adding 

  1024
  2048

to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf

at least this error message vanished (while others persist, still does
not work).

However, this should be in /etc/dbus-1/system.d/bluetooth.conf as
delivered from the package and not require the user to debug and change.

regards

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun May 26 14:37:28 2019
InstallationDate: Installed on 2018-06-09 (350 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:13  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:2128 acl:0 sco:0 events:126 errors:0
TX bytes:4712 acl:0 sco:0 commands:106 errors:0
mtime.conffile..etc.dbus-1.system.d.bluetooth.conf: 2019-05-26T14:29:51.468868

** Affects: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1830537

Title:
  missing max_match_rules_per_connection

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  I'm currently trying to debug why my Bluetooth Barcode scanner
  (emulating a keyboard) with a USB bluetooth dongle does not work
  anymore with my 18.04, can't connect it anoymore (it used to work at
  lease occasionally months ago.) It pairs, but can't be connected as a
  HID.

  One of the problems was that error message in /var/log/syslog:


  Connection ":1.182" is not allowed to add more match rules (increase
  limits in configuration file if required;
  max_match_rules_per_connection=2048)

  
  After adding 

1024
2048

  to the busconfig struct in /etc/dbus-1/system.d/bluetooth.conf

  at least this error message vanished (while others persist, still does
  not work).

  However, this should be in /etc/dbus-1/system.d/bluetooth.conf as
  delivered from the package and not require the user to debug and
  change.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun May 26 14:37:28 2019
  InstallationDate: Installed on 2018-06-09 (350 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic 
root=UUID=a3f06afa-8405-4064-8044-0a9e1b4c19c8 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 1825331] Re: apparmor chromium profile blocks yubikeys

2019-04-25 Thread Hadmut Danisch
That's a long list of EPERMs in strace and mostly useless by itself,
since chrome make use of nonblocking/asynchronous IO, so you always have
to look for the syscall that had caused the EPERM. A full trace is
rather huge.


In case you have a yubikey (not just a regular u2f oder blue yubikey, they 
don't show the problem) simply do something like


strace -s 80 -f -o chromiumyubitrace chromium-browser --temp-profile
https://demo.yubico.com/u2f

** Attachment added: "chromium_yubikey_EPERM.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+attachment/5258943/+files/chromium_yubikey_EPERM.txt

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

Title:
  apparmor chromium profile blocks yubikeys

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  some months ago (can't give a precise date) I could use all my pure
  u2f tokens, as well as Yubikey tokens with mixed apps (yubikey 4,
  yubikey neo) pretty well with chromium browser as u2f tokens.

  For some months now and since an update of the chromium-browser in
  18.04, it was working with pure u2f tokens (e.g. the blue yubikeys,
  FIDO u2f token,...), but not with regular yubikeys anymore, although
  command line tools like u2f-host worked pretty well.

  I checked the kernel messages and did not find any apparmor deny
  message or other reasons. Furthermore, the apparmor profile for
  usr.bin.chromium-browser was in complain mode only.

  Now I did again some debugging and found that the problem is gone
  after

  
  aa-disable usr.bin.chromium-browser

  
  Although the profile was in complain mode and dmesg did not show any 
forbidden actions, the strace showed some EPERM (Operation not permitted) 
errors, that's why I tried to disable aa. 

  Interestingly, this problem does not affect regular u2f tokens, just
  the yubikeys with additional functions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor-profiles 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Apr 18 11:14:22 2019
  InstallationDate: Installed on 2018-04-30 (352 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=5dca854b-2558-44a1-918d-c8380934754d ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+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 1825331] [NEW] apparmor chromium profile blocks yubikeys

2019-04-18 Thread Hadmut Danisch
Public bug reported:

Hi,

some months ago (can't give a precise date) I could use all my pure u2f
tokens, as well as Yubikey tokens with mixed apps (yubikey 4, yubikey
neo) pretty well with chromium browser as u2f tokens.

For some months now and since an update of the chromium-browser in
18.04, it was working with pure u2f tokens (e.g. the blue yubikeys, FIDO
u2f token,...), but not with regular yubikeys anymore, although command
line tools like u2f-host worked pretty well.

I checked the kernel messages and did not find any apparmor deny message
or other reasons. Furthermore, the apparmor profile for usr.bin
.chromium-browser was in complain mode only.

Now I did again some debugging and found that the problem is gone after


aa-disable usr.bin.chromium-browser


Although the profile was in complain mode and dmesg did not show any forbidden 
actions, the strace showed some EPERM (Operation not permitted) errors, that's 
why I tried to disable aa. 

Interestingly, this problem does not affect regular u2f tokens, just the
yubikeys with additional functions.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apparmor-profiles 2.12-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Apr 18 11:14:22 2019
InstallationDate: Installed on 2018-04-30 (352 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=5dca854b-2558-44a1-918d-c8380934754d ro nosplash
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apparmor (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 apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1825331

Title:
  apparmor chromium profile blocks yubikeys

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  some months ago (can't give a precise date) I could use all my pure
  u2f tokens, as well as Yubikey tokens with mixed apps (yubikey 4,
  yubikey neo) pretty well with chromium browser as u2f tokens.

  For some months now and since an update of the chromium-browser in
  18.04, it was working with pure u2f tokens (e.g. the blue yubikeys,
  FIDO u2f token,...), but not with regular yubikeys anymore, although
  command line tools like u2f-host worked pretty well.

  I checked the kernel messages and did not find any apparmor deny
  message or other reasons. Furthermore, the apparmor profile for
  usr.bin.chromium-browser was in complain mode only.

  Now I did again some debugging and found that the problem is gone
  after

  
  aa-disable usr.bin.chromium-browser

  
  Although the profile was in complain mode and dmesg did not show any 
forbidden actions, the strace showed some EPERM (Operation not permitted) 
errors, that's why I tried to disable aa. 

  Interestingly, this problem does not affect regular u2f tokens, just
  the yubikeys with additional functions.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apparmor-profiles 2.12-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
  Uname: Linux 4.15.0-47-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Apr 18 11:14:22 2019
  InstallationDate: Installed on 2018-04-30 (352 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic 
root=UUID=5dca854b-2558-44a1-918d-c8380934754d ro nosplash
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1825331/+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 1665695] Re: OpenSSH PKCS#11 interface does not support ECC.

2019-04-16 Thread Hadmut Danisch
As mentioned in the upstream bug, they plan to add support in openssh
8.0.

But I guess 18.04 won't get the upgrade from openssh 7.x to 8.0.

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

Title:
  OpenSSH PKCS#11 interface does not support ECC.

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged

Bug description:
  OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard

  ssh-keygen -v -D /usr/lib/libeTPkcs11.so 
  debug1: manufacturerID  cryptokiVersion 2.20 
libraryDescription  libraryVersion 9.1
  debug1: label  manufacturerID  model  
serial <> flags 0x60d
  C_GetAttributeValue failed: 18
  debug1: X509_get_pubkey failed or no rsa
  debug1: X509_get_pubkey failed or no rsa
  debug1: X509_get_pubkey failed or no rsa
  no keys
  cannot read public key from pkcs11

  pkcs11-tool --module /usr/lib/libeTPkcs11.so -O
  ...
  Public Key Object; EC  EC_POINT 256 bits
EC_POINT:   
04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc
EC_PARAMS:  06082a8648ce3d030107
label:  TestECCpair
Usage:  encrypt, verify, wrap

  
  There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474
  Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728

  release: Ubuntu 16.04.2 LTS
  openssh version: 7.2p2-4ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1665695/+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 1812567] Re: Internal speakers not working after crash reboot

2019-01-20 Thread Hadmut Danisch
** Attachment added: "alsa-info output"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1812567/+attachment/5230734/+files/alsa-info.txt.mql2KR8jRa

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

Title:
  Internal speakers not working after crash reboot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi,
  I have a AIO computer with builtin analog speakers and headphone plug, both 
working for years, also under 18.04, after countless reboots. 

  Now I had a hard reboot after the machine had crashed.

  Now the speakers remain silent. Plugged in headphones still work.

  - I've checked that the speakears are not muted and the volume is
  between 50 and 100

  - I've checked alsamixer and pavucontrol. The show healthy volumes,
  not muted, speakers selected, and pavucontrol is even showing a moving
  indicator for the sound level. I did not find any error message.

  As I said, headphones work well, but the builtin speakers are dead.

  Some parameter must be changed, but I don't find what.

  See logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   hadmut17547 F...m pulseaudio
   /dev/snd/pcmC0D0p:   hadmut17547 F...m pulseaudio
   /dev/snd/controlC0:  hadmut17547 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 20 16:19:55 2019
  InstallationDate: Installed on 2018-06-09 (224 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1812567/+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 1812567] Re: Internal speakers not working after crash reboot

2019-01-20 Thread Hadmut Danisch
** Attachment added: "pulseaudio verbose output"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1812567/+attachment/5230733/+files/pulseverbose.log

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

Title:
  Internal speakers not working after crash reboot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi,
  I have a AIO computer with builtin analog speakers and headphone plug, both 
working for years, also under 18.04, after countless reboots. 

  Now I had a hard reboot after the machine had crashed.

  Now the speakers remain silent. Plugged in headphones still work.

  - I've checked that the speakears are not muted and the volume is
  between 50 and 100

  - I've checked alsamixer and pavucontrol. The show healthy volumes,
  not muted, speakers selected, and pavucontrol is even showing a moving
  indicator for the sound level. I did not find any error message.

  As I said, headphones work well, but the builtin speakers are dead.

  Some parameter must be changed, but I don't find what.

  See logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   hadmut17547 F...m pulseaudio
   /dev/snd/pcmC0D0p:   hadmut17547 F...m pulseaudio
   /dev/snd/controlC0:  hadmut17547 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 20 16:19:55 2019
  InstallationDate: Installed on 2018-06-09 (224 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1812567/+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 1812567] [NEW] Internal speakers not working after crash reboot

2019-01-20 Thread Hadmut Danisch
Public bug reported:

Hi,
I have a AIO computer with builtin analog speakers and headphone plug, both 
working for years, also under 18.04, after countless reboots. 

Now I had a hard reboot after the machine had crashed.

Now the speakers remain silent. Plugged in headphones still work.

- I've checked that the speakears are not muted and the volume is
between 50 and 100

- I've checked alsamixer and pavucontrol. The show healthy volumes, not
muted, speakers selected, and pavucontrol is even showing a moving
indicator for the sound level. I did not find any error message.

As I said, headphones work well, but the builtin speakers are dead.

Some parameter must be changed, but I don't find what.

See logs attached.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0c:   hadmut17547 F...m pulseaudio
 /dev/snd/pcmC0D0p:   hadmut17547 F...m pulseaudio
 /dev/snd/controlC0:  hadmut17547 F pulseaudio
CurrentDesktop: XFCE
Date: Sun Jan 20 16:19:55 2019
InstallationDate: Installed on 2018-06-09 (224 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

** Affects: pulseaudio (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 pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1812567

Title:
  Internal speakers not working after crash reboot

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hi,
  I have a AIO computer with builtin analog speakers and headphone plug, both 
working for years, also under 18.04, after countless reboots. 

  Now I had a hard reboot after the machine had crashed.

  Now the speakers remain silent. Plugged in headphones still work.

  - I've checked that the speakears are not muted and the volume is
  between 50 and 100

  - I've checked alsamixer and pavucontrol. The show healthy volumes,
  not muted, speakers selected, and pavucontrol is even showing a moving
  indicator for the sound level. I did not find any error message.

  As I said, headphones work well, but the builtin speakers are dead.

  Some parameter must be changed, but I don't find what.

  See logs attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   hadmut17547 F...m pulseaudio
   /dev/snd/pcmC0D0p:   hadmut17547 F...m pulseaudio
   /dev/snd/controlC0:  hadmut17547 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 20 16:19:55 2019
  InstallationDate: Installed on 2018-06-09 (224 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

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

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

[Touch-packages] [Bug 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Hadmut Danisch
dnsmasq _after_ networking?

Isn't it part of networking and should be running and ready for other
services depending on networking?


(my guess is that Ubuntu has never defined the targets very precisely. it 
should distinguish between low level /interface level configuration and 
networking services.)

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-19 Thread Hadmut Danisch
setting optional: false   does not solve the problem, a systemctl
restart dnsmasq is still required.

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq started too early, not getting all interfaces

2018-06-15 Thread Hadmut Danisch
So it is not possible to have an interface as optional (for other
reasons beyond that example) and still have a dnsmasq running for it?

In former versions of ubuntu I had my bridges (some containing usb
ethernet interfaces to bridge virtual with physical machines) configured
in /etc/network/if-up.d, and started separate dnsmasq instances for
every single one of these bridges.

Now there is no regular way to start a daemon like dnsmasq through ifup-
scripts, since netplan does not support them. Some people try to
workaround that problem with udev clauses, starting systemd services,
but then it's overcomplicated and error prone.

So what is the offical way to have services like dnsmasq run for
optional interfaces under 18.04?


"Don't use optional" is a workaround, not a solution to the problem. If there 
is no ifup-script anymore, then how are services to be started, once the 
interface is up (late or just sometimes)?

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  Incomplete
Status in netplan.io package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq started too early, not getting all ports

2018-06-15 Thread Hadmut Danisch
** Summary changed:

- dnsmasq startet too early, not getting all ports
+ dnsmasq started too early, not getting all ports

** Summary changed:

- dnsmasq started too early, not getting all ports
+ dnsmasq started too early, not getting all interfaces

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

Title:
  dnsmasq started too early, not getting all interfaces

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq startet too early, not getting all ports

2018-06-15 Thread Hadmut Danisch
** Attachment added: "dnsmasq parameters for virtual lan"
   
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+attachment/5152990/+files/vlan0

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

Title:
  dnsmasq startet too early, not getting all ports

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] Re: dnsmasq startet too early, not getting all ports

2018-06-15 Thread Hadmut Danisch
** Attachment added: "netplan example"
   
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+attachment/5152989/+files/60-vlan0.yaml

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

Title:
  dnsmasq startet too early, not getting all ports

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1777094] [NEW] dnsmasq startet too early, not getting all ports

2018-06-15 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm still struggling with 18.04 and the move from ifupdown to netplan.

I am running a local virtual linux bridge as a network for several
virtual machines and containers, which is to be serviced with dhcp and
dns by dnsmasq.

Conforming to latest designs from Ubuntu the bridge is now started by
netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

Since there is no ifupdown-scripts anymore, I've configured the default
dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that bridge.


This works only when started manually. 

When booting ubuntu the normal way, the bridge is correctly generated,
and dnsmasq is running, but it does *not* offer DNS for the bridge and
does not occupy its port 53. But just a manual systemctl restart
dnsmasq.service make it run as expected, then everything is fine.

So my guess is that my configuration is correct, but dnsmasq simply
started to early, i.e. before the bridge is created, and thus does not
see the bridge when starting up.

There's something wrong in the dependencies of the startup
configuration.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Jun 15 10:59:43 2018
InstallationDate: Installed on 2018-04-30 (45 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dnsmasq (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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1777094

Title:
  dnsmasq startet too early, not getting all ports

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm still struggling with 18.04 and the move from ifupdown to netplan.

  I am running a local virtual linux bridge as a network for several
  virtual machines and containers, which is to be serviced with dhcp and
  dns by dnsmasq.

  Conforming to latest designs from Ubuntu the bridge is now started by
  netplan and configured in /etc/netplan/60-vlan0.yaml straightforward.

  Since there is no ifupdown-scripts anymore, I've configured the
  default dnsmasq daemon in /etc/dnsmasq.d/vlan0 to offer dhcp for that
  bridge.

  
  This works only when started manually. 

  When booting ubuntu the normal way, the bridge is correctly generated,
  and dnsmasq is running, but it does *not* offer DNS for the bridge and
  does not occupy its port 53. But just a manual systemctl restart
  dnsmasq.service make it run as expected, then everything is fine.

  So my guess is that my configuration is correct, but dnsmasq simply
  started to early, i.e. before the bridge is created, and thus does not
  see the bridge when starting up.

  There's something wrong in the dependencies of the startup
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jun 15 10:59:43 2018
  InstallationDate: Installed on 2018-04-30 (45 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1777094/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-05-14 Thread Hadmut Danisch
Ooops, no, sorry, it works (/tmp/a was missing).

So the kernel is definitely able to mount the file systems, it's just
that ecryptfs-utils and their key management do not work.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-05-14 Thread Hadmut Danisch
Even a direct


mount -t ecryptfs -o 
ecryptfs_check_dev_ruid,ecryptfs_cipher=aes,ecryptfs_key_bytes=16,ecryptfs_unlink_sigs
 /tmp/work /tmp/a   

fails with 
[-2] No such file or directory

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-05-14 Thread Hadmut Danisch
Please keep in mind that ecryptfs-mount-private and
mount.ecryptfs_private are slightly different things.

Since ecryptfs-mount-private is a frontend to the underlying
mount.ecryptfs_private, and this isn't working either (also not under
18.04), it is vital to focus on fixing that.

I found that keyctl shows different things under 16.04 and 18.04 after
doing ecryptfs-add-passphrase.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2018-05-05 Thread Hadmut Danisch
ecryptfs (private mount) still does not work under 18.04.


That's a complete showstopper for the upgrade 16.04->18.04 because access to 
encrypted files becomes impossible or at least troublesome.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1768488] [NEW] dependency problem lightdm -> pam

2018-05-02 Thread Hadmut Danisch
Public bug reported:

Hi,

I've installed Lubuntu 18.04 and found that problem:

the display-manager service complains:

 ● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor 
preset: enabled)
   Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
 Docs: man:lightdm(1)
  Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, 
status=0/SUCCESS)
 Main PID: 1720 (lightdm)
Tasks: 6 (limit: 4915)
   CGroup: /system.slice/lightdm.service
   ├─1720 /usr/sbin/lightdm
   ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
   └─1786 lightdm --session-child 12 19

Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: 
pam_kwallet5.so
Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open 
shared object file: No such file or directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_gnome_keyring.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet.so): 
/lib/security/pam_kwallet.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to dlopen(pam_kwallet5.so): 
/lib/security/pam_kwallet5.so: cannot open shared object file: No such file or 
directory
Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_kwallet5.so
Mai 02 11:36:30 pcdanisch lightdm[1786]: pam_succeed_if(lightdm:auth): 
requirement "user ingroup nopasswdlogin" not met by user "danisch"


It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load pam 
modules which are not installed since there are not dependencies to 
libpam-gnome-keyring  libpam-kwallet4 libpam-kwallet5


If it is not intended to let things run into error message (and possible
further trouble), you should either remove these lines from the config
files or add dependencies to pull in that packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed May  2 12:21:26 2018
InstallationDate: Installed on 2018-04-30 (2 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1768488

Title:
  dependency problem lightdm -> pam

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  I've installed Lubuntu 18.04 and found that problem:

  the display-manager service complains:

   ● lightdm.service - Light Display Manager
 Loaded: loaded (/lib/systemd/system/lightdm.service; indirect; vendor 
preset: enabled)
 Active: active (running) since Wed 2018-05-02 11:36:27 CEST; 1min 22s ago
   Docs: man:lightdm(1)
Process: 1717 ExecStartPre=/bin/sh -c [ "$(basename $(cat 
/etc/X11/default-display-manager 2>/dev/null))" = "lightdm" ] (code=exited, 
status=0/SUCCESS)
   Main PID: 1720 (lightdm)
  Tasks: 6 (limit: 4915)
 CGroup: /system.slice/lightdm.service
 ├─1720 /usr/sbin/lightdm
 ├─1726 /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
 └─1786 lightdm --session-child 12 19

  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM unable to 
dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared 
object file: No such file or directory
  Mai 02 11:36:29 pcdanisch lightdm[1735]: PAM adding faulty module: 
pam_kwallet5.so
  Mai 02 11:36:29 pcdanisch lightdm[1735]: pam_unix(lightdm-greeter:session): 
session opened for user lightdm by (uid=0)
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 
dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open 
shared object file: No such file or directory
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM adding faulty module: 
pam_gnome_keyring.so
  Mai 02 11:36:30 pcdanisch lightdm[1786]: PAM unable to 

[Touch-packages] [Bug 1742123] [NEW] obscure slapd configuration

2018-01-09 Thread Hadmut Danisch
Public bug reported:

Hi,

the openldap server slapd comes with two configuration options, the old
one based on slapd.conf, and a new one based on ldifs.

The debian/ubuntu package performs some obscure magic to generate a ldif
based config in /etc/slapd/slapd.d, but does not provide any hint or
documentation about how to change/adjust it. E.g. if the package was
installed non-interactively through puppet or ansible, it is not obvious
where the root password comes from or how to change it or how to re-
setup.

Furthermore it is a security gap to create something like

dn: dc=buero,dc=danisch,dc=de
objectClass: top
objectClass: dcObject
objectClass: organization
o: buero.danisch.de
dc: buero
structuralObjectClass: organization
entryUUID: 4f765744-85aa-1037-9ee9-1db94ae2a6d4
creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
createTimestamp: 20180104145011Z
entryCSN: 20180104145011.817411Z#00#000#00
modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
modifyTimestamp: 20180104145011Z

dn: cn=admin,dc=buero,dc=danisch,dc=de
objectClass: simpleSecurityObject
objectClass: organizationalRole
cn: admin
description: LDAP administrator
userPassword:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=
structuralObjectClass: organizationalRole
entryUUID: 4f79fd9a-85aa-1037-9eea-1db94ae2a6d4
creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
createTimestamp: 20180104145011Z
entryCSN: 20180104145011.841518Z#00#000#00
modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
modifyTimestamp: 20180104145011Z

and

olcRootDN: cn=admin,dc=buero,dc=danisch,dc=de
olcRootPW:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=


that contains an admin password without me ever having set it or having a 
randomly generated one.

Since I do not see how to cleanly change this with ldapmodify, I do not
see an option to remove this all and restart with an old-style
slapd.conf.


regards

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

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

Title:
  obscure slapd configuration

Status in openldap package in Ubuntu:
  New

Bug description:
  Hi,

  the openldap server slapd comes with two configuration options, the
  old one based on slapd.conf, and a new one based on ldifs.

  The debian/ubuntu package performs some obscure magic to generate a
  ldif based config in /etc/slapd/slapd.d, but does not provide any hint
  or documentation about how to change/adjust it. E.g. if the package
  was installed non-interactively through puppet or ansible, it is not
  obvious where the root password comes from or how to change it or how
  to re-setup.

  Furthermore it is a security gap to create something like

  dn: dc=buero,dc=danisch,dc=de
  objectClass: top
  objectClass: dcObject
  objectClass: organization
  o: buero.danisch.de
  dc: buero
  structuralObjectClass: organization
  entryUUID: 4f765744-85aa-1037-9ee9-1db94ae2a6d4
  creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
  createTimestamp: 20180104145011Z
  entryCSN: 20180104145011.817411Z#00#000#00
  modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
  modifyTimestamp: 20180104145011Z

  dn: cn=admin,dc=buero,dc=danisch,dc=de
  objectClass: simpleSecurityObject
  objectClass: organizationalRole
  cn: admin
  description: LDAP administrator
  userPassword:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=
  structuralObjectClass: organizationalRole
  entryUUID: 4f79fd9a-85aa-1037-9eea-1db94ae2a6d4
  creatorsName: cn=admin,dc=buero,dc=danisch,dc=de
  createTimestamp: 20180104145011Z
  entryCSN: 20180104145011.841518Z#00#000#00
  modifiersName: cn=admin,dc=buero,dc=danisch,dc=de
  modifyTimestamp: 20180104145011Z

  and

  olcRootDN: cn=admin,dc=buero,dc=danisch,dc=de
  olcRootPW:: e1NTSEF9aUlUVXlxNE9ZWFFuZjA1ejhqem0yWnJpY09xaGxBc0Y=

  
  that contains an admin password without me ever having set it or having a 
randomly generated one.

  Since I do not see how to cleanly change this with ldapmodify, I do
  not see an option to remove this all and restart with an old-style
  slapd.conf.

  
  regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1742123/+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 1731211] [NEW] systemd breaks interface configuration due to late resolv.conf

2017-11-09 Thread Hadmut Danisch
Public bug reported:

Hi,

I have configured a linux bridge (vlan0) for virtual machines in
/etc/network/interfaces.d/vlan0. The usual configuration including to
start dnasmasq as a dhcp and dns server for that network.

With 17.10 that fails, systemd can't start networking.service

# systemctl |fgrep networking.service  
● networking.service
loaded failed failedRaise network interfaces   


systemctl status networking.service 
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Thu 2017-11-09 10:16:02 CET; 1h 
35min ago
 Docs: man:interfaces(5)
 Main PID: 1938 (code=exited, status=1/FAILURE)
  CPU: 257ms

Nov 09 10:15:59 pcdanisch systemd[1]: Starting Raise network interfaces...
Nov 09 10:16:01 pcdanisch ifup[1938]: Waiting for vlan0 to get ready (MAXWAIT 
is 2 seconds).
Nov 09 10:16:01 pcdanisch ifup[1938]: Set name-type for VLAN subsystem. Should 
be visible in /proc/net/vlan/config
Nov 09 10:16:01 pcdanisch ifup[1938]: dnsmasq: directory /etc/resolv.conf for 
resolv-file is missing, cannot poll
Nov 09 10:16:01 pcdanisch ifup[1938]: Failed to bring up vlan0.
Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Main process exited, 
code=exited, status=1/FAILURE
Nov 09 10:16:02 pcdanisch systemd[1]: Failed to start Raise network interfaces.
Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Unit entered failed 
state.
Nov 09 10:16:02 pcdanisch systemd[1]: networking.service: Failed with result 
'exit-code'.


# ls -lF /etc/resolv.conf 
lrwxrwxrwx 1 root root 39 Okt 24 11:58 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf


As far as I can see at that time of booting, the /etc/resolv.conf shows into a 
a directory which is not yet created (/run is a tmpfs, thus empty at boot 
time), and I have seen more trouble caused by this, that there is a certain 
amount of time in the boot process, where /etc/resolv.conf is neither absent 
nor readable, but a dangling symlink, causing lots of trouble. 

This construction to have a permanent symlink pointing to nowhere while
booting is broken by design.

Furthermore, it's really difficult to get rid of that filthy systemd
dns. That's really odd stuff.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov  9 11:53:46 2017
InstallationDate: Installed on 2017-10-24 (16 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=c100cc19-4ea7-4c2c-a2ee-10d8ed40c2e7 ro rootflags=subvol=@ nomodeset 
quiet splash
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug artful

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

Title:
  systemd breaks interface configuration due to late resolv.conf

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I have configured a linux bridge (vlan0) for virtual machines in
  /etc/network/interfaces.d/vlan0. The usual configuration including to
  start dnasmasq as a dhcp and dns server for that network.

  With 17.10 that fails, systemd can't start networking.service

  # systemctl |fgrep networking.service  
  ● networking.service  
  loaded failed failedRaise network interfaces   


  systemctl status networking.service 
  ● networking.service - Raise network interfaces
 Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 

[Touch-packages] [Bug 1701875] [NEW] systemd crashing swap partitions

2017-07-02 Thread Hadmut Danisch
Public bug reported:

Hi,

systemd still kills the swap device sometimes.

I typically avoid lvm and prefer the partition scheme like

/dev/sda1   unencrypted boot
/dev/sda2   luks-encrypted swap
/dev/sda3   luks-encrypted /root


and haven an /etc/crypttab like

sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard


Since using systemd it sometimes happens that the system does not boot anymore. 
Analysis shows that for some reason the swap partition (the raw partition 
before encryption) contains just rubbish, and since systemd insists on getting 
this swap device for dependencies and thus never fulfills it's dependencies. 

I have no idea what happens insided that damned systemd, since I did not
found any debugging method to see what systemd does. If /etc/crypttab
contains a swap tag, systemd tries to run mkswap and something goes
wrong every now and then (not always, most of the time it works as
expected).

My current guess is that there is some race condition between the normal
mount and recreating the swap, and it looks as if systemd has
dependencies twice, for the device name (sda2 and sda2_crypt) and the
UUID, maybe two processes are spawned instead of one and interfere.

However, it makes systems unstable and unreliable.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu17
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Jul  2 09:06:42 2017
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic 
root=UUID=4638a5a1-629c-477c-b1df-b370d0181be5 ro rootflags=subvol=@ splash 
quiet
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

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


** Tags: amd64 apport-bug xenial

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

Title:
  systemd crashing swap partitions

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  systemd still kills the swap device sometimes.

  I typically avoid lvm and prefer the partition scheme like

  /dev/sda1   unencrypted boot
  /dev/sda2   luks-encrypted swap
  /dev/sda3   luks-encrypted /root

  
  and haven an /etc/crypttab like

  sda2_crypt UUID=a5b1de14-00e7-46a2-a18a-118af13d0ea7 none luks,swap,discard
  sda3_crypt UUID=9ec0971c-605f-4045-a8e4-57f15c933441 none luks,discard

  
  Since using systemd it sometimes happens that the system does not boot 
anymore. Analysis shows that for some reason the swap partition (the raw 
partition before encryption) contains just rubbish, and since systemd insists 
on getting this swap device for dependencies and thus never fulfills it's 
dependencies. 

  I have no idea what happens insided that damned systemd, since I did
  not found any debugging method to see what systemd does. If
  /etc/crypttab contains a swap tag, systemd tries to run mkswap and
  something goes wrong every now and then (not always, most of the time
  it works as expected).

  My current guess is that there is some race condition between the
  normal mount and recreating the swap, and it looks as if systemd has
  dependencies twice, for the device name (sda2 and sda2_crypt) and the
  UUID, maybe two processes are spawned instead of one and interfere.

  However, it makes systems unstable and unreliable.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu17
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jul  2 09:06:42 2017
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic 

[Touch-packages] [Bug 1688017] [NEW] Connection to bluetooth headsets fails

2017-05-03 Thread Hadmut Danisch
Public bug reported:

Hi,

since upgrading to 17.04 I can't connect to bluetooth headsets anymore.
Headsets are found and listed as devices, but when trying to connect,
there's an error

blueman.bluez.errors.DBusFailedError: Protocol not available...


syslog says:

May  3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
May  3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]
May  3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating 
services: Operation already in progress (114)
May  3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
May  3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0
May  3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
May  3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]


Here someone else reports the same observation:
http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: bluez 5.43-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed May  3 17:12:51 2017
InstallationDate: Installed on 2016-04-22 (376 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
InterestingModules: bnep btusb bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: bluez
UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 4C:BB:58:C1:E9:FA  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:18751 acl:51 sco:0 events:1345 errors:0
TX bytes:27309 acl:48 sco:0 commands:1243 errors:0

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


** Tags: amd64 apport-bug zesty

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

Title:
  Connection to bluetooth headsets fails

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi,

  since upgrading to 17.04 I can't connect to bluetooth headsets
  anymore. Headsets are found and listed as devices, but when trying to
  connect, there's an error

  blueman.bluez.errors.DBusFailedError: Protocol not available...

  
  syslog says:

  May  3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]
  May  3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating 
services: Operation already in progress (114)
  May  3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0
  May  3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]



  Here someone else reports the same observation:
  

[Touch-packages] [Bug 1681832] [NEW] Wrong /dev/hwrng for non-existing generator

2017-04-11 Thread Hadmut Danisch
Public bug reported:

Hi,

just ran into a problem:

I have some software dealing with openssl and some crypto stuff. I
recently extended it to read bytes from /dev/hwrng if it exists, because
the software should run on a Raspberry Pi as well. The Raspi does not
have a clock and usually no user input, thus lack of randomness, but a
hardware random number generator, so it is necessary to use /dev/hwrng
if it exists.

But now the software aborts on regular (intel) PCs, since my regular
Ubuntu PCs get a /dev/hwrng entry as well, which just throws a „no such
device“ error when trying to read.

For some strange reason there is this device entry even if the device is
not present, causing trouble.


/dev/hwrng should exist only if there is really some hardware generator.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: udev 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
Uname: Linux 4.8.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
CustomUdevRuleFiles: 50-usb-hbox.rules 50-net-hbox.rules 70-snap.core.rules
Date: Tue Apr 11 14:17:28 2017
InstallationDate: Installed on 2016-04-22 (353 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-45-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (176 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Wrong /dev/hwrng for non-existing generator

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  just ran into a problem:

  I have some software dealing with openssl and some crypto stuff. I
  recently extended it to read bytes from /dev/hwrng if it exists,
  because the software should run on a Raspberry Pi as well. The Raspi
  does not have a clock and usually no user input, thus lack of
  randomness, but a hardware random number generator, so it is necessary
  to use /dev/hwrng if it exists.

  But now the software aborts on regular (intel) PCs, since my regular
  Ubuntu PCs get a /dev/hwrng entry as well, which just throws a „no
  such device“ error when trying to read.

  For some strange reason there is this device entry even if the device
  is not present, causing trouble.

  
  /dev/hwrng should exist only if there is really some hardware generator.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: udev 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17
  Uname: Linux 4.8.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 50-usb-hbox.rules 50-net-hbox.rules 70-snap.core.rules
  Date: Tue Apr 11 14:17:28 2017
  InstallationDate: Installed on 2016-04-22 (353 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-45-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: systemd
  

[Touch-packages] [Bug 1676820] [NEW] systemd-resolved giving false negatives

2017-03-28 Thread Hadmut Danisch
Public bug reported:

Hi,
I was just debugging why so many of my virtual machines have so much trouble in 
getting DNS responses and found, that the dnsmasq on the host machine, which is 
the DNS resolver for all machines asks the three (!) name servers given in 
/etc/resolv.conf, which is the regular two DNS resolvers from the LAN and 
127.0.0.53 where systemd-resolved is running. 

So every time dnsmasq is asking this systemd-resolved (in about one in
three queries) it happens often, not always, that systemd-resolved is
giving false negatives.


I currently do not see why systemd should bring it's own DNS resolver at all, 
and even worse, force that into /etc/resolv.conf, causing lots of trouble with 
false replies. 

That's just another chapter of the intrusive natur of systemd.

What the hell should such a third nameserver be good for?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Mar 28 12:06:13 2017
InstallationDate: Installed on 2016-04-22 (339 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (162 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  systemd-resolved giving false negatives

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  I was just debugging why so many of my virtual machines have so much trouble 
in getting DNS responses and found, that the dnsmasq on the host machine, which 
is the DNS resolver for all machines asks the three (!) name servers given in 
/etc/resolv.conf, which is the regular two DNS resolvers from the LAN and 
127.0.0.53 where systemd-resolved is running. 

  So every time dnsmasq is asking this systemd-resolved (in about one in
  three queries) it happens often, not always, that systemd-resolved is
  giving false negatives.

  
  I currently do not see why systemd should bring it's own DNS resolver at all, 
and even worse, force that into /etc/resolv.conf, causing lots of trouble with 
false replies. 

  That's just another chapter of the intrusive natur of systemd.

  What the hell should such a third nameserver be good for?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Mar 28 12:06:13 2017
  InstallationDate: Installed on 2016-04-22 (339 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-41-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: systemd
  UpgradeStatus: 

[Touch-packages] [Bug 1675705] [NEW] unknown file system type zfs_member

2017-03-24 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm happy to see that there is some progress about automounting
removable devices with zfs, but when I plug in a pendrive with zfs, I
still get the error message

Error mounting /dev/dm-2 at /media/danisch/sync2: Command-line `mount -t
"zfs_member" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2"
"/media/danisch/sync2"' exited with non-zero exit status 32: mount:
unknown filesystem type 'zfs_member'

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: mount 2.28.2-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 24 10:20:03 2017
InstallationDate: Installed on 2016-04-22 (335 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: util-linux
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (158 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  unknown file system type zfs_member

Status in util-linux package in Ubuntu:
  New

Bug description:
  Hi,

  I'm happy to see that there is some progress about automounting
  removable devices with zfs, but when I plug in a pendrive with zfs, I
  still get the error message

  Error mounting /dev/dm-2 at /media/danisch/sync2: Command-line `mount
  -t "zfs_member" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2"
  "/media/danisch/sync2"' exited with non-zero exit status 32: mount:
  unknown filesystem type 'zfs_member'

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: mount 2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
  Uname: Linux 4.8.0-41-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 24 10:20:03 2017
  InstallationDate: Installed on 2016-04-22 (335 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (158 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1675705/+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 1672321] [NEW] systemd renders its own debug console unusable

2017-03-13 Thread Hadmut Danisch
Public bug reported:

Hi,

I have a problem with some of my ubuntu machines, they are sometimes
stuck in a boot process, issuing "a start job is running..." in an
endless loop.

I have activated systemd's debug console (terminal 9) to find the
problem, but found the debug console as almost useless, since systemd is
blasting this messages to the debug console as well, making it
impossible to use a shell (can't read any output because of that
garbage).

I did not find a way to turn this off.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Mar 13 10:41:18 2017
InstallationDate: Installed on 2016-04-22 (324 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (147 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  systemd renders its own debug console unusable

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I have a problem with some of my ubuntu machines, they are sometimes
  stuck in a boot process, issuing "a start job is running..." in an
  endless loop.

  I have activated systemd's debug console (terminal 9) to find the
  problem, but found the debug console as almost useless, since systemd
  is blasting this messages to the debug console as well, making it
  impossible to use a shell (can't read any output because of that
  garbage).

  I did not find a way to turn this off.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Mar 13 10:41:18 2017
  InstallationDate: Installed on 2016-04-22 (324 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (147 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To 

[Touch-packages] [Bug 1668906] Re: systemd occasionally hangs forever while booting: A start job is running for ...

2017-03-07 Thread Hadmut Danisch
All passwords are already entered, the problem occurs some time after
the passwords have been entered, and as far as I could see on the debug
console, all encrypted devices exist under /dev/mapper, so it does not
seem to be caused by encryption (except for the fact that encryption
generataes long device names as /dev/mapper/crypt... which get
shortened).


My current guess is that it is a problem with the swap device (I'm using 
separate encrypted swap devices on those machines where the problem occurs), 
that systemd somehow tries to clean/format the swap device and something goes 
wrong there. 

And no, the problem is not new, I've already seen this months ago. It
came with 16.04/systemd.

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

Title:
  systemd occasionally hangs forever while booting: A start job is
  running for ...

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* 
happens, that systemd is stuck in booting telling 

  "A start job is running for dev-mapp...ypt.device (5min 40s / no
  limit)" (endless loop, counting the time up)

  (only) rebooting helps, but that's annoying and keeps machines from
  automated booting.


  
  Additional problem one: 
  That damned systemd shortens the output to the terminal line length and 
instead of telling the device name to give a hint where the problems come from 
it just says  dev-mapp...ypt.device


  Additional problem two:
  I've activated systemd's debug shell on Terminal 9 in order to debug the 
problem, but the debug shell is rendered useless by systemd, since it blasts 
it's messages about the problem to tty9 as well, thus making it impossible to 
work there. 


  Additional problem three: 
  These device entries seem to be generated dynamically from fstab/crypttab and 
not exist as files, so it is not even visible, what's the contents of these 
tasks. 

  Additional problem four: 
  I did not find a description of a debugging procedure. 


  So I do not even see how to debug that weird mess. Why on earth has
  ubuntu moved to such a confused heap of undebuggable spaghetti code?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Mar  1 10:18:15 2017
  InstallationDate: Installed on 2016-04-22 (312 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (135 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1668906/+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 1668906] [NEW] systemd occasionally hangs forever while booting: A start job is running for ...

2017-03-01 Thread Hadmut Danisch
Public bug reported:

Hi,
on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* happens, 
that systemd is stuck in booting telling 

"A start job is running for dev-mapp...ypt.device (5min 40s / no limit)"
(endless loop, counting the time up)

(only) rebooting helps, but that's annoying and keeps machines from
automated booting.


Additional problem one: 
That damned systemd shortens the output to the terminal line length and instead 
of telling the device name to give a hint where the problems come from it just 
says  dev-mapp...ypt.device


Additional problem two:
I've activated systemd's debug shell on Terminal 9 in order to debug the 
problem, but the debug shell is rendered useless by systemd, since it blasts 
it's messages about the problem to tty9 as well, thus making it impossible to 
work there. 


Additional problem three: 
These device entries seem to be generated dynamically from fstab/crypttab and 
not exist as files, so it is not even visible, what's the contents of these 
tasks. 

Additional problem four: 
I did not find a description of a debugging procedure. 


So I do not even see how to debug that weird mess. Why on earth has
ubuntu moved to such a confused heap of undebuggable spaghetti code?

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
Uname: Linux 4.8.0-39-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar  1 10:18:15 2017
InstallationDate: Installed on 2016-04-22 (312 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
 Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-39-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: systemd
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (135 days ago)
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: N3150-NUC
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug yakkety

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

Title:
  systemd occasionally hangs forever while booting: A start job is
  running for ...

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  on several of my machines (encrypted, 16.04 and 16.10) it *sometimes* 
happens, that systemd is stuck in booting telling 

  "A start job is running for dev-mapp...ypt.device (5min 40s / no
  limit)" (endless loop, counting the time up)

  (only) rebooting helps, but that's annoying and keeps machines from
  automated booting.


  
  Additional problem one: 
  That damned systemd shortens the output to the terminal line length and 
instead of telling the device name to give a hint where the problems come from 
it just says  dev-mapp...ypt.device


  Additional problem two:
  I've activated systemd's debug shell on Terminal 9 in order to debug the 
problem, but the debug shell is rendered useless by systemd, since it blasts 
it's messages about the problem to tty9 as well, thus making it impossible to 
work there. 


  Additional problem three: 
  These device entries seem to be generated dynamically from fstab/crypttab and 
not exist as files, so it is not even visible, what's the contents of these 
tasks. 

  Additional problem four: 
  I did not find a description of a debugging procedure. 


  So I do not even see how to debug that weird mess. Why on earth has
  ubuntu moved to such a confused heap of undebuggable spaghetti code?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17
  Uname: Linux 4.8.0-39-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  

[Touch-packages] [Bug 1660040] [NEW] old-fashioned ufw structure reduces usability

2017-01-28 Thread Hadmut Danisch
Public bug reported:

Hi,

ufw makes it difficult to deploy firewall rules through management
systems like puppet, ansible or other scripts.

ufw has three points where to put rules in:

before.rules
user.rules
after.rules


the ufw command accepts only a very limited sort of rules, and user.rules 
should not be used to deploy files, since user changes would be overwritten. 

before.rules and after.rules could easily be used for that purpose, but
then the machine is cut from automated updates through apt, since apt
refuses (for good reason) to replace modified files in /etc.


It would be much better to have a directory like /etc/ufw/rules_v4.d ,
to put the old-fashioned three files into 20_before, 50_user and
70_after, and to execute all rules in this directory, thus allowing to
have additional rules in separate files.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ufw 0.35-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: LXDE
Date: Sat Jan 28 16:21:02 2017
PackageArchitecture: all
SourcePackage: ufw
UpgradeStatus: Upgraded to xenial on 2016-04-06 (297 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  old-fashioned ufw structure reduces usability

Status in ufw package in Ubuntu:
  New

Bug description:
  Hi,

  ufw makes it difficult to deploy firewall rules through management
  systems like puppet, ansible or other scripts.

  ufw has three points where to put rules in:

  before.rules
  user.rules
  after.rules

  
  the ufw command accepts only a very limited sort of rules, and user.rules 
should not be used to deploy files, since user changes would be overwritten. 

  before.rules and after.rules could easily be used for that purpose,
  but then the machine is cut from automated updates through apt, since
  apt refuses (for good reason) to replace modified files in /etc.


  It would be much better to have a directory like /etc/ufw/rules_v4.d ,
  to put the old-fashioned three files into 20_before, 50_user and
  70_after, and to execute all rules in this directory, thus allowing to
  have additional rules in separate files.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ufw 0.35-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sat Jan 28 16:21:02 2017
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (297 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1660040/+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 1654624] Re: dhcp apparmor profile complains about lxd client

2017-01-28 Thread Hadmut Danisch
> Which are the perceivable consequences of this bug?

I currently cannot survey the consequences, since I am not familiar with
the recent semantic changes of apparmor (are there any docs? Any hints
to the users about changes? Any release notes?)

For some time now I am spending and wasting lots of time to hunt bugs in
all sorts of software like firefox, chromium, ejabberd, lxd,... which is
all caused by sudden apparmor trouble.


A side effect of all these bugs is that log files (and desktops through 
aa-notify) are flooded with hundres, thousands, millions of log messages, which 
jams a system and makes it impossible to find really important log messages, 
and, btw., can ruin flash memory in SSDs and SD-Cards within short time. 

Why on earth has one backported this pile of bugs into a LTS version?

This rendered Ubuntu so unreliable, that I have to consider to change to
CentOS or something like this for servers in order to get SELinux
instead.

Is there any way to get 16.04 stable again?

BTW: How should I answer the question about the consequences of the bug,
if I don't see any docs about was has changed with apparmor?


** Changed in: isc-dhcp (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  dhcp apparmor profile complains about lxd client

Status in apparmor package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  strange problem recently occured:

  I'm having some ubuntu machines running in LXD (nothing unusual, just
  based on the regular ubuntu LXD images) on a ubuntu host. Worked well
  for some time.

  But now the host generates messages like


  Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
  audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
  namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
  name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
  denied_mask="w" fsuid=165536 ouid=0

  
  in /var/log/kern.log. 

  For some reason the apparmor running on the host interferes with the
  containers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.6
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jan  6 19:19:12 2017
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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 1654624] Re: dhcp apparmor profile complains about lxd client

2017-01-28 Thread Hadmut Danisch
> Removing the LXD task, this is yet another apparmor bug from the apparmor 
> stacking/namespacing change which was backported to Xenial.


Well, that explains a lot. 16.04 was formerly stable but recently began to 
drive me crazy because of so many apparmor problems with almost every major 
daemon or browser, and an aa-notify which just vomates hundreds of messages 
onto the desktop faster than one can click them away. 

I am not an apparmor expert, but was able to deal with it for years, but
suddenly have the problem that adding permissions to the local-files for
local extensions does not solve problems as expected.

I think it is not overestimated to say that this apparmor thing broke
the usability of 16.04.

What in the world was the reason to backport these problems into a
stable release?

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

Title:
  dhcp apparmor profile complains about lxd client

Status in apparmor package in Ubuntu:
  New
Status in isc-dhcp package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  strange problem recently occured:

  I'm having some ubuntu machines running in LXD (nothing unusual, just
  based on the regular ubuntu LXD images) on a ubuntu host. Worked well
  for some time.

  But now the host generates messages like


  Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
  audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
  namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
  name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
  denied_mask="w" fsuid=165536 ouid=0

  
  in /var/log/kern.log. 

  For some reason the apparmor running on the host interferes with the
  containers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.6
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jan  6 19:19:12 2017
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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 1658943] Re: aa-notify blocks desktop with garbage notifications

2017-01-24 Thread Hadmut Danisch
I already have opened separate bugreports for firefox and chromium.
Seems as if some problems can not be fixed since the sandbox model of
chromium allegedly has a higher complexity than apparmor can deal with
and would exceed the capabilities of apparmor.

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

Title:
  aa-notify blocks desktop with garbage notifications

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  aa-notify is highly annoying.

  Unfortunately the aa-armor profiles of firefox and chromium-browser
  are poorly maintained and cause dozens, hundreds, thousands of log
  messages for denied access, in most cases the same message again and
  again.

  aa-notify then throws dozens, hundreds of notification tiles on the
  desktop, sometimes faster than one can click them to go away, thus
  rendering the desktop unusable, making windows invisible.

  It is broken by design to throw unlimited numbers of notification on
  the user interface.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apparmor-notify 2.10.95-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 24 10:26:57 2017
  InstallationDate: Installed on 2016-04-22 (276 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (99 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1658943/+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 1658943] [NEW] aa-notify blocks desktop with garbage notifications

2017-01-24 Thread Hadmut Danisch
Public bug reported:

Hi,

aa-notify is highly annoying.

Unfortunately the aa-armor profiles of firefox and chromium-browser are
poorly maintained and cause dozens, hundreds, thousands of log messages
for denied access, in most cases the same message again and again.

aa-notify then throws dozens, hundreds of notification tiles on the
desktop, sometimes faster than one can click them to go away, thus
rendering the desktop unusable, making windows invisible.

It is broken by design to throw unlimited numbers of notification on the
user interface.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apparmor-notify 2.10.95-4ubuntu5.1
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Jan 24 10:26:57 2017
InstallationDate: Installed on 2016-04-22 (276 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
SourcePackage: apparmor
Syslog:
 
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (99 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  aa-notify blocks desktop with garbage notifications

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  aa-notify is highly annoying.

  Unfortunately the aa-armor profiles of firefox and chromium-browser
  are poorly maintained and cause dozens, hundreds, thousands of log
  messages for denied access, in most cases the same message again and
  again.

  aa-notify then throws dozens, hundreds of notification tiles on the
  desktop, sometimes faster than one can click them to go away, thus
  rendering the desktop unusable, making windows invisible.

  It is broken by design to throw unlimited numbers of notification on
  the user interface.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apparmor-notify 2.10.95-4ubuntu5.1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 24 10:26:57 2017
  InstallationDate: Installed on 2016-04-22 (276 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (99 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1658943/+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 1654624] [NEW] dhcp apparmor profile comlains about lxd client

2017-01-06 Thread Hadmut Danisch
Public bug reported:

Hi,

strange problem recently occured:

I'm having some ubuntu machines running in LXD (nothing unusual, just
based on the regular ubuntu LXD images) on a ubuntu host. Worked well
for some time.

But now the host generates messages like


Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
denied_mask="w" fsuid=165536 ouid=0


in /var/log/kern.log. 

For some reason the apparmor running on the host interferes with the
containers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-client 4.3.3-5ubuntu12.6
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Jan  6 19:19:12 2017
SourcePackage: isc-dhcp
UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  dhcp apparmor profile comlains about lxd client

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi,

  strange problem recently occured:

  I'm having some ubuntu machines running in LXD (nothing unusual, just
  based on the regular ubuntu LXD images) on a ubuntu host. Worked well
  for some time.

  But now the host generates messages like


  Jan  6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400
  audit(1483726625.388:247): apparmor="DENIED" operation="file_perm"
  namespace="root//lxd-rackadmin_" profile="/sbin/dhclient"
  name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w"
  denied_mask="w" fsuid=165536 ouid=0

  
  in /var/log/kern.log. 

  For some reason the apparmor running on the host interferes with the
  containers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu12.6
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Jan  6 19:19:12 2017
  SourcePackage: isc-dhcp
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1654624/+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 1652269] Re: udev script shortcuts ifup-scripts

2016-12-23 Thread Hadmut Danisch
More trouble with that udev script:

Plugging in a USB ethernet dongle into a bridge which lists it as a port
does not work. It takes an additional

ifconfig up

to switch the ethernet interface on.

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

Title:
  udev script shortcuts ifup-scripts

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Hi,

  I just ran into a problem. I've configured a bridge as a virtual lan
  (for lxc, lxd, and these things), but also configured an USB Ethernet
  dongle to be part of the bridge.

  If the dongle is present at boot time or if the dongle is put in while
  the bridge is down, then

  
  /lib/udev/bridge-network-interface  

  
  tries to take the bridge up. Nice. 

  But it does not call ifup, instead it directly calls

  IFACE=$port /etc/network/if-pre-up.d/vlan

  
  This ifup is not aware that the interface is up and still thinks it would be 
down, and all the other settings (up/down-scripts ...) are not executed. Breaks 
functionality (and can be a security problem, since firewall settings my be 
skipped.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bridge-utils 1.5-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:31:43 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2
   libgcc1 1:6.2.0-5ubuntu12
  InstallationDate: Installed on 2016-04-22 (244 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: bridge-utils
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1652269/+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 1652269] [NEW] udev script shortcuts ifup-scripts

2016-12-23 Thread Hadmut Danisch
Public bug reported:

Hi,

I just ran into a problem. I've configured a bridge as a virtual lan
(for lxc, lxd, and these things), but also configured an USB Ethernet
dongle to be part of the bridge.

If the dongle is present at boot time or if the dongle is put in while
the bridge is down, then


/lib/udev/bridge-network-interface  


tries to take the bridge up. Nice. 

But it does not call ifup, instead it directly calls

IFACE=$port /etc/network/if-pre-up.d/vlan


This ifup is not aware that the interface is up and still thinks it would be 
down, and all the other settings (up/down-scripts ...) are not executed. Breaks 
functionality (and can be a security problem, since firewall settings my be 
skipped.)

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: bridge-utils 1.5-9ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
Uname: Linux 4.8.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Dec 23 11:31:43 2016
Dependencies:
 gcc-6-base 6.2.0-5ubuntu12
 libc6 2.24-3ubuntu2
 libgcc1 1:6.2.0-5ubuntu12
InstallationDate: Installed on 2016-04-22 (244 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: bridge-utils
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago)

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug yakkety

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

Title:
  udev script shortcuts ifup-scripts

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  Hi,

  I just ran into a problem. I've configured a bridge as a virtual lan
  (for lxc, lxd, and these things), but also configured an USB Ethernet
  dongle to be part of the bridge.

  If the dongle is present at boot time or if the dongle is put in while
  the bridge is down, then

  
  /lib/udev/bridge-network-interface  

  
  tries to take the bridge up. Nice. 

  But it does not call ifup, instead it directly calls

  IFACE=$port /etc/network/if-pre-up.d/vlan

  
  This ifup is not aware that the interface is up and still thinks it would be 
down, and all the other settings (up/down-scripts ...) are not executed. Breaks 
functionality (and can be a security problem, since firewall settings my be 
skipped.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: bridge-utils 1.5-9ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:31:43 2016
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2
   libgcc1 1:6.2.0-5ubuntu12
  InstallationDate: Installed on 2016-04-22 (244 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: bridge-utils
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (67 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1652269/+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 1652032] [NEW] ambiguous config file

2016-12-22 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm currently hunting some problems caused by some ambiguity in the
dnsmasq config.

There's a directory /etc/dnsmasq.d, where some packages put files with
except-interface=... clauses, telling other instances of dnsmasq to
"Keep your fingers from my interface". Good practice.

But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
commented out, so actually the /etc/dnsmasq.d directory is not read by
default.

Some packages that use dnsmasq therefore give it a --conf-
dir=/etc/dnsmasq.d command line parameter to make it read all those
config snippets.

This causes two problems:

- Not all packages give their dnsmasq this additional parameter, and
therefore not all dnsmasq instances obey those config. E.g.
NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt does
not read it either.


- Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


So it is quite unclear how these things should work together cleanly.
Since the details are left to both the user's arbitrary configuration of
/etc/dnsmasq.conf and every single package maintainer how he would
prefer to use it, there's just a heap of confusion.

In my eyes the best way would be to just use

conf-dir=/etc/dnsmasq.d/,*.conf


in the /etc/dnsmasq.conf and have this as a default, and that's it. 


regards

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Dec 22 12:55:33 2016
InstallationDate: Installed on 2016-04-22 (243 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
PackageArchitecture: all
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  ambiguous config file

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm currently hunting some problems caused by some ambiguity in the
  dnsmasq config.

  There's a directory /etc/dnsmasq.d, where some packages put files with
  except-interface=... clauses, telling other instances of dnsmasq to
  "Keep your fingers from my interface". Good practice.

  But then, conf-dir=/etc/dnsmasq.d clauses in /etc/dnsmasq.conf are
  commented out, so actually the /etc/dnsmasq.d directory is not read by
  default.

  Some packages that use dnsmasq therefore give it a --conf-
  dir=/etc/dnsmasq.d command line parameter to make it read all those
  config snippets.

  This causes two problems:

  - Not all packages give their dnsmasq this additional parameter, and
  therefore not all dnsmasq instances obey those config. E.g.
  NetwerkManager uses it's own /etc/NetworkManager/dnsmasq.d, libvirt
  does not read it either.

  
  - Even those packages that use --conf-dir=/etc/dnsmasq.d do not all read the 
same, since there is an additional parameter telling which files to load or 
ignore, which is used differently by all the packages. 


  So it is quite unclear how these things should work together cleanly.
  Since the details are left to both the user's arbitrary configuration
  of /etc/dnsmasq.conf and every single package maintainer how he would
  prefer to use it, there's just a heap of confusion.

  In my eyes the best way would be to just use

  conf-dir=/etc/dnsmasq.d/,*.conf

  
  in the /etc/dnsmasq.conf and have this as a default, and that's it. 


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: dnsmasq 2.76-4
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Dec 22 12:55:33 2016
  InstallationDate: Installed on 2016-04-22 (243 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to yakkety on 2016-10-17 (66 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1652032/+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 1650827] [NEW] "Failed name lookup - disconnected path"

2016-12-17 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm currently trying to use dovecot in a test scenario, but run into the
problem of a strange malfunction of apparmor.

What I do:

installed packages   dovecot-core   and   dovecot-lmtp
(and of course apparmor)

Then I do (as root)

/usr/lib/dovecot/dovecot-lda -d hadmut 

[Touch-packages] [Bug 1647142] [NEW] usr.bin.chromium-browser terribly outdated

2016-12-04 Thread Hadmut Danisch
Public bug reported:

Hi,

when using the Chromium Browser, the screen (LXDE) drowns in warning
messages because of heaps of apparmor profile violations. Unusable
without intense manual modifications.

For some strange reason /etc/apparmor.d/usr.bin.chromium-browser is over
a year old

-rw-r--r-- 1 root root 8243 Sep  3  2015 usr.bin.chromium-browser


and part of the apparmor-profiles and not of the chromium-package (where it 
would belong to). 

It seems as if the chromium browser is continuously developed and re-
compiled with new library versions, while the apparmor profile is frozen
and noone takes care about, thus things are diverging more and more.

IMHO the profile should be

a) part of the chromium browser package
b) maintained (tested) by the same package maintainers

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.5
ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
Uname: Linux 4.4.0-51-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Dec  4 12:44:25 2016
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic 
root=UUID=3e286927-f1b6-4954-8b0d-7cf23484309f ro rootflags=subvol=@ splash 
quiet vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: Upgraded to xenial on 2016-04-06 (242 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  usr.bin.chromium-browser terribly outdated

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi,

  when using the Chromium Browser, the screen (LXDE) drowns in warning
  messages because of heaps of apparmor profile violations. Unusable
  without intense manual modifications.

  For some strange reason /etc/apparmor.d/usr.bin.chromium-browser is
  over a year old

  -rw-r--r-- 1 root root 8243 Sep  3  2015 usr.bin.chromium-browser

  
  and part of the apparmor-profiles and not of the chromium-package (where it 
would belong to). 

  It seems as if the chromium browser is continuously developed and re-
  compiled with new library versions, while the apparmor profile is
  frozen and noone takes care about, thus things are diverging more and
  more.

  IMHO the profile should be

  a) part of the chromium browser package
  b) maintained (tested) by the same package maintainers

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apparmor-profiles 2.10.95-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-51.72-generic 4.4.30
  Uname: Linux 4.4.0-51-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Dec  4 12:44:25 2016
  PackageArchitecture: all
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-51-generic 
root=UUID=3e286927-f1b6-4954-8b0d-7cf23484309f ro rootflags=subvol=@ splash 
quiet vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (242 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1647142/+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 1639897] Re: lxc / lxc1 uninstallable

2016-11-07 Thread Hadmut Danisch
Strange side effect:

Launchpad didn't let me report the bug against the package lxc1 because
launchpad insists that there is no lxc1 package.

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

Title:
  lxc / lxc1 uninstallable

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi,

  I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc
  during upgrade, because the upgrade process removed it.

  Now I can't install lxc due to broken dependencies/incomplete package
  upload:


   lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not
  going to be installed


   lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 
2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed
  Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not 
going to be installed
  Recommends: libpam-cgfs but it is not going to be installed
  Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is 
not going to be installed

  
  liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1).

  python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but
  2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed

  
  Obviously someone has rendered lxc uninstallable by putting an incomplete set 
of packages in the 16.04 repository.

  Please fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639897/+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 1639897] [NEW] lxc / lxc1 uninstallable

2016-11-07 Thread Hadmut Danisch
Public bug reported:

Hi,

I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc
during upgrade, because the upgrade process removed it.

Now I can't install lxc due to broken dependencies/incomplete package
upload:


 lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not
going to be installed


 lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 
2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed
Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not 
going to be installed
Recommends: libpam-cgfs but it is not going to be installed
Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is 
not going to be installed


liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1).

python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but
2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed


Obviously someone has rendered lxc uninstallable by putting an incomplete set 
of packages in the 16.04 repository.

Please fix.

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

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

Title:
  lxc / lxc1 uninstallable

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi,

  I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc
  during upgrade, because the upgrade process removed it.

  Now I can't install lxc due to broken dependencies/incomplete package
  upload:


   lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not
  going to be installed


   lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 
2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed
  Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not 
going to be installed
  Recommends: libpam-cgfs but it is not going to be installed
  Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is 
not going to be installed

  
  liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1).

  python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but
  2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed

  
  Obviously someone has rendered lxc uninstallable by putting an incomplete set 
of packages in the 16.04 repository.

  Please fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639897/+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 1611140] [NEW] --dhcp-boot option differs from man page

2016-08-08 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm running an Ubuntu PXE server with dnsmasq.

Manpage says
-M, --dhcp-boot=[tag:,],[[,|]]
  (IPv4  only) Set BOOTP options to be returned by the DHCP server. 
Server name and address are optional: if not provided, the name is left empty, 
and the address set to the address of the machine running dnsmasq. 


However, I found PXE clients ot be stuck after loading pxelinux.0.

Analysis showed that the DHCP offers from dnsmasq do not conform to the
man page, if no server is given. The "Next Server IP Adress" field is
then set to 0.0.0.0 instead of the dnsmasq's own IP address.

Which is odd, since the PXE server itself gets his IP-address
dynamically, thus requires the config file to be changed after every
boot.

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dnsmasq-base 2.75-1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Aug  9 00:50:05 2016
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  --dhcp-boot option differs from man page

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Hi,

  I'm running an Ubuntu PXE server with dnsmasq.

  Manpage says
  -M, --dhcp-boot=[tag:,],[[,|]]
(IPv4  only) Set BOOTP options to be returned by the DHCP 
server. Server name and address are optional: if not provided, the name is left 
empty, and the address set to the address of the machine running dnsmasq. 


  However, I found PXE clients ot be stuck after loading pxelinux.0.

  Analysis showed that the DHCP offers from dnsmasq do not conform to
  the man page, if no server is given. The "Next Server IP Adress" field
  is then set to 0.0.0.0 instead of the dnsmasq's own IP address.

  Which is odd, since the PXE server itself gets his IP-address
  dynamically, thus requires the config file to be changed after every
  boot.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug  9 00:50:05 2016
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1611140/+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 1605160] Re: kernel autoremove not working

2016-07-21 Thread Hadmut Danisch
Definitely no manual interaction, fresh install recently.

# apt-mark showauto ^linux-image-.*
linux-image-4.4.0-21-generic
linux-image-4.4.0-22-generic
linux-image-4.4.0-24-generic
linux-image-4.4.0-28-generic
linux-image-4.4.0-31-generic
linux-image-extra-4.4.0-28-generic
linux-image-extra-4.4.0-31-generic
linux-image-generic


# apt-mark showmanual ^linux-image-.*

(no output..)





# cat /etc/apt/apt.conf.d/01autoremove-kernels
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
   "^linux-image-4\.4\.0-28-generic$";
   "^linux-image-4\.4\.0-31-generic$";
   "^linux-headers-4\.4\.0-28-generic$";
   "^linux-headers-4\.4\.0-31-generic$";
   "^linux-image-extra-4\.4\.0-28-generic$";
   "^linux-image-extra-4\.4\.0-31-generic$";
   "^linux-signed-image-4\.4\.0-28-generic$";
   "^linux-signed-image-4\.4\.0-31-generic$";
   "^kfreebsd-image-4\.4\.0-28-generic$";
   "^kfreebsd-image-4\.4\.0-31-generic$";
   "^kfreebsd-headers-4\.4\.0-28-generic$";
   "^kfreebsd-headers-4\.4\.0-31-generic$";
   "^gnumach-image-4\.4\.0-28-generic$";
   "^gnumach-image-4\.4\.0-31-generic$";
   "^.*-modules-4\.4\.0-28-generic$";
   "^.*-modules-4\.4\.0-31-generic$";
   "^.*-kernel-4\.4\.0-28-generic$";
   "^.*-kernel-4\.4\.0-31-generic$";
   "^linux-backports-modules-.*-4\.4\.0-28-generic$";
   "^linux-backports-modules-.*-4\.4\.0-31-generic$";
   "^linux-tools-4\.4\.0-28-generic$";
   "^linux-tools-4\.4\.0-31-generic$";
};
/* Debug information:
# dpkg list:
ii  linux-image-4.4.0-21-generic  4.4.0-21.37   
  amd64Linux kernel image for version 4.4.0 
on 64 bit x86 SMP
ii  linux-image-4.4.0-22-generic  4.4.0-22.40   
  amd64Linux kernel image for version 4.4.0 
on 64 bit x86 SMP
ii  linux-image-4.4.0-24-generic  4.4.0-24.43   
  amd64Linux kernel image for version 4.4.0 
on 64 bit x86 SMP
ii  linux-image-4.4.0-28-generic  4.4.0-28.47   
  amd64Linux kernel image for version 4.4.0 
on 64 bit x86 SMP
ii  linux-image-4.4.0-31-generic  4.4.0-31.50   
  amd64Linux kernel image for version 4.4.0 
on 64 bit x86 SMP
rc  linux-image-extra-4.4.0-21-generic4.4.0-21.37   
  amd64Linux kernel extra modules for 
version 4.4.0 on 64 bit x86 SMP
rc  linux-image-extra-4.4.0-22-generic4.4.0-22.40   
  amd64Linux kernel extra modules for 
version 4.4.0 on 64 bit x86 SMP
rc  linux-image-extra-4.4.0-24-generic4.4.0-24.43   
  amd64Linux kernel extra modules for 
version 4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-28-generic4.4.0-28.47   
  amd64Linux kernel extra modules for 
version 4.4.0 on 64 bit x86 SMP
ii  linux-image-extra-4.4.0-31-generic4.4.0-31.50   
  amd64Linux kernel extra modules for 
version 4.4.0 on 64 bit x86 SMP
ii  linux-image-generic   4.4.0.31.33   
  amd64Generic Linux kernel image
# list of installed kernel packages:
4.4.0-21-generic 4.4.0-21.37
4.4.0-22-generic 4.4.0-22.40
4.4.0-24-generic 4.4.0-24.43
4.4.0-28-generic 4.4.0-28.47
4.4.0-31-generic 4.4.0-31.50
# list of different kernel versions:
4.4.0-31.50
4.4.0-28.47
4.4.0-24.43
4.4.0-22.40
4.4.0-21.37
# Installing kernel:  ()
# Running kernel: 4.4.0-31.50 (4.4.0-31-generic)
# Last kernel: 4.4.0-31.50
# Previous kernel: 4.4.0-28.47
# Kernel versions list to keep:
4.4.0-28.47
4.4.0-31.50
# Kernel packages (version part) to protect:
4\.4\.0-28-generic
4\.4\.0-31-generic
*/

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

Title:
  kernel autoremove not working

Status in apt package in Ubuntu:
  New

Bug description:
  On one 16.04 machine I have 5 4.4.0-kernels in /boot now (on another
  machine even 6):

  -rw--- 1 root root  7013968 Apr 19 00:21 vmlinuz-4.4.0-21-generic
  -rw--- 1 root root  7015440 Mai 13 01:55 vmlinuz-4.4.0-22-generic
  -rw--- 1 root root  7020176 Jun  8 23:39 vmlinuz-4.4.0-24-generic
  -rw--- 1 root root  7026864 Jun 24 14:03 vmlinuz-4.4.0-28-generic
  -rw--- 1 root root  7047504 Jul 13 03:59 vmlinuz-4.4.0-31-generic

  
  Should not hapen that way. apt-get autoremove should clean that, but doesn't. 

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1605160] [NEW] kernel autoremove not working

2016-07-21 Thread Hadmut Danisch
Public bug reported:

On one 16.04 machine I have 5 4.4.0-kernels in /boot now (on another
machine even 6):

-rw--- 1 root root  7013968 Apr 19 00:21 vmlinuz-4.4.0-21-generic
-rw--- 1 root root  7015440 Mai 13 01:55 vmlinuz-4.4.0-22-generic
-rw--- 1 root root  7020176 Jun  8 23:39 vmlinuz-4.4.0-24-generic
-rw--- 1 root root  7026864 Jun 24 14:03 vmlinuz-4.4.0-28-generic
-rw--- 1 root root  7047504 Jul 13 03:59 vmlinuz-4.4.0-31-generic


Should not hapen that way. apt-get autoremove should clean that, but doesn't. 

regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.12~ubuntu16.04.1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jul 21 11:41:43 2016
InstallationDate: Installed on 2016-04-22 (89 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  kernel autoremove not working

Status in apt package in Ubuntu:
  New

Bug description:
  On one 16.04 machine I have 5 4.4.0-kernels in /boot now (on another
  machine even 6):

  -rw--- 1 root root  7013968 Apr 19 00:21 vmlinuz-4.4.0-21-generic
  -rw--- 1 root root  7015440 Mai 13 01:55 vmlinuz-4.4.0-22-generic
  -rw--- 1 root root  7020176 Jun  8 23:39 vmlinuz-4.4.0-24-generic
  -rw--- 1 root root  7026864 Jun 24 14:03 vmlinuz-4.4.0-28-generic
  -rw--- 1 root root  7047504 Jul 13 03:59 vmlinuz-4.4.0-31-generic

  
  Should not hapen that way. apt-get autoremove should clean that, but doesn't. 

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 11:41:43 2016
  InstallationDate: Installed on 2016-04-22 (89 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1605160/+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 1593196] Re: synthetic font generation causes confusion

2016-06-16 Thread Hadmut Danisch
I tried to fix the problem with a config file






Swis721 BdRnd BT


Bold


regular


regular





fc-cache now complains about

Fontconfig warning: "/etc/fonts/conf.d/81-swiss.conf", line 16: saw
number, expected string


although there is no number. It fixes the problem for some programs (e.g. 
gnome-specimen), but not for all (e.g. not libreoffice, which gives the same 
warning as fc-cache, but does not dinstinguish the fonts).

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

Title:
  synthetic font generation causes confusion

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi,

  the font configs just caused me lots of headache.

  I have a single TTF font (in this case Swiss 721 Bold Rounded BT),
  where the font foundry for some reason chose to call the subfamily
  name given in the TTF file 'Bold'. Which is confusing, since the font
  is not really that bold, but that's the way it is.

  
  Since this is just a single font and not a family, it causes fontconfig to 
generate synthetic fonts, i.e. it makes four out of one: The regular 
(unmodified), the bold, the italic, and the bold italic.

  That's where trouble begins. Since the original font is already named
  bold, there are suddenly two bold fonts, confusing all software that
  handles fonts by family and subfamily, e.g. libreoffice.

  
  1) It is in general not a good idea to generate synthetic fonts that cannot 
be distinguished from real font families. 

  2) It is a bad idea to generate synthatic fonts which have the same
  sub name as the original font.


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fontconfig-config 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 16 13:24:01 2016
  InstallationDate: Installed on 2016-04-22 (54 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1593196/+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 1593196] [NEW] synthetic font generation causes confusion

2016-06-16 Thread Hadmut Danisch
Public bug reported:

Hi,

the font configs just caused me lots of headache.

I have a single TTF font (in this case Swiss 721 Bold Rounded BT), where
the font foundry for some reason chose to call the subfamily name given
in the TTF file 'Bold'. Which is confusing, since the font is not really
that bold, but that's the way it is.


Since this is just a single font and not a family, it causes fontconfig to 
generate synthetic fonts, i.e. it makes four out of one: The regular 
(unmodified), the bold, the italic, and the bold italic.

That's where trouble begins. Since the original font is already named
bold, there are suddenly two bold fonts, confusing all software that
handles fonts by family and subfamily, e.g. libreoffice.


1) It is in general not a good idea to generate synthetic fonts that cannot be 
distinguished from real font families. 

2) It is a bad idea to generate synthatic fonts which have the same sub
name as the original font.


regards

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: fontconfig-config 2.11.94-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jun 16 13:24:01 2016
InstallationDate: Installed on 2016-04-22 (54 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
PackageArchitecture: all
SourcePackage: fontconfig
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  synthetic font generation causes confusion

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi,

  the font configs just caused me lots of headache.

  I have a single TTF font (in this case Swiss 721 Bold Rounded BT),
  where the font foundry for some reason chose to call the subfamily
  name given in the TTF file 'Bold'. Which is confusing, since the font
  is not really that bold, but that's the way it is.

  
  Since this is just a single font and not a family, it causes fontconfig to 
generate synthetic fonts, i.e. it makes four out of one: The regular 
(unmodified), the bold, the italic, and the bold italic.

  That's where trouble begins. Since the original font is already named
  bold, there are suddenly two bold fonts, confusing all software that
  handles fonts by family and subfamily, e.g. libreoffice.

  
  1) It is in general not a good idea to generate synthetic fonts that cannot 
be distinguished from real font families. 

  2) It is a bad idea to generate synthatic fonts which have the same
  sub name as the original font.


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fontconfig-config 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 16 13:24:01 2016
  InstallationDate: Installed on 2016-04-22 (54 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1593196/+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 1593196] Re: synthetic font generation causes confusion

2016-06-16 Thread Hadmut Danisch
BTW: Is there anywhere some docs for /etc/fonts/* stuff, or is it just
that 'take-it-as-it-is-or-die' thing?

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

Title:
  synthetic font generation causes confusion

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Hi,

  the font configs just caused me lots of headache.

  I have a single TTF font (in this case Swiss 721 Bold Rounded BT),
  where the font foundry for some reason chose to call the subfamily
  name given in the TTF file 'Bold'. Which is confusing, since the font
  is not really that bold, but that's the way it is.

  
  Since this is just a single font and not a family, it causes fontconfig to 
generate synthetic fonts, i.e. it makes four out of one: The regular 
(unmodified), the bold, the italic, and the bold italic.

  That's where trouble begins. Since the original font is already named
  bold, there are suddenly two bold fonts, confusing all software that
  handles fonts by family and subfamily, e.g. libreoffice.

  
  1) It is in general not a good idea to generate synthetic fonts that cannot 
be distinguished from real font families. 

  2) It is a bad idea to generate synthatic fonts which have the same
  sub name as the original font.


  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: fontconfig-config 2.11.94-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jun 16 13:24:01 2016
  InstallationDate: Installed on 2016-04-22 (54 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1593196/+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 1581824] Re: nfs-kernel-server dependency loop

2016-05-14 Thread Hadmut Danisch
It seems to be rather a problem of sasl2-bin.

#1575757 says that (and how) nfs-kernel-server should run inside lxc. I
therefore changed the config and tried to purge both problematic
packages sasl2-bin and nfs-kernel-server.

I could remove nfs-kernel-server, but sasl2-bin does not even allow to
remove it:


# dpkg --purge sasl2-bin


rmdir: failed to remove '/usr/lib/sasl2': No such file or directory 


  
insserv: warning: script 'K01iptdaemon' missing LSB tags and overrides
insserv: warning: script 'iptdaemon' missing LSB tags and overrides
insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
insserv: There is a loop between service iptdaemon and ondemand if started
insserv:  loop involving service ondemand at depth 6
insserv:  loop involving service iptdaemon at depth 1
insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package sasl2-bin (--purge):
 subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
 sasl2-bin



** Package changed: ubuntu => cyrus-sasl2 (Ubuntu)

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

Title:
  nfs-kernel-server dependency loop

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just trying to install nfs-kernel-server on a 16.04 machine
  running in lxc (seems odd, since lxc-machines don't have their own
  server, but there's several web pages claiming it works when

  lxc.aa_profile = unconfined

  is set).

  
  However, it fails directly at installation because of some dependency loop:

  
  # dpkg --configure --pending
  Setting up nfs-kernel-server (1:1.2.8-9ubuntu12) ...
  insserv: warning: script 'K20iptdaemon' missing LSB tags and overrides
  insserv: warning: script 'iptdaemon' missing LSB tags and overrides
  insserv: There is a loop between service ondemand and networking if started
  insserv:  loop involving service networking at depth 5
  insserv:  loop involving service urandom at depth 4
  insserv: There is a loop between service ondemand and mountdevsubfs if started
  insserv:  loop involving service mountdevsubfs at depth 2
  insserv:  loop involving service udev at depth 1
  insserv: There is a loop at service iptdaemon if started
  insserv: There is a loop at service ondemand if started
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can not be true!
  insserv: Starting iptdaemon depends on ondemand and therefore on system 
facility `$all' which can 

[Touch-packages] [Bug 1493804] Re: incorrect apparmor settings for lightdm-guest-session

2016-04-10 Thread Hadmut Danisch
Well, the sheer number of warnings on the screen renders the session
unusable. Didn't test it any further to see whether it's just warnings
or a limitation of functions.

Let's wait for 16.04.

regards

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

Title:
  incorrect apparmor settings for lightdm-guest-session

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  when using a guest session with xubuntu 15.10 beta1, I get several
  apparmor alerts (see attached file).

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Sep  9 13:00:38 2015
  InstallationDate: Installed on 2015-08-28 (12 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1493804/+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 1567102] [NEW] package systemd-sysv 229-3ubuntu2 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv

2016-04-06 Thread Hadmut Danisch
Public bug reported:

Upgrade 15.10 -> 16.04 failed

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd-sysv 229-3ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
Date: Wed Apr  6 00:24:23 2016
ErrorMessage: pre-dependency problem - not installing systemd-sysv
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.9
SourcePackage: systemd
Title: package systemd-sysv 229-3ubuntu2 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
UpgradeStatus: Upgraded to xenial on 2016-04-06 (0 days ago)

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


** Tags: amd64 apport-package need-duplicate-check xenial

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

Title:
  package systemd-sysv 229-3ubuntu2 failed to install/upgrade: pre-
  dependency problem - not installing systemd-sysv

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrade 15.10 -> 16.04 failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 229-3ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Wed Apr  6 00:24:23 2016
  ErrorMessage: pre-dependency problem - not installing systemd-sysv
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: systemd
  Title: package systemd-sysv 229-3ubuntu2 failed to install/upgrade: 
pre-dependency problem - not installing systemd-sysv
  UpgradeStatus: Upgraded to xenial on 2016-04-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1567102/+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 1535648] Re: ifquery crashing

2016-02-10 Thread Hadmut Danisch
typo:  meant ifquery --state   instead of ifstate


Need to do more checks, but seems to be fixed on Ubuntu 16.04, which comes with 
a newer version of ifupdown

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

Title:
  ifquery crashing

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just doing some tests where to use an ubuntu machine as a router
  and thus plugging in an USB Ethernet devices as it's second ethernet
  interfaces.

  Unfortunately I can't keep that damned Network manager from renaming
  the device (i.e. from eth0 to  enxe80006d8), even if I tell NM to
  ignore the device. Since this happens before udev, it confuses several
  udev scripts).

  In context of this problem I found lots of messages in /var/log/syslog
  of the kind

  Jan 19 11:27:22 pcdanisch kernel: [   58.468781] ifquery[2851]: segfault at 1 
ip 00403187 sp 7ffd578ec7e0 error 4 in ifup[40+d000]
  Jan 19 11:27:22 pcdanisch sh[799]: Segmentation fault (core dumped)
  Jan 19 11:27:23 pcdanisch kernel: [   59.827088] ifquery[2854]: segfault at 1 
ip 00403187 sp 7fffc05179f0 error 4 in ifup[40+d000]
  Jan 19 11:27:30 pcdanisch kernel: [   67.250139] ifquery[2869]: segfault at 1 
ip 00403187 sp 7ffd35611ce0 error 4 in ifup[40+d000]
  Jan 19 11:27:32 pcdanisch kernel: [   68.602021] ifquery[2872]: segfault at 1 
ip 00403187 sp 7ffcf72b86d0 error 4 in ifup[40+d000]
  Jan 19 11:27:34 pcdanisch kernel: [   70.959531] ifquery[2877]: segfault at 1 
ip 00403187 sp 7fffde45f440 error 4 in ifup[40+d000]
  Jan 19 11:27:35 pcdanisch kernel: [   72.308751] ifquery[2880]: segfault at 1 
ip 00403187 sp 7ffe5b504290 error 4 in ifup[40+d000]
  Jan 19 11:27:38 pcdanisch kernel: [   74.665195] ifquery[2885]: segfault at 1 
ip 00403187 sp 7ffc740490d0 error 4 in ifup[40+d000]
  Jan 19 11:27:41 pcdanisch kernel: [   78.025873] ifquery[2892]: segfault at 1 
ip 00403187 sp 7ffe07b6dbc0 error 4 in ifup[40+d000]
  Jan 19 11:27:42 pcdanisch kernel: [   79.373347] ifquery[2896]: segfault at 1 
ip 00403187 sp 7ffe48bf52c0 error 4 in ifup[40+d000]
  Jan 19 11:27:45 pcdanisch kernel: [   81.735654] ifquery[2901]: segfault at 1 
ip 00403187 sp 7ffdae631d10 error 4 in ifup[40+d000]
  Jan 19 11:27:46 pcdanisch kernel: [   83.096254] ifquery[2904]: segfault at 1 
ip 00403187 sp 7fff1832ff20 error 4 in ifup[40+d000]
  Jan 19 11:27:48 pcdanisch kernel: [   84.464102] ifquery[2907]: segfault at 1 
ip 00403187 sp 7fff187e0190 error 4 in ifup[40+d000]
  Jan 19 11:27:51 pcdanisch kernel: [   87.846187] ifquery[2926]: segfault at 1 
ip 00403187 sp 7ffdda95e5a0 error 4 in ifup[40+d000]
  Jan 19 11:27:53 pcdanisch kernel: [   90.221171] ifquery[2943]: segfault at 1 
ip 00403187 sp 7ffc74040e80 error 4 in ifup[40+d000]
  Jan 19 11:27:55 pcdanisch kernel: [   91.585842] ifquery[2946]: segfault at 1 
ip 00403187 sp 7ffe9e5690a0 error 4 in ifup[40+d000]
  Jan 19 11:27:56 pcdanisch kernel: [   92.944679] ifquery[2949]: segfault at 1 
ip 00403187 sp 7ffe87e171c0 error 4 in ifup[40+d000]
  Jan 19 11:27:57 pcdanisch kernel: [   94.311727] ifquery[2952]: segfault at 1 
ip 00403187 sp 7ffc6e785e50 error 4 in ifup[40+d000]
  Jan 19 11:28:00 pcdanisch kernel: [   96.675499] ifquery[2957]: segfault at 1 
ip 00403187 sp 7fff554d8c50 error 4 in ifup[40+d000]
  Jan 19 11:28:02 pcdanisch kernel: [   99.054338] ifquery[2962]: segfault at 1 
ip 00403187 sp 7ffe86f84f10 error 4 in ifup[40+d000]
  Jan 19 11:28:03 pcdanisch kernel: [  100.421026] ifquery[2965]: segfault at 1 
ip 00403187 sp 7ffc207b43e0 error 4 in ifup[40+d000]
  Jan 19 11:28:06 pcdanisch kernel: [  102.797828] ifquery[2970]: segfault at 1 
ip 00403187 sp 7ffeadf03670 error 4 in ifup[40+d000]
  Jan 19 11:28:10 pcdanisch kernel: [  107.196645] ifquery[2979]: segfault at 1 
ip 00403187 sp 7ffecb784e70 error 4 in ifup[40+d000]
  Jan 19 11:28:12 pcdanisch kernel: [  108.559839] ifquery[2982]: segfault at 1 
ip 00403187 sp 7ffd583c4260 error 4 in ifup[40+d000]
  Jan 19 11:28:14 pcdanisch kernel: [  110.923263] ifquery[2987]: segfault at 1 
ip 00403187 sp 7ffc9a42fcb0 error 4 in ifup[40+d000]
  Jan 19 11:28:15 pcdanisch kernel: [  112.290839] ifquery[2990]: segfault at 1 
ip 00403187 sp 7ffd42fb2960 error 4 in ifup[40+d000]
  Jan 19 11:28:17 pcdanisch kernel: [  113.663268] ifquery[2993]: segfault at 1 
ip 00403187 sp 7ffec52573c0 error 4 in ifup[40+d000]
  Jan 19 11:28:19 pcdanisch kernel: [  116.039414] ifquery[2998]: segfault at 1 
ip 00403187 sp 

[Touch-packages] [Bug 1535648] Re: ifquery crashing

2016-01-20 Thread Hadmut Danisch
Famous last words of strace -s 80 -f ifquery --state vlan0


arch_prctl(ARCH_SET_FS, 0x7fb790db1700) = 0
mprotect(0x7fb790bb2000, 16384, PROT_READ) = 0
mprotect(0x60c000, 4096, PROT_READ) = 0
mprotect(0x7fb790ddf000, 4096, PROT_READ) = 0
munmap(0x7fb790db3000, 171412)  = 0
fcntl(0, F_GETFD)   = 0
fcntl(1, F_GETFD)   = 0
fcntl(2, F_GETFD)   = 0
brk(0)  = 0x10f3000
brk(0x1114000)  = 0x1114000
open("/run/network/.ifstate.lock", O_RDONLY) = -1 ENOENT (No such file or 
directory)
open("/run/network/ifstate", O_RDONLY)  = -1 ENOENT (No such file or directory)
exit_group(1)   = ?
+++ exited with 1 +++

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

Title:
  ifquery crashing

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just doing some tests where to use an ubuntu machine as a router
  and thus plugging in an USB Ethernet devices as it's second ethernet
  interfaces.

  Unfortunately I can't keep that damned Network manager from renaming
  the device (i.e. from eth0 to  enxe80006d8), even if I tell NM to
  ignore the device. Since this happens before udev, it confuses several
  udev scripts).

  In context of this problem I found lots of messages in /var/log/syslog
  of the kind

  Jan 19 11:27:22 pcdanisch kernel: [   58.468781] ifquery[2851]: segfault at 1 
ip 00403187 sp 7ffd578ec7e0 error 4 in ifup[40+d000]
  Jan 19 11:27:22 pcdanisch sh[799]: Segmentation fault (core dumped)
  Jan 19 11:27:23 pcdanisch kernel: [   59.827088] ifquery[2854]: segfault at 1 
ip 00403187 sp 7fffc05179f0 error 4 in ifup[40+d000]
  Jan 19 11:27:30 pcdanisch kernel: [   67.250139] ifquery[2869]: segfault at 1 
ip 00403187 sp 7ffd35611ce0 error 4 in ifup[40+d000]
  Jan 19 11:27:32 pcdanisch kernel: [   68.602021] ifquery[2872]: segfault at 1 
ip 00403187 sp 7ffcf72b86d0 error 4 in ifup[40+d000]
  Jan 19 11:27:34 pcdanisch kernel: [   70.959531] ifquery[2877]: segfault at 1 
ip 00403187 sp 7fffde45f440 error 4 in ifup[40+d000]
  Jan 19 11:27:35 pcdanisch kernel: [   72.308751] ifquery[2880]: segfault at 1 
ip 00403187 sp 7ffe5b504290 error 4 in ifup[40+d000]
  Jan 19 11:27:38 pcdanisch kernel: [   74.665195] ifquery[2885]: segfault at 1 
ip 00403187 sp 7ffc740490d0 error 4 in ifup[40+d000]
  Jan 19 11:27:41 pcdanisch kernel: [   78.025873] ifquery[2892]: segfault at 1 
ip 00403187 sp 7ffe07b6dbc0 error 4 in ifup[40+d000]
  Jan 19 11:27:42 pcdanisch kernel: [   79.373347] ifquery[2896]: segfault at 1 
ip 00403187 sp 7ffe48bf52c0 error 4 in ifup[40+d000]
  Jan 19 11:27:45 pcdanisch kernel: [   81.735654] ifquery[2901]: segfault at 1 
ip 00403187 sp 7ffdae631d10 error 4 in ifup[40+d000]
  Jan 19 11:27:46 pcdanisch kernel: [   83.096254] ifquery[2904]: segfault at 1 
ip 00403187 sp 7fff1832ff20 error 4 in ifup[40+d000]
  Jan 19 11:27:48 pcdanisch kernel: [   84.464102] ifquery[2907]: segfault at 1 
ip 00403187 sp 7fff187e0190 error 4 in ifup[40+d000]
  Jan 19 11:27:51 pcdanisch kernel: [   87.846187] ifquery[2926]: segfault at 1 
ip 00403187 sp 7ffdda95e5a0 error 4 in ifup[40+d000]
  Jan 19 11:27:53 pcdanisch kernel: [   90.221171] ifquery[2943]: segfault at 1 
ip 00403187 sp 7ffc74040e80 error 4 in ifup[40+d000]
  Jan 19 11:27:55 pcdanisch kernel: [   91.585842] ifquery[2946]: segfault at 1 
ip 00403187 sp 7ffe9e5690a0 error 4 in ifup[40+d000]
  Jan 19 11:27:56 pcdanisch kernel: [   92.944679] ifquery[2949]: segfault at 1 
ip 00403187 sp 7ffe87e171c0 error 4 in ifup[40+d000]
  Jan 19 11:27:57 pcdanisch kernel: [   94.311727] ifquery[2952]: segfault at 1 
ip 00403187 sp 7ffc6e785e50 error 4 in ifup[40+d000]
  Jan 19 11:28:00 pcdanisch kernel: [   96.675499] ifquery[2957]: segfault at 1 
ip 00403187 sp 7fff554d8c50 error 4 in ifup[40+d000]
  Jan 19 11:28:02 pcdanisch kernel: [   99.054338] ifquery[2962]: segfault at 1 
ip 00403187 sp 7ffe86f84f10 error 4 in ifup[40+d000]
  Jan 19 11:28:03 pcdanisch kernel: [  100.421026] ifquery[2965]: segfault at 1 
ip 00403187 sp 7ffc207b43e0 error 4 in ifup[40+d000]
  Jan 19 11:28:06 pcdanisch kernel: [  102.797828] ifquery[2970]: segfault at 1 
ip 00403187 sp 7ffeadf03670 error 4 in ifup[40+d000]
  Jan 19 11:28:10 pcdanisch kernel: [  107.196645] ifquery[2979]: segfault at 1 
ip 00403187 sp 7ffecb784e70 error 4 in ifup[40+d000]
  Jan 19 11:28:12 pcdanisch kernel: [  108.559839] ifquery[2982]: segfault at 1 
ip 00403187 sp 

[Touch-packages] [Bug 1535648] Re: ifquery crashing

2016-01-20 Thread Hadmut Danisch
I've found two problems:


1.) See /lib/systemd/system/ifup-wait-all-auto.service   the line 

  for i in $(ifquery --list --exclude lo --allow auto); do
INTERFACES="$INTERFACES$i "; done;

  There is  a space missing in "$INTERFACES$i "  it concatenates all
device names into one


2.) This ifquery-call just crashes:

# ifquery --state vlan0
Segmentation fault (core dumped)

# ifquery --state lo
Segmentation fault (core dumped)


for some reason it does not crash with eth0

# ifquery --state eth0


So please fix ifquery.

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

Title:
  ifquery crashing

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just doing some tests where to use an ubuntu machine as a router
  and thus plugging in an USB Ethernet devices as it's second ethernet
  interfaces.

  Unfortunately I can't keep that damned Network manager from renaming
  the device (i.e. from eth0 to  enxe80006d8), even if I tell NM to
  ignore the device. Since this happens before udev, it confuses several
  udev scripts).

  In context of this problem I found lots of messages in /var/log/syslog
  of the kind

  Jan 19 11:27:22 pcdanisch kernel: [   58.468781] ifquery[2851]: segfault at 1 
ip 00403187 sp 7ffd578ec7e0 error 4 in ifup[40+d000]
  Jan 19 11:27:22 pcdanisch sh[799]: Segmentation fault (core dumped)
  Jan 19 11:27:23 pcdanisch kernel: [   59.827088] ifquery[2854]: segfault at 1 
ip 00403187 sp 7fffc05179f0 error 4 in ifup[40+d000]
  Jan 19 11:27:30 pcdanisch kernel: [   67.250139] ifquery[2869]: segfault at 1 
ip 00403187 sp 7ffd35611ce0 error 4 in ifup[40+d000]
  Jan 19 11:27:32 pcdanisch kernel: [   68.602021] ifquery[2872]: segfault at 1 
ip 00403187 sp 7ffcf72b86d0 error 4 in ifup[40+d000]
  Jan 19 11:27:34 pcdanisch kernel: [   70.959531] ifquery[2877]: segfault at 1 
ip 00403187 sp 7fffde45f440 error 4 in ifup[40+d000]
  Jan 19 11:27:35 pcdanisch kernel: [   72.308751] ifquery[2880]: segfault at 1 
ip 00403187 sp 7ffe5b504290 error 4 in ifup[40+d000]
  Jan 19 11:27:38 pcdanisch kernel: [   74.665195] ifquery[2885]: segfault at 1 
ip 00403187 sp 7ffc740490d0 error 4 in ifup[40+d000]
  Jan 19 11:27:41 pcdanisch kernel: [   78.025873] ifquery[2892]: segfault at 1 
ip 00403187 sp 7ffe07b6dbc0 error 4 in ifup[40+d000]
  Jan 19 11:27:42 pcdanisch kernel: [   79.373347] ifquery[2896]: segfault at 1 
ip 00403187 sp 7ffe48bf52c0 error 4 in ifup[40+d000]
  Jan 19 11:27:45 pcdanisch kernel: [   81.735654] ifquery[2901]: segfault at 1 
ip 00403187 sp 7ffdae631d10 error 4 in ifup[40+d000]
  Jan 19 11:27:46 pcdanisch kernel: [   83.096254] ifquery[2904]: segfault at 1 
ip 00403187 sp 7fff1832ff20 error 4 in ifup[40+d000]
  Jan 19 11:27:48 pcdanisch kernel: [   84.464102] ifquery[2907]: segfault at 1 
ip 00403187 sp 7fff187e0190 error 4 in ifup[40+d000]
  Jan 19 11:27:51 pcdanisch kernel: [   87.846187] ifquery[2926]: segfault at 1 
ip 00403187 sp 7ffdda95e5a0 error 4 in ifup[40+d000]
  Jan 19 11:27:53 pcdanisch kernel: [   90.221171] ifquery[2943]: segfault at 1 
ip 00403187 sp 7ffc74040e80 error 4 in ifup[40+d000]
  Jan 19 11:27:55 pcdanisch kernel: [   91.585842] ifquery[2946]: segfault at 1 
ip 00403187 sp 7ffe9e5690a0 error 4 in ifup[40+d000]
  Jan 19 11:27:56 pcdanisch kernel: [   92.944679] ifquery[2949]: segfault at 1 
ip 00403187 sp 7ffe87e171c0 error 4 in ifup[40+d000]
  Jan 19 11:27:57 pcdanisch kernel: [   94.311727] ifquery[2952]: segfault at 1 
ip 00403187 sp 7ffc6e785e50 error 4 in ifup[40+d000]
  Jan 19 11:28:00 pcdanisch kernel: [   96.675499] ifquery[2957]: segfault at 1 
ip 00403187 sp 7fff554d8c50 error 4 in ifup[40+d000]
  Jan 19 11:28:02 pcdanisch kernel: [   99.054338] ifquery[2962]: segfault at 1 
ip 00403187 sp 7ffe86f84f10 error 4 in ifup[40+d000]
  Jan 19 11:28:03 pcdanisch kernel: [  100.421026] ifquery[2965]: segfault at 1 
ip 00403187 sp 7ffc207b43e0 error 4 in ifup[40+d000]
  Jan 19 11:28:06 pcdanisch kernel: [  102.797828] ifquery[2970]: segfault at 1 
ip 00403187 sp 7ffeadf03670 error 4 in ifup[40+d000]
  Jan 19 11:28:10 pcdanisch kernel: [  107.196645] ifquery[2979]: segfault at 1 
ip 00403187 sp 7ffecb784e70 error 4 in ifup[40+d000]
  Jan 19 11:28:12 pcdanisch kernel: [  108.559839] ifquery[2982]: segfault at 1 
ip 00403187 sp 7ffd583c4260 error 4 in ifup[40+d000]
  Jan 19 11:28:14 pcdanisch kernel: [  110.923263] ifquery[2987]: segfault at 1 
ip 00403187 sp 7ffc9a42fcb0 error 4 in ifup[40+d000]
  Jan 19 11:28:15 pcdanisch kernel: [  

[Touch-packages] [Bug 1535648] Re: ifquery crashing

2016-01-20 Thread Hadmut Danisch
More analysis:

ifstate crashes if /run/network/ifstate is not present.

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

Title:
  ifquery crashing

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just doing some tests where to use an ubuntu machine as a router
  and thus plugging in an USB Ethernet devices as it's second ethernet
  interfaces.

  Unfortunately I can't keep that damned Network manager from renaming
  the device (i.e. from eth0 to  enxe80006d8), even if I tell NM to
  ignore the device. Since this happens before udev, it confuses several
  udev scripts).

  In context of this problem I found lots of messages in /var/log/syslog
  of the kind

  Jan 19 11:27:22 pcdanisch kernel: [   58.468781] ifquery[2851]: segfault at 1 
ip 00403187 sp 7ffd578ec7e0 error 4 in ifup[40+d000]
  Jan 19 11:27:22 pcdanisch sh[799]: Segmentation fault (core dumped)
  Jan 19 11:27:23 pcdanisch kernel: [   59.827088] ifquery[2854]: segfault at 1 
ip 00403187 sp 7fffc05179f0 error 4 in ifup[40+d000]
  Jan 19 11:27:30 pcdanisch kernel: [   67.250139] ifquery[2869]: segfault at 1 
ip 00403187 sp 7ffd35611ce0 error 4 in ifup[40+d000]
  Jan 19 11:27:32 pcdanisch kernel: [   68.602021] ifquery[2872]: segfault at 1 
ip 00403187 sp 7ffcf72b86d0 error 4 in ifup[40+d000]
  Jan 19 11:27:34 pcdanisch kernel: [   70.959531] ifquery[2877]: segfault at 1 
ip 00403187 sp 7fffde45f440 error 4 in ifup[40+d000]
  Jan 19 11:27:35 pcdanisch kernel: [   72.308751] ifquery[2880]: segfault at 1 
ip 00403187 sp 7ffe5b504290 error 4 in ifup[40+d000]
  Jan 19 11:27:38 pcdanisch kernel: [   74.665195] ifquery[2885]: segfault at 1 
ip 00403187 sp 7ffc740490d0 error 4 in ifup[40+d000]
  Jan 19 11:27:41 pcdanisch kernel: [   78.025873] ifquery[2892]: segfault at 1 
ip 00403187 sp 7ffe07b6dbc0 error 4 in ifup[40+d000]
  Jan 19 11:27:42 pcdanisch kernel: [   79.373347] ifquery[2896]: segfault at 1 
ip 00403187 sp 7ffe48bf52c0 error 4 in ifup[40+d000]
  Jan 19 11:27:45 pcdanisch kernel: [   81.735654] ifquery[2901]: segfault at 1 
ip 00403187 sp 7ffdae631d10 error 4 in ifup[40+d000]
  Jan 19 11:27:46 pcdanisch kernel: [   83.096254] ifquery[2904]: segfault at 1 
ip 00403187 sp 7fff1832ff20 error 4 in ifup[40+d000]
  Jan 19 11:27:48 pcdanisch kernel: [   84.464102] ifquery[2907]: segfault at 1 
ip 00403187 sp 7fff187e0190 error 4 in ifup[40+d000]
  Jan 19 11:27:51 pcdanisch kernel: [   87.846187] ifquery[2926]: segfault at 1 
ip 00403187 sp 7ffdda95e5a0 error 4 in ifup[40+d000]
  Jan 19 11:27:53 pcdanisch kernel: [   90.221171] ifquery[2943]: segfault at 1 
ip 00403187 sp 7ffc74040e80 error 4 in ifup[40+d000]
  Jan 19 11:27:55 pcdanisch kernel: [   91.585842] ifquery[2946]: segfault at 1 
ip 00403187 sp 7ffe9e5690a0 error 4 in ifup[40+d000]
  Jan 19 11:27:56 pcdanisch kernel: [   92.944679] ifquery[2949]: segfault at 1 
ip 00403187 sp 7ffe87e171c0 error 4 in ifup[40+d000]
  Jan 19 11:27:57 pcdanisch kernel: [   94.311727] ifquery[2952]: segfault at 1 
ip 00403187 sp 7ffc6e785e50 error 4 in ifup[40+d000]
  Jan 19 11:28:00 pcdanisch kernel: [   96.675499] ifquery[2957]: segfault at 1 
ip 00403187 sp 7fff554d8c50 error 4 in ifup[40+d000]
  Jan 19 11:28:02 pcdanisch kernel: [   99.054338] ifquery[2962]: segfault at 1 
ip 00403187 sp 7ffe86f84f10 error 4 in ifup[40+d000]
  Jan 19 11:28:03 pcdanisch kernel: [  100.421026] ifquery[2965]: segfault at 1 
ip 00403187 sp 7ffc207b43e0 error 4 in ifup[40+d000]
  Jan 19 11:28:06 pcdanisch kernel: [  102.797828] ifquery[2970]: segfault at 1 
ip 00403187 sp 7ffeadf03670 error 4 in ifup[40+d000]
  Jan 19 11:28:10 pcdanisch kernel: [  107.196645] ifquery[2979]: segfault at 1 
ip 00403187 sp 7ffecb784e70 error 4 in ifup[40+d000]
  Jan 19 11:28:12 pcdanisch kernel: [  108.559839] ifquery[2982]: segfault at 1 
ip 00403187 sp 7ffd583c4260 error 4 in ifup[40+d000]
  Jan 19 11:28:14 pcdanisch kernel: [  110.923263] ifquery[2987]: segfault at 1 
ip 00403187 sp 7ffc9a42fcb0 error 4 in ifup[40+d000]
  Jan 19 11:28:15 pcdanisch kernel: [  112.290839] ifquery[2990]: segfault at 1 
ip 00403187 sp 7ffd42fb2960 error 4 in ifup[40+d000]
  Jan 19 11:28:17 pcdanisch kernel: [  113.663268] ifquery[2993]: segfault at 1 
ip 00403187 sp 7ffec52573c0 error 4 in ifup[40+d000]
  Jan 19 11:28:19 pcdanisch kernel: [  116.039414] ifquery[2998]: segfault at 1 
ip 00403187 sp 7ffc89c7a6a0 error 4 in ifup[40+d000]
  Jan 19 11:28:20 pcdanisch kernel: [  

[Touch-packages] [Bug 1535635] [NEW] NetworkManager does not really ignore devices, disturbing udev

2016-01-19 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm just trying to configure an ubuntu machine to work as a network
controller (dhcp, dns,...) for several virtual and physical machines,
using a linux bridge as a virtual network, and trying to automatically
add USB-Ethernet-Devices to the bridge through udev.

Unfortunately my udev rules fail since Network Manager does rename new
Ethernet devices *before* udev runs, e.g.

eth0 to enxe80006d8

for my USB ethernet device. Thus, many regular udev rules fail since
they use the device name the kernel passes (=eth0), but can't find that
device for commands (since it changed it's name).

Instructing NetworkManager to ignore ifup-configured devices does not
help, since NetworkManager renames the devices and thus does not apply
/etc/network/interfaces rules for eth0.

Even worse: Even when listing the particular mac address in
/etc/NetworkManager/NetworkManager.conf to be ignored, NM ignores it in
the way that it does not configure it, but still renames it.

Is there any other way to make NetworkManager completely keep its dirty
fingers away from Network Devices except for completely killing it?

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Jan 19 11:16:42 2016
InstallationDate: Installed on 2015-09-03 (137 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
IpRoute:
 default via 192.168.103.254 dev enp2s0  proto static  metric 100 
 169.254.0.0/16 dev docker0  scope link  metric 1000 
 172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
 192.168.100.0/22 dev enp2s0  proto kernel  scope link  src 192.168.102.125  
metric 100 
 192.168.200.0/24 dev vlan0  proto kernel  scope link  src 192.168.200.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2016-01-19T11:01:36.653148
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH
 docker0 5b3eb2b2-d7bd-49a4-9b1d-32c6dbaaf121  bridge  
1453198365  Di 19 Jan 2016 11:12:45 CET  no   0 no  
  /org/freedesktop/NetworkManager/Settings/1  yes docker0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 Wired connection 1  c9b5bf9d-a9f7-4b15-a183-63209d80bf73  802-3-ethernet  
1453198365  Di 19 Jan 2016 11:12:45 CET  yes  0 no  
  /org/freedesktop/NetworkManager/Settings/0  yes enp2s0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  NetworkManager does not really ignore devices, disturbing udev

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  I'm just trying to configure an ubuntu machine to work as a network
  controller (dhcp, dns,...) for several virtual and physical machines,
  using a linux bridge as a virtual network, and trying to automatically
  add USB-Ethernet-Devices to the bridge through udev.

  Unfortunately my udev rules fail since Network Manager does rename new
  Ethernet devices *before* udev runs, e.g.

  eth0 to enxe80006d8

  for my USB ethernet device. Thus, many regular udev rules fail since
  they use the device name the kernel passes (=eth0), but can't find
  that device for commands (since it changed it's name).

  Instructing NetworkManager to ignore ifup-configured devices does not
  help, since NetworkManager renames the devices and thus does not apply
  /etc/network/interfaces rules for eth0.

  Even worse: Even when listing the particular mac address in
  /etc/NetworkManager/NetworkManager.conf to be ignored, NM ignores it
  in the way that it does not configure it, but still renames it.

  Is there any other way to make NetworkManager completely keep its
  dirty fingers away from Network Devices except for completely killing
  it?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  

[Touch-packages] [Bug 1535648] [NEW] ifquery crashing

2016-01-19 Thread Hadmut Danisch
Public bug reported:

Hi,

I'm just doing some tests where to use an ubuntu machine as a router and
thus plugging in an USB Ethernet devices as it's second ethernet
interfaces.

Unfortunately I can't keep that damned Network manager from renaming the
device (i.e. from eth0 to  enxe80006d8), even if I tell NM to ignore
the device. Since this happens before udev, it confuses several udev
scripts).

In context of this problem I found lots of messages in /var/log/syslog
of the kind

Jan 19 11:27:22 pcdanisch kernel: [   58.468781] ifquery[2851]: segfault at 1 
ip 00403187 sp 7ffd578ec7e0 error 4 in ifup[40+d000]
Jan 19 11:27:22 pcdanisch sh[799]: Segmentation fault (core dumped)
Jan 19 11:27:23 pcdanisch kernel: [   59.827088] ifquery[2854]: segfault at 1 
ip 00403187 sp 7fffc05179f0 error 4 in ifup[40+d000]
Jan 19 11:27:30 pcdanisch kernel: [   67.250139] ifquery[2869]: segfault at 1 
ip 00403187 sp 7ffd35611ce0 error 4 in ifup[40+d000]
Jan 19 11:27:32 pcdanisch kernel: [   68.602021] ifquery[2872]: segfault at 1 
ip 00403187 sp 7ffcf72b86d0 error 4 in ifup[40+d000]
Jan 19 11:27:34 pcdanisch kernel: [   70.959531] ifquery[2877]: segfault at 1 
ip 00403187 sp 7fffde45f440 error 4 in ifup[40+d000]
Jan 19 11:27:35 pcdanisch kernel: [   72.308751] ifquery[2880]: segfault at 1 
ip 00403187 sp 7ffe5b504290 error 4 in ifup[40+d000]
Jan 19 11:27:38 pcdanisch kernel: [   74.665195] ifquery[2885]: segfault at 1 
ip 00403187 sp 7ffc740490d0 error 4 in ifup[40+d000]
Jan 19 11:27:41 pcdanisch kernel: [   78.025873] ifquery[2892]: segfault at 1 
ip 00403187 sp 7ffe07b6dbc0 error 4 in ifup[40+d000]
Jan 19 11:27:42 pcdanisch kernel: [   79.373347] ifquery[2896]: segfault at 1 
ip 00403187 sp 7ffe48bf52c0 error 4 in ifup[40+d000]
Jan 19 11:27:45 pcdanisch kernel: [   81.735654] ifquery[2901]: segfault at 1 
ip 00403187 sp 7ffdae631d10 error 4 in ifup[40+d000]
Jan 19 11:27:46 pcdanisch kernel: [   83.096254] ifquery[2904]: segfault at 1 
ip 00403187 sp 7fff1832ff20 error 4 in ifup[40+d000]
Jan 19 11:27:48 pcdanisch kernel: [   84.464102] ifquery[2907]: segfault at 1 
ip 00403187 sp 7fff187e0190 error 4 in ifup[40+d000]
Jan 19 11:27:51 pcdanisch kernel: [   87.846187] ifquery[2926]: segfault at 1 
ip 00403187 sp 7ffdda95e5a0 error 4 in ifup[40+d000]
Jan 19 11:27:53 pcdanisch kernel: [   90.221171] ifquery[2943]: segfault at 1 
ip 00403187 sp 7ffc74040e80 error 4 in ifup[40+d000]
Jan 19 11:27:55 pcdanisch kernel: [   91.585842] ifquery[2946]: segfault at 1 
ip 00403187 sp 7ffe9e5690a0 error 4 in ifup[40+d000]
Jan 19 11:27:56 pcdanisch kernel: [   92.944679] ifquery[2949]: segfault at 1 
ip 00403187 sp 7ffe87e171c0 error 4 in ifup[40+d000]
Jan 19 11:27:57 pcdanisch kernel: [   94.311727] ifquery[2952]: segfault at 1 
ip 00403187 sp 7ffc6e785e50 error 4 in ifup[40+d000]
Jan 19 11:28:00 pcdanisch kernel: [   96.675499] ifquery[2957]: segfault at 1 
ip 00403187 sp 7fff554d8c50 error 4 in ifup[40+d000]
Jan 19 11:28:02 pcdanisch kernel: [   99.054338] ifquery[2962]: segfault at 1 
ip 00403187 sp 7ffe86f84f10 error 4 in ifup[40+d000]
Jan 19 11:28:03 pcdanisch kernel: [  100.421026] ifquery[2965]: segfault at 1 
ip 00403187 sp 7ffc207b43e0 error 4 in ifup[40+d000]
Jan 19 11:28:06 pcdanisch kernel: [  102.797828] ifquery[2970]: segfault at 1 
ip 00403187 sp 7ffeadf03670 error 4 in ifup[40+d000]
Jan 19 11:28:10 pcdanisch kernel: [  107.196645] ifquery[2979]: segfault at 1 
ip 00403187 sp 7ffecb784e70 error 4 in ifup[40+d000]
Jan 19 11:28:12 pcdanisch kernel: [  108.559839] ifquery[2982]: segfault at 1 
ip 00403187 sp 7ffd583c4260 error 4 in ifup[40+d000]
Jan 19 11:28:14 pcdanisch kernel: [  110.923263] ifquery[2987]: segfault at 1 
ip 00403187 sp 7ffc9a42fcb0 error 4 in ifup[40+d000]
Jan 19 11:28:15 pcdanisch kernel: [  112.290839] ifquery[2990]: segfault at 1 
ip 00403187 sp 7ffd42fb2960 error 4 in ifup[40+d000]
Jan 19 11:28:17 pcdanisch kernel: [  113.663268] ifquery[2993]: segfault at 1 
ip 00403187 sp 7ffec52573c0 error 4 in ifup[40+d000]
Jan 19 11:28:19 pcdanisch kernel: [  116.039414] ifquery[2998]: segfault at 1 
ip 00403187 sp 7ffc89c7a6a0 error 4 in ifup[40+d000]
Jan 19 11:28:20 pcdanisch kernel: [  117.410062] ifquery[3001]: segfault at 1 
ip 00403187 sp 7ffc73a40f90 error 4 in ifup[40+d000]
Jan 19 11:28:22 pcdanisch kernel: [  118.778371] ifquery[3004]: segfault at 1 
ip 00403187 sp 7fff27fa05e0 error 4 in ifup[40+d000]
Jan 19 11:28:24 pcdanisch kernel: [  121.154538] ifquery[3009]: segfault at 1 
ip 00403187 sp 7fff61c73220 error 4 in ifup[40+d000]

[Touch-packages] [Bug 1535665] [NEW] ifup no taking up bridge at boot time

2016-01-19 Thread Hadmut Danisch
Public bug reported:

Hi,

I have a

source interfaces.d/vlan0
 
in my /etc/network/interfaces, and in that vlan0 file

auto vlan0
iface vlan0 inet static
  bridge_ports none
  bridge_fd0
  bridge_stp   off
  address  192.168.200.1
  netmask  255.255.255.0
  up   iptables -I INPUT   -j ACCEPT -i $IFACE
  up   iptables -I FORWARD -j ACCEPT -i $IFACE
  up   iptables -I FORWARD -j ACCEPT -o $IFACE
  up   dnsmasq --pid-file=/var/run/dnsmasq.$IFACE.pid 
--except-interface=lo --interface=$IFACE --bind-interfaces 
--dhcp-range=192.168.200.100,192.168.200.250 
--dhcp-boot=/pxelinux.0,192.168.200.1 --enable-tftp 
--tftp-root=/var/lib/tftpboot
  down kill `cat /var/run/dnsmasq.$IFACE.pid`


Seems to be straightforward , and works correctly if I call   ifup vlan0 from 
the command line.

However, the bridge interface is not created within the boot process. I
have to call it manually every time.

Seems to be related to #1535648  ifquery/ifup crashing, which happens
even without the usb device mentioned there and might be the reason,
i.e. crash when trying to create this interface.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: ifupdown 0.7.54ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
Uname: Linux 4.2.0-23-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Jan 19 12:09:54 2016
InstallationDate: Installed on 2015-09-03 (137 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: ifupdown
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  ifup no taking up bridge at boot time

Status in ifupdown package in Ubuntu:
  New

Bug description:
  Hi,

  I have a

  source interfaces.d/vlan0
   
  in my /etc/network/interfaces, and in that vlan0 file

  auto vlan0
  iface vlan0 inet static
bridge_ports none
bridge_fd0
bridge_stp   off
address  192.168.200.1
netmask  255.255.255.0
up   iptables -I INPUT   -j ACCEPT -i $IFACE
up   iptables -I FORWARD -j ACCEPT -i $IFACE
up   iptables -I FORWARD -j ACCEPT -o $IFACE
up   dnsmasq --pid-file=/var/run/dnsmasq.$IFACE.pid 
--except-interface=lo --interface=$IFACE --bind-interfaces 
--dhcp-range=192.168.200.100,192.168.200.250 
--dhcp-boot=/pxelinux.0,192.168.200.1 --enable-tftp 
--tftp-root=/var/lib/tftpboot
down kill `cat /var/run/dnsmasq.$IFACE.pid`

  
  Seems to be straightforward , and works correctly if I call   ifup vlan0 from 
the command line.

  However, the bridge interface is not created within the boot process.
  I have to call it manually every time.

  Seems to be related to #1535648  ifquery/ifup crashing, which happens
  even without the usb device mentioned there and might be the reason,
  i.e. crash when trying to create this interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ifupdown 0.7.54ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Jan 19 12:09:54 2016
  InstallationDate: Installed on 2015-09-03 (137 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: ifupdown
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1535665/+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 1530951] [NEW] Ubuntu 15.10 claims to be a debian jessie

2016-01-04 Thread Hadmut Danisch
Public bug reported:

Ubuntu 15.10 comes with a /etc/debian_version , claiming to be a
jessie/sid. Can confuse software. Should have /etc/ubuntu_version
instead.

regards

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: base-files 7.2ubuntu11
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jan  4 19:41:03 2016
Dependencies:
 
InstallationDate: Installed on 2015-10-08 (87 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
SourcePackage: base-files
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wily

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

Title:
  Ubuntu 15.10 claims to be a debian jessie

Status in base-files package in Ubuntu:
  New

Bug description:
  Ubuntu 15.10 comes with a /etc/debian_version , claiming to be a
  jessie/sid. Can confuse software. Should have /etc/ubuntu_version
  instead.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: base-files 7.2ubuntu11
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jan  4 19:41:03 2016
  Dependencies:
   
  InstallationDate: Installed on 2015-10-08 (87 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1530951/+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 1506139] Re: 15.10beta crashes encrypted swap partition

2015-11-28 Thread Hadmut Danisch
Further observations:


I meanwhile figured out three modes:

1) putting the swap flag into /etc/crypttab   -> crashes the partition
every now and then, but not always.


2) removing the flag from /etc/crypttab, but keeping it in /etc/fstab and 
keeping it in 
/etc/initramfs-tools/conf.d/resume:   Everything works well , but  a) initramfs 
asks for the password twice (once per partition), which is sort of annoying, 
maybe the password sharing scripts coming with cryptsetup might work (didn't 
try yet with 15.10).


3) as 2, but removing /etc/initramfs-tools/conf.d/resume: Interesting effect. 
The bootprocess asks for password only once for the root partition(!), but 
systemd nevertheless mounts the swap partition as a second  luks device without 
needing the password.  Source code says something about a password cache, so 
the password from the root device seems to be cache for some time and 
accessible. Nice, but resume from hibernation does not work.  


Unfortunately the ubuntu installer produces mode 1, which does not
really work.

This mess should really be fixed for 16.04 LTS. In my eyes it's a major
problem of systemd, but the initramfs code could also be extended to use
the password cache (which is there and caches anyway) to avoid asking
twice.

regards

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

Title:
  15.10beta crashes encrypted swap partition

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I 
experienced the problem that the swap is not activated at boot time and that 
/dev/disks/by-uuid does not contain a link to the swap partition, and the 
previously created luks-encrypted swap is destroyed after boot: It is not a 
luks partition anymore and filled with random (presumably encrypted) bytes 
without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab:
   sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
   sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+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 1517383] [NEW] chromium browser cause heaps of apparmor warnings

2015-11-18 Thread Hadmut Danisch
Public bug reported:

Hi,

I had recently reported that the chromium-browser cause lots of apparmor
denial messages, thus filling the screen completely with those ubuntu-
specific black warning message tiles.  See #1504049

Some people then turned this into a guest session problem and fixed the
guest session problem with

/etc/apparmor.d/abstractions/lightdm_chromium-browser

but this file is included only in lightdm-guest-session and thus
effective in guest sessions only.

usr.bin.chromium-browser instead reads abstractions/ubuntu-browsers.d
/chromium-browser , which does not contain the bug fixes.


So the people fixed a different problem.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Nov 18 10:35:57 2015
InstallationDate: Installed on 2015-09-03 (75 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug wily

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

Title:
  chromium browser cause heaps of apparmor warnings

Status in lightdm package in Ubuntu:
  New

Bug description:
  Hi,

  I had recently reported that the chromium-browser cause lots of
  apparmor denial messages, thus filling the screen completely with
  those ubuntu-specific black warning message tiles.  See #1504049

  Some people then turned this into a guest session problem and fixed
  the guest session problem with

  /etc/apparmor.d/abstractions/lightdm_chromium-browser

  but this file is included only in lightdm-guest-session and thus
  effective in guest sessions only.

  usr.bin.chromium-browser instead reads abstractions/ubuntu-browsers.d
  /chromium-browser , which does not contain the bug fixes.

  
  So the people fixed a different problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lightdm 1.16.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Nov 18 10:35:57 2015
  InstallationDate: Installed on 2015-09-03 (75 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1517383/+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 1514080] [NEW] lxc-templates lacks template for ubuntu core

2015-11-07 Thread Hadmut Danisch
Public bug reported:

Hi,

lxc-templates comes with tamples for ubuntu and ubuntu-cloud, but both
are rather large and „complete”, too large for most applications. E.g.
it does not make sense to have multiple consoles running in a container
or an sshd.

Would be nice to have a template for ubuntu-core as an absolute minimal
system.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lxc-templates 1.1.4-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Nov  7 16:04:54 2015
InstallationDate: Installed on 2015-10-08 (29 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
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

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


** Tags: amd64 apparmor apport-bug wily

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

Title:
  lxc-templates lacks template for ubuntu core

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi,

  lxc-templates comes with tamples for ubuntu and ubuntu-cloud, but both
  are rather large and „complete”, too large for most applications. E.g.
  it does not make sense to have multiple consoles running in a
  container or an sshd.

  Would be nice to have a template for ubuntu-core as an absolute
  minimal system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc-templates 1.1.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov  7 16:04:54 2015
  InstallationDate: Installed on 2015-10-08 (29 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  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/1514080/+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 1514080] Re: lxc-templates lacks template for ubuntu core

2015-11-07 Thread Hadmut Danisch
As far as I can see the ubuntu template uses debootstrap and not the
core image.

And a plain lxc image created with the ubuntu template takes 379 MB
(btrfs file system), while an unpacked ubuntu core has just 145 MB.

So I doubt that this is the same.

It is, btw., not a good idea to include vom and sshd by default. What
would a lxc container need a sshd for by default?

On the contrary, it is definitely a severe security problem to install
an sshd on y machine , which has a default user ubuntu with default
password ubuntu and ability to become root with the same default
password.

Who creates such security gaps?

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

Title:
  lxc-templates lacks template for ubuntu core

Status in lxc package in Ubuntu:
  New

Bug description:
  Hi,

  lxc-templates comes with tamples for ubuntu and ubuntu-cloud, but both
  are rather large and „complete”, too large for most applications. E.g.
  it does not make sense to have multiple consoles running in a
  container or an sshd.

  Would be nice to have a template for ubuntu-core as an absolute
  minimal system.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: lxc-templates 1.1.4-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Nov  7 16:04:54 2015
  InstallationDate: Installed on 2015-10-08 (29 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  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/1514080/+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 1506139] Re: 15.10beta crashes encrypted swap partition

2015-11-07 Thread Hadmut Danisch
OK, I've finally found the problem(s). Was a bunch of little nasty
problems, that's why it was difficult to debug.


1)

The 15.10 beta installer had filled /etc/initramfs-tools/conf.d/resume
with

RESUME=UUID=a18e9ec9-1255-4dda-8298-8e10bdbe6835

which is never updated after first installation. Since I had to repair
the swap device several times, this was not correct anymore, and
furthermore /usr/share/initramfs-tools/hooks/cryptroot can't deal with
it. It's important that

RESUME=sda2_crypt

is entered.


2) That's why /usr/share/initramfs-tools/hooks/cryptroot did not mention the 
device in /conf/conf.d/cryptroot of the initramfs. 

Once it is correctly mentioned in this file (after fixing bug 1), the
password is fetched and the device is opened at the initramfs phase,
i.e. before systemd takes control.  This works well.


3) If sda2_crypt is not mentioned in the initramfs' /conf/conf.d/cryptroot, it 
is not opened while initramfs has control. But then, once systemd takes 
control, systemd tries to open it since it is listed in /etc/crypttab. 

But this does not work, since both systemd and plymouthd have bugs.
plymouthd can go into an endlesss loop or completey fail, depending
whether you have splash/graphical boot or textual.

Once bug 1 and 2 are solved, this issue does not occur anymore.


4) But then, system hangs while booting for another reason. systemd still tries 
to create a swap device and hangs forever. I could not reliably figure out why, 
but it looks as if it waits for systemd-cryptsetup for to do some things which 
it doesn't do since the crypt device is already open. 

Solution: remove the swap option in /etc/crypttab


5) Finally seems to work.


Just for the notes: systemd (and plymouth) is so buggy and intransparent
that it is far from beeing production-ready.

That cost me several evenings of work and headache.

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

Title:
  15.10beta crashes encrypted swap partition

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I 
experienced the problem that the swap is not activated at boot time and that 
/dev/disks/by-uuid does not contain a link to the swap partition, and the 
previously created luks-encrypted swap is destroyed after boot: It is not a 
luks partition anymore and filled with random (presumably encrypted) bytes 
without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab:
   sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
   sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+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 1511065] [NEW] systemd hangs while booting because unable to ask for password

2015-10-28 Thread Hadmut Danisch
Public bug reported:

Hi, this is a splitoff of bug #1506139

I'm usually using a setup with three partitions on a disk

Partition 1: plain ext4 boot partition mounted on /boot
Partition 2: luks-encrypted swap
Partition 3: luks-encrypted btrfs for / /home ...


but on one of my systems the boot process hangs at the point where it would ask 
for the password for the second time (first password prompt is for /-partition 
3, which works). 

Using the debug shell shows that a process like

/lib/systemd/systemd-cryptsetup attach sda2_crypt /dev/disk/by-id/ata-
SanDisk_SDSSDHII480G_*-part2 none luks,swap,discard is alive and has
send it's password-query to /run/systemd/ask-password/sck.*

but there is no process to listen for it and query for the password, so
it waits forever.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu9
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Oct 28 18:47:14 2015
InstallationDate: Installed on 2015-10-08 (19 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
MachineType: Medion G24
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=9b9831d9-62f5-4fe0-872a-704bd66d5f7f ro rootflags=subvol=@ nosplash
SourcePackage: systemd
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
dmi.product.name: G24
dmi.product.version: 1.0
dmi.sys.vendor: Medion

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


** Tags: amd64 apport-bug wily

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

Title:
  systemd hangs while booting because unable to ask for password

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi, this is a splitoff of bug #1506139

  I'm usually using a setup with three partitions on a disk

  Partition 1: plain ext4 boot partition mounted on /boot
  Partition 2: luks-encrypted swap
  Partition 3: luks-encrypted btrfs for / /home ...

  
  but on one of my systems the boot process hangs at the point where it would 
ask for the password for the second time (first password prompt is for 
/-partition 3, which works). 

  Using the debug shell shows that a process like

  /lib/systemd/systemd-cryptsetup attach sda2_crypt /dev/disk/by-id/ata-
  SanDisk_SDSSDHII480G_*-part2 none luks,swap,discard is alive and
  has send it's password-query to /run/systemd/ask-password/sck.*

  but there is no process to listen for it and query for the password,
  so it waits forever.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: systemd 225-1ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 28 18:47:14 2015
  InstallationDate: Installed on 2015-10-08 (19 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: Medion G24
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=9b9831d9-62f5-4fe0-872a-704bd66d5f7f ro rootflags=subvol=@ nosplash
  SourcePackage: systemd
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:
  dmi.product.name: G24
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1511065/+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 1506139] Re: 15.10beta crashes encrypted swap partition

2015-10-23 Thread Hadmut Danisch
More info from the source code of systemd-cryptsetup:


 else if (streq(option, "luks"))
arg_type = CRYPT_LUKS1;
...
 } else if (STR_IN_SET(option, "plain", "swap", "tmp"))
arg_type = CRYPT_PLAIN;


so the swap argument overwrites the luks argument and resets the ecryption type 
to plain. 


And indeed, when using

/lib/systemd/systemd-cryptsetup attach sda2_crypt /dev/sda2 none
swap,luks,discard


(i.e. just change the order of the parameters,  use   swap,luks,discard   
instead of  luks, swap, discard , as the ubuntu installer creates, it works and 
uses the luks partition correctly.

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

Title:
  15.10beta crashes encrypted swap partition

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I 
experienced the problem that the swap is not activated at boot time and that 
/dev/disks/by-uuid does not contain a link to the swap partition, and the 
previously created luks-encrypted swap is destroyed after boot: It is not a 
luks partition anymore and filled with random (presumably encrypted) bytes 
without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  crypttab:
   sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
   sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1506139/+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 1506139] Re: 15.10beta crashes encrypted swap partition

2015-10-23 Thread Hadmut Danisch
OK,

I have debugged this down and got big steps further in identifying the
problem.


An important step for debugging was to learn how to debug systemd. 

http://freedesktop.org/wiki/Software/systemd/Debugging/

was quite helpful, that

   systemctl enable debug-shell.service

helps a lot. After that, one can get a root shell when the systemd boot
process is hanging.


I have identified *two*  problems, both in 
/lib/systemd/systemd-cryptsetup



First problem:

The system boot procedure hangs because the process

/lib/systemd/systemd-cryptsetup attach sda2_crypt /dev/disk/by-id
/ata-SanDisk_SDSSDHII480G_**-part2 none  luks,swap,discard

hangs. It waits for password input, but for some reason it's prompt and
input don't make it their way to the boot console or boot splash prompt.
There's a problem with the procedure for requesting a password.

Killing that process from the debug console makes the boot process
continue immediately (of course without working swap).


Once knowing that this is the process causing trouble, debugging get's much 
easier, since it is not required anymore to try this within a boot process. You 
can use a running machine with any test partition for easy debugging. 

BTW: systemd does not use /etc/crypttab directly, but converts the
contents of /etc/crypttab to dynamically created units first, which can
be found under /run/systemd. It shows


ExecStart=/lib/systemd/systemd-cryptsetup attach 'sda2_crypt' 
'/dev/disk/by-id/ata-SanDisk_SDSSDHII480G_**-part2' 'none' 
'luks,swap,discard'
ExecStop=/lib/systemd/systemd-cryptsetup detach 'sda2_crypt'
ExecStartPost=/sbin/mkswap '/dev/mapper/sda2_crypt'


So one knows what happens right here. 


You can easily call the given command from anywhere as root with any partition, 
without the need to edit /etc/crypttab, because it's all command line 
parameters here. Makes testing pretty easy now. 



Second problem: 


That damned systemd-cryptsetup ignores luks (or is unable to cope with modern 
luks settings). 

That's what the dmsetup looks like for my root partition setup in the
initramfs:

0 903712768 crypt aes-xts-plain64

0 8:3 4096 1 allow_discards


This looks good, because it's the same crypt-parameters (aes-xts) as I used 
when creating the luks partition, and it uses an offset of 4096, allowing the 
luks header to remain untouched. 


But after running that systemd-cryptsetup for the sda2 partition (even
after freshly partitioning it with cryptsetup), dmtable shows that:


0 32616448 crypt aes-cbc-essiv:sha256 
 0 8:2 0 1 
allow_discards


which contains *two* wrong settings:

- it's the wrong cipher

- it's an offset of 0, which overwrites the luks header. That's why I am
seeing garbage again and again.




So it turns out that systemd-cryptsetup is tripple-buggy:

- Password dialog not working in boot process, neither in splash or non-
splash mode (that's why boot process hangs)

- wrong cipher

- no offset, thus overwriting the luks header.

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

Title:
  15.10beta crashes encrypted swap partition

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm usually using a setup with three partitions on a disk

  Partition 1:  plain ext4 boot partition mounted on  /boot
  Partition 2:  luks-encrypted swap
  Partition 3: luks-encrypted btrfs for /  /home ...

  both mentioned in /etc/crypttab like

  sda2_crypt UUID=a7976d5c-6191-436d-9cf9-2cedf17d0893 none luks,swap,discard
  sda3_crypt UUID=339b9a90-8292-422d-a3cf-eeb0317e9f84 none luks,discard

  
  With several machines I have installed 15.10 beta on and in several cases I 
experienced the problem that the swap is not activated at boot time and that 
/dev/disks/by-uuid does not contain a link to the swap partition, and the 
previously created luks-encrypted swap is destroyed after boot: It is not a 
luks partition anymore and filled with random (presumably encrypted) bytes 
without structure. 

  I first thought that this is a problem of the setup process, and
  repaired the swap manually. But then I found the partition destroyed
  again. This happend several times on several machines.

  I am not sure yet what exactly would destroy the partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cryptsetup 2:1.6.6-5ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct 14 18:12:58 2015
  InstallationDate: Installed on 2015-10-08 (5 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  

[Touch-packages] [Bug 1503590] XorgLogOld.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500078/+files/XorgLogOld.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] XorgLog.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500077/+files/XorgLog.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] xdpyinfo.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500080/+files/xdpyinfo.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] Re: Trouble with DisplayPort

2015-10-19 Thread Hadmut Danisch
> Hadmut Danisch, you didn't follow the instructions noted in


Why do you give instructions in reverse order and not in the order they have to 
be followed?

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-

[Touch-packages] [Bug 1503590] Re: Trouble with DisplayPort

2015-10-19 Thread Hadmut Danisch
apport information

** Tags added: ubuntu

** Description changed:

  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm having
  a Display with 2560x1600, and thus want to use with with DisplayPort for
  full resolution.
  
  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be connected
  to DisplayPort and are displayed as usual. But as soon as X starts,
  screen becomes black (and the screen itself somewhat confused, because
  it does not even respond to the menu button anymore). Interestingly, the
  same screen worked properly when connected with DisplayPort to another
  Linux machine with 14.04.
  
- Connecting the screen with HDMI instead works without any problems, but
- gives a reduced resolution of 1920x1080 only.
+ Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
+ --- 
+ ApportVersion: 2.19.1-0ubuntu2
+ Architecture: amd64
+ BootLog:
+  
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: wily
+ DistroRelease: Ubuntu 15.10
+ DistroVariant: ubuntu
+ DkmsStatus:
+  virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
+  virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
+ ExtraDebuggingInterest: Yes, if not too technical
+ GraphicsCard:
+  Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
+Subsystem: ASRock Incorporation Device [1849:22b1]
+ InstallationDate: Installed on 2015-09-03 (45 days ago)
+ InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
+ LightdmGreeterLog:
+  ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
+  Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
+ LightdmGreeterLogOld:
+  ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
+  ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
+  upstart: indicator-application main process (1537) killed by TERM signal
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
+  Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
+  Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: xorg 1:7.7+7ubuntu4
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
+ Tags:  wily ubuntu
+ UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
+ Uname: Linux 4.2.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
+ _MarkForUpload: True
+ dmi.bios.date: 07/16/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: P1.10
+ dmi.board.name: N3150-NUC
+ dmi.board.vendor: ASRock
+ dmi.chassis.asset.tag: To Be Filled By O.E.M.
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: To Be Filled By O.E.M.
+ dmi.chassis.version: To Be Filled By O.E.M.
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
+ dmi.product.name: To Be Filled By O.E.M.
+ dmi.product.version: To Be Filled By O.E.M.
+ dmi.sys.vendor: To Be Filled By O.E.M.
+ version.compiz: compiz N/A
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.64-1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
+ version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
+ version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1503590] ProcEnviron.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500073/+files/ProcEnviron.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] ProcInterrupts.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500074/+files/ProcInterrupts.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] xserver.devices.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "xserver.devices.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500081/+files/xserver.devices.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1503590] Dependencies.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500066/+files/Dependencies.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] DpkgLog.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500067/+files/DpkgLog.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] ProcCpuinfo.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500072/+files/ProcCpuinfo.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] ProcModules.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500075/+files/ProcModules.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] JournalErrors.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500068/+files/JournalErrors.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] Xrandr.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1503590/+attachment/4500079/+files/Xrandr.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] UdevDb.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1503590/+attachment/4500076/+files/UdevDb.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] LightdmLog.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500070/+files/LightdmLog.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1503590] Lspci.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1503590/+attachment/4500071/+files/Lspci.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
 

[Touch-packages] [Bug 1503590] LightdmDisplayLog.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4500069/+files/LightdmDisplayLog.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems, but gives 
a reduced resolution of 1920x1080 only.
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.4, 4.2.0-14-generic, x86_64: installed
   virtualbox, 5.0.4, 4.2.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:22b1] (rev 21) (prog-if 00 [VGA controller])
 Subsystem: ASRock Incorporation Device [1849:22b1]
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  LightdmGreeterLog:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   Invalid MIT-MAGIC-COOKIE-1 keyupstart: indicator-application main process 
(1991) killed by TERM signal
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1537) killed by TERM signal
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
   Bus 001 Device 002: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=UUID=881c90c8-ac82-4df6-98d7-83045b0f9c1b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily ubuntu
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd07/16/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1503590] Re: Trouble with DisplayPort

2015-10-19 Thread Hadmut Danisch
apport information

** Tags added: apport-collected

** Description changed:

  Hi,
  
  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm having
  a Display with 2560x1600, and thus want to use with with DisplayPort for
  full resolution.
  
  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be connected
  to DisplayPort and are displayed as usual. But as soon as X starts,
  screen becomes black (and the screen itself somewhat confused, because
  it does not even respond to the menu button anymore). Interestingly, the
  same screen worked properly when connected with DisplayPort to another
  Linux machine with 14.04.
  
  Connecting the screen with HDMI instead works without any problems, but
  gives a reduced resolution of 1920x1080 only.
  
  regards
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 10:01:31 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.19.1-0ubuntu2
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 15.10
+ InstallationDate: Installed on 2015-09-03 (45 days ago)
+ InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
+ Package: xorg 1:7.7+7ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
+ Tags:  wily
+ Uname: Linux 4.2.0-16-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4499980/+files/Dependencies.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems,
  but gives a reduced resolution of 1920x1080 only.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 10:01:31 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1503590/+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 1503590] ProcEnviron.txt

2015-10-19 Thread Hadmut Danisch
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1503590/+attachment/4499982/+files/ProcEnviron.txt

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

Title:
  Trouble with DisplayPort

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I've installed 15.10 beta on a brand new ASRock beebox N3150 PC. This
  device has three display connectors, 1x DisplayPort, 2xHDMI. I'm
  having a Display with 2560x1600, and thus want to use with with
  DisplayPort for full resolution.

  When connecting screen and PC with DisplayPort, both the BIOS and the
  Linux BootSplash/Console correctly recognize the screen to be
  connected to DisplayPort and are displayed as usual. But as soon as X
  starts, screen becomes black (and the screen itself somewhat confused,
  because it does not even respond to the menu button anymore).
  Interestingly, the same screen worked properly when connected with
  DisplayPort to another Linux machine with 14.04.

  Connecting the screen with HDMI instead works without any problems,
  but gives a reduced resolution of 1920x1080 only.

  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Oct  7 10:01:31 2015
  InstallationDate: Installed on 2015-09-03 (33 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-03 (45 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825)
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Tags:  wily
  Uname: Linux 4.2.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare scanner sudo 
video www-data
  _MarkForUpload: True

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


  1   2   >