from:"russianneuromancer"

Add Linux as affected package as known workaround require changing
kernel build configuration (unset CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT).

** Summary changed:

- [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on 
Dell Venue 11 Pro 7140
+ [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works 
on Dell Venue 11 Pro 7140

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:

[Touch-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140

** Attachment added: "Linux 5.3.1 with CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT=y"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846539/+attachment/5294053/+files/dmesg_sof

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  irina   818 F pulseaudio
   /dev/snd/controlC0:  irina   818 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct

[Touch-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback stop working on Dell Venue 11 Pro 7140

** Attachment added: "Linux 5.3.1 without CONFIG_SND_SOC_SOF_BROADWELL_SUPPORT"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846539/+attachment/5294054/+files/dmesg_no_sof

** Bug watch added: Linux Kernel Bug Tracker #205083
   https://bugzilla.kernel.org/show_bug.cgi?id=205083

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=205083
   Importance: Unknown
   Status: Unknown

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Unknown
Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu

[Touch-packages] [Bug 1846539] [NEW] [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

Public bug reported:

Hello!

I noticed that since Linux 5.2rc2 audio playback no longer works on Dell
Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened
because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary
builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.2-rc2/

To verify this assumption I tested two builds of Linux 5.3.1.
1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

Audio playback doesn't work, dmesg:
[4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
[4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
[4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin 
not available(-2)
[4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback 
FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
[4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
[4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 
Pin mapping ok
[4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 
Pin mapping ok
[4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback 
Pin mapping ok
[4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
[4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
[7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
[   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still 
running
[   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still 
running
[   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
[   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

Audio playback works, dmesg:
[4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
[4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin 
not available(-2)
[4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback 
FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
[4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
[4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
[4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 
Pin mapping ok
[4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 
Pin mapping ok
[4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback 
Pin mapping ok
[4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
[4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  irina   818 F pulseaudio
 /dev/snd/controlC0:  irina   818 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Oct  4 01:22:54 2019
InstallationDate: Installed on 2019-02-12 (233 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:broadwellrt286 
failed
Symptom_AlsaPlaybackTestStderr:
 W r i t e   e r r o r :   - 5 , I n p u t / o u t p u t   e r r o r 
  x r u n _ r e c o v e r y   f a i l e d :   - 5 , I n p u t / o u t p u t   e 
r r o r 
  T r a n s f e r   f a i l e d :   I n p u t / o u t p u t   e r r o r
Symptom_Card: Встроенное

[Touch-packages] [Bug 1563110]

2019-01-25 Thread russianneuromancer

> Or do we have to compile it ourselves from this branch?

There is prebuilt packages, if you need them:
https://github.com/heikomat/linux/releases

By the way, is UCM from Comment 68 is recent, or there is newer version
somewhere?

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 606579] Re: Digital output has a higher priority than analog output

2018-09-17 Thread RussianNeuroMancer

Lenovo Y550P-4CWI is not available anymore, so I re-verified this issue
on another laptop - Acer Aspire 7560G (Radeon HD 6620G+6650M). This time
I tested with Kubuntu 18,10 daily image, instead of Kubuntu 17.10.

With Radeon driver digital output is disabled by default, so audio goes
to internal audio adapter. Also when I enabled HDMI output manually in
System Settings, it priority remain below internal audio adapter which
is desired behaviour.

Unfortunately, I can no longer verify if issue is present with nouveau,
but let's hope it's fixed there too. For the time being, I close this
report.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Digital output has a higher priority than analog output

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: phonon

  Digital output (nVidia GT216M HDMI) has a higher priority than analog output 
(hda_codec: ALC272) in Ubuntu Maverick. 
  In result after boot LiveCD/DVD on laptop (Lenovo Y550P-4CWI) user not hear 
any sound.

  Analog outputs should have higher priority by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/606579/+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 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal

** Description changed:

  Hello!
  
- I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
- text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
- running program. This happen even when I do this inside virt-viewer
- connection to virtual machine.
+ I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text 
with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for running 
program. This happen even when I do this inside virt-viewer connection to 
virtual machine.
+ Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work.
  
  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it was
  pressed as separate buttong) which interrupt text typing. Issue is not
  reproducible if user press Shift first, however many people used to hold
  Alt first and then press Shift.

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under
  Wayland session of Gnome Shell cause Ctrl+C interrupt for program
  running under Gnome Terminal

Status in gnome-shell package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text 
with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for running 
program. This happen even when I do this inside virt-viewer connection to 
virtual machine.
  Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+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 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal

** Summary changed:

- Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C 
interrupt for running program 
+ Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under 
Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under 
Gnome Terminal

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under
  Wayland session of Gnome Shell cause Ctrl+C interrupt for program
  running under Gnome Terminal

Status in gnome-shell package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
  text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
  running program. This happen even when I do this inside virt-viewer
  connection to virtual machine.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+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 1789645] [NEW] Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C interrupt for running program

Public bug reported:

Hello!

I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
running program. This happen even when I do this inside virt-viewer
connection to virtual machine.

A also find that switch keyboard layout with default Alt+Shift cause
Opera display it's menu (seems like this is reaction to Alt like it was
pressed as separate buttong) which interrupt text typing. Issue is not
reproducible if user press Shift first, however many people used to hold
Alt first and then press Shift.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C
  interrupt for running program

Status in gnome-shell package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
  text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
  running program. This happen even when I do this inside virt-viewer
  connection to virtual machine.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789645/+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 1789644] [NEW] Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached

Public bug reported:

Hello!

In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for me
back to GDM3 when I close warning message that appear on Evolution
3.29.90 (window that inform user that he is running unstable version of
Evolution). Seems like this happen only if external display attached.

Dell Latitude 7285
Dock: Belkin USB-C Express Dock 3.1 HD F4U093
External display: Dell UP3017

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: wayland
   Importance: Undecided
   Status: New

** No longer affects: wayland

** Also affects: wayland (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if
  external display attached

Status in gnome-shell package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  New

Bug description:
  Hello!

  In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for
  me back to GDM3 when I close warning message that appear on Evolution
  3.29.90 (window that inform user that he is running unstable version
  of Evolution). Seems like this happen only if external display
  attached.

  Dell Latitude 7285
  Dock: Belkin USB-C Express Dock 3.1 HD F4U093
  External display: Dell UP3017

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1789644/+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 1773167]

2018-06-25 Thread RussianNeuroMancer

> What does the EDID contain when there is an HDMI output but cable is
not plugged in?

On devices with physical HDMI output get-edid return nothing (because no 
devices HDMI is attached).
On devices without HDMI output, such as Lenovo Miix2 8, EDID contain this:

[5.431895] i915 :00:02.0: HDMI-A-2: EDID is invalid:
[5.431902]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431904]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431906]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431908]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431910]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431912]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431914]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[5.431916]  [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

> It would seem more appropriate to do that already in the kernel,
though.

So I should fill separate report here, at freedesktop, or at kernel's
bugzilla? Which component I should choice?

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

Title:
  [Intel HDMI LPE driver] Audio is not working; pulseaudio consumes 100%
  of a single CPU core

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  On a krez ninja 1103 laptop audio is not working; pulseaudio consumes
  100% of a single CPU core. Pulseaudio log atached.

  According to perf, most CPU is consumed at __memset_erms.

  Below is the GDB stacktrace of pulseaudio.

  # gdb -p 1009 -batch -eval-command="thread apply all bt"
  [New LWP 1028]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, 
expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  205   ../sysdeps/unix/sysv/linux/futex-internal.h: No such file or directory.

  Thread 2 (Thread 0x7fe2a7458700 (LWP 1028)):
  #0  0x7fe2ab063339 in _IO_str_init_static_internal 
(sf=sf@entry=0x7fe2a7453700, ptr=ptr@entry=0x7fe2a7453b80 "", 
size=size@entry=255, pstart=pstart@entry=0x7fe2a7453b80 "") at strops.c:36
  #1  0x7fe2ab10515b in ___vsnprintf_chk (s=0x7fe2a7453b80 "", 
maxlen=, flags=1, slen=, format=0x7fe2ac698e8d 
"%s%c: %s", args=0x7fe2a74538a0) at vsnprintf_chk.c:62
  #2  0x7fe2ac6601ca in pa_vsnprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #3  0x7fe2ac660366 in pa_snprintf () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac66bda8 in pa_log_levelv_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #5  0x7fe2ac66b655 in pa_log_level_meta () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #6  0x7fe2a52b36ae in ?? () from 
/usr/lib/pulse-11.1/modules/libalsa-util.so
  #7  0x7fe2ac68c2a8 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #8  0x7fe2abb756db in start_thread (arg=0x7fe2a7458700) at 
pthread_create.c:463
  #9  0x7fe2ab0f488f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

  Thread 1 (Thread 0x7fe2acfe7500 (LWP 1009)):
  #0  0x7fe2abb7e6d6 in futex_abstimed_wait_cancelable (private=0, 
abstime=0x0, expected=0, futex_word=0x56318e574a30) at 
../sysdeps/unix/sysv/linux/futex-internal.h:205
  #1  do_futex_wait (sem=sem@entry=0x56318e574a30, abstime=0x0) at 
sem_waitcommon.c:111
  #2  0x7fe2abb7e7c8 in __new_sem_wait_slow (sem=0x56318e574a30, 
abstime=0x0) at sem_waitcommon.c:181
  #3  0x7fe2ac68c502 in pa_semaphore_wait () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #4  0x7fe2ac8cca24 in pa_asyncmsgq_send () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-11.1.so
  #5  0x7fe2a6841119 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #6  0x7fe2ac675ee2 in pa_pdispatch_run () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #7  0x7fe2a6844695 in ?? () from 
/usr/lib/pulse-11.1/modules/libprotocol-native.so
  #8  0x7fe2ac678bef in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #9  0x7fe2ac67b6ab in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #10 0x7fe2ac67ba49 in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #11 0x7fe2ac67c2cf in ?? () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
  #12 0x7fe2ac40e0d8 in pa_mainloop_dispatch () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #13 0x7fe2ac40e4ae in pa_mainloop_iterate () from 
/usr/lib/x86_64-linux-gnu/libpulse.so.0
  #14 0x7fe2ac40e530 in pa_mainloop_run () from

[Touch-packages] [Bug 1326954]

In addition to Dell Venue 8 Pro 5855 tablet with Dell Wireless 5809e
(Comment 13) I find same issue reproducible on Dell Wireless 5810e
(Telit LN930 with 1620 firmware) with patch from Comment 23.

I also find that detach/attach modem via systemd unit is sufficient,
ModemManager restart seems like not necessary.

Aleksander, please let us know if any additional logs or testing is
required.

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   |

[Touch-packages] [Bug 1326954]

Created attachment 134822
ModemManagerHook.service

I also need to mention that workaround from Commentary 16 later was
modified to not only restart ModemManager, but also detach modem before
suspend, and reattach it after suspend.

systemd unit is attached.

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin:

[Touch-packages] [Bug 1326954]

Created attachment 134821
ModemManager 1.6.8, patched, suspend->resume cycle

I was able to test it kind of ahead of time, and unfortunately this
doesn't help. Log attached.

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports:

[Touch-packages] [Bug 1326954]

Thanks you once again :)

Yes, with this patch build was successful. I will test it next week and
will let you know.

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-

[Touch-packages] [Bug 1326954]

> Could you apply the patch in a custom build and retry, to see if it
fixes your issue?

Hello!

Thank you for looking into this issue! :)

I tried to build version 1.6.8, but build failed: 
https://launchpad.net/~russianneuromancer/+archive/ubuntu/drivers/+build/13571525
 

It is supposed to work with version 1.6.8 or I need master? (In latter
case I have no idea how to build modemmanager package.)

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  <<<<<< RAW:
  <<<<<<   length = 16
  <<<<<<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  <<<<<< Header:
  <<<<<<   length  = 16
  <<<<<<   type= open (0x0001)
  <<<<<<   transaction = 1
  <<<<<< Contents:
  <<<<<<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >>>>>> RAW:
  >>>>>>   length = 16
  >>>>>>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  <<<<<< RAW:
  <<<<<<   length = 12
  <<<<<<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  <<<<<< Header:
  <<<<<<   length  = 12
  <<<<<<   type= close (0x0002)
  <<<<<<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >>>>>> RAW:
  >>>>>>   length = 16
  >>>>>>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/f

[Touch-packages] [Bug 1326954]

I wonder if the fact that I use "suspend freeze" mode instead of default 
"suspend" mode makes a difference?
https://www.freedesktop.org/software/systemd/man/sleep.conf.d.html

I have to do so because modern hardware implement S0i3 instead of S3, so
default mode will just won't work (tablets and laptops without S3
support will just poweroff or reboot on attempt to go into S3).

> I'll analyze the logs and let you know what I find.

Ok. Just to let you know, I find first unit not reliable enough, so I edited it 
a little bit:
Removed "StopWhenUnneeded=yes" and "RemainAfterExit=yes".
Replaced "=-/bin/systemctl" with "=/bin/systemctl".

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM

[Touch-packages] [Bug 1326954]

Hi

Any news?

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'
-
Status   |   lock:

[Touch-packages] [Bug 1326954]

Created attachment 130975
ModemManager (suspend -> wakeup) from EM7305

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'

[Touch-packages] [Bug 1326954]

I have same issue on Dell Venue 8 Pro 5855 tablet with Dell Wireless
5809e (Sierra Wireless AirPrime EM7305; default SWI9X15C_05.05.58.00
firmware).

Please look into attached logs:
4:26 mbim-proxy and ModemManager proxy is started, then tablet was suspended
4:27 wakeup from suspended, connection is not established
4:28 second attempt to connect, also unsuccessful. 

mbim-proxy and ModemManager termination and following restart allowed me
to successfully establish connection again.

If my issue is different and I need to fill separate bugreport - please
let me know.

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'

[Touch-packages] [Bug 1326954]

Created attachment 130974
mbim-proxy log (suspend -> wakeup) from EM7305

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'
-
System   | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6'
 |drivers: 'cdc_mbim'
 | plugin: 'Generic'
 |   primary port: 'cdc-wdm0'
 |  ports: 'cdc-wdm0 (mbim), wwan0 (net)'
-
Numbers  |   own : 'unknown'

[Touch-packages] [Bug 1326954]

And in case it could help someone, this workaround systemd unit helps
me. With this unit connection could be established after suspend.

/etc/systemd/system/ModemManagerHook.service:

[Unit]
Description=ModemManager sleep hook
Before=sleep.target
StopWhenUnneeded=yes

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=-/bin/systemctl stop ModemManager
ExecStop=-/bin/systemctl start ModemManager

[Install]
WantedBy=sleep.target

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

Title:
  Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after
  suspend/hibernate

Status in ModemManager:
  Unknown
Status in libmbim package in Ubuntu:
  Confirmed
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1

  Card: Sierra Wireless EM7305 (PCI Express M.2 form factor)

  Expected: Sierra plugin is used
  Happens: Generic plugin is used instead

  After cold start the card seems to work almost fine, but does not come
  back after suspend or hibernate. At least after hibernate MM may go
  into a tight loop consuming 100% CPU.

  MM debug log output (full log attached):

   [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): 
(Plugin Manager) [wwan0] Found '1' plugins to try...
   [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): 
(Plugin Manager) [wwan0]   Will try with plugin 'Generic'
   [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992536.132687] [mm-plugin-manager.c:505] 
plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check 
until result suggested
   [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): 
(usbmisc/cdc-wdm0) probing MBIM...
   [1401992538.202591] [mm-plugin-manager.c:646] 
min_probing_timeout_cb(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed
  [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent 
message...
  << RAW:
  <<   length = 16
  <<   data   = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 16
  <<   type= open (0x0001)
  <<   transaction = 1
  << Contents:
  <<   max_control_transfer = 4096
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00
   [1401992539.481429] [mm-port-probe.c:300] 
mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable
  [/dev/cdc-wdm0] Sent message...
  << RAW:
  <<   length = 12
  <<   data   = 02:00:00:00:0C:00:00:00:02:00:00:00
  [/dev/cdc-wdm0] Sent message (translated)...
  << Header:
  <<   length  = 12
  <<   type= close (0x0002)
  <<   transaction = 2
  [/dev/cdc-wdm0] Received message...
  >> RAW:
  >>   length = 16
  >>   data   = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00
   [1401992539.545529] [mm-plugin-manager.c:417] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best 
plugin for port
   [1401992539.549361] [mm-plugin-manager.c:334] 
suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task 
completed, got suggested plugin
   [1401992539.553247] [mm-plugin-manager.c:274] 
port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, 
still 1 running probes in this device (wwan0)
   [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): 
(Generic) [wwan0] probing deferred until result suggested
   [1401992539.560690] [mm-plugin-manager.c:485] 
plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task 
completed, got suggested plugin
   [1401992539.564175] [mm-plugin-manager.c:285] 
port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, 
last one in device
   [1401992539.567868] [mm-plugin-manager.c:107] 
find_device_support_context_complete_and_free(): (Plugin Manager) 
[/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished 
in '3.677528' seconds
[1401992539.571611] [mm-device.c:486] mm_device_create_modem(): 
Creating modem with plugin 'Generic' and '2' ports
   [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): 
MBIM-powered generic modem found...

  mmcli output:

  /org/freedesktop/ModemManager1/Modem/0 (device id 
'b3a77501ed8da196baa804a4142ff280766f6f98')
-
Hardware |   manufacturer: 'Generic'
 |  model: 'MBIM [1199:9063]'
 |   revision: 'SWI9X15C_01.12'
 |  supported: 'gsm-umts, lte'
 |current: 'gsm-umts, lte'
 |   equipment id: '356906050069168'

[Touch-packages] [Bug 606579] Re: Digital output has a higher priority than analog output

2017-10-09 Thread RussianNeuroMancer

Issue is still reproducible.

** Changed in: pulseaudio (Ubuntu)
   Status: Expired => New

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

Title:
  Digital output has a higher priority than analog output

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Binary package hint: phonon

  Digital output (nVidia GT216M HDMI) has a higher priority than analog output 
(hda_codec: ALC272) in Ubuntu Maverick. 
  In result after boot LiveCD/DVD on laptop (Lenovo Y550P-4CWI) user not hear 
any sound.

  Analog outputs should have higher priority by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/606579/+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 1719038] Re: X Server crashes during log in VM starting from Kubuntu 16.04.2

2017-09-24 Thread RussianNeuroMancer

** Tags added: regression-release

** Tags added: artful zesty

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

Title:
  X Server crashes during log in VM starting from Kubuntu 16.04.2

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+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 1719038] Re: X Server crashes during login in VM 16.04.3

2017-09-22 Thread RussianNeuroMancer

** Bug watch added: freedesktop.org Bugzilla #102554
   https://bugs.freedesktop.org/show_bug.cgi?id=102554

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=102554
   Importance: Unknown
   Status: Unknown

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

Title:
  X Server crashes during login in VM 16.04.3

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+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 1679727] Re: Don't attempt to create devices in lx-brand containers

2017-06-02 Thread RussianNeuroMancer

Check comment #4

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

Title:
  Don't attempt to create devices in lx-brand containers

Status in makedev package in Ubuntu:
  Confirmed

Bug description:
  This is a similar issue to
  https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163

  In a Joyent lx-brand container environment an upgrade of the makedev
  package fails at the post-installation script:

  # apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ...
  mknod: ‘mem-’: Operation not permitted
  makedev mem c 1 1 root kmem 0640: failed
  mknod: ‘kmem-’: Operation not permitted
  makedev kmem c 1 2 root kmem 0640: failed
  mknod: ‘null-’: Operation not permitted
  makedev null c 1 3 root root 0666: failed
  mknod: ‘port-’: Operation not permitted
  makedev port c 1 4 root kmem 0640: failed
  mknod: ‘zero-’: Operation not permitted
  makedev zero c 1 5 root root 0666: failed
  mknod: ‘full-’: Operation not permitted
  makedev full c 1 7 root root 0666: failed
  mknod: ‘random-’: Operation not permitted
  makedev random c 1 8 root root 0666: failed
  mknod: ‘urandom-’: Operation not permitted
  makedev urandom c 1 9 root root 0666: failed
  mknod: ‘tty-’: Operation not permitted
  makedev tty c 5 0 root tty 0666: failed
  mknod: ‘ram0-’: Operation not permitted
  makedev ram0 b 1 0 root disk 0660: failed
  mknod: ‘ram1-’: Operation not permitted
  makedev ram1 b 1 1 root disk 0660: failed
  mknod: ‘ram2-’: Operation not permitted
  makedev ram2 b 1 2 root disk 0660: failed
  mknod: ‘ram3-’: Operation not permitted
  makedev ram3 b 1 3 root disk 0660: failed
  mknod: ‘ram4-’: Operation not permitted
  makedev ram4 b 1 4 root disk 0660: failed
  mknod: ‘ram5-’: Operation not permitted
  makedev ram5 b 1 5 root disk 0660: failed
  mknod: ‘ram6-’: Operation not permitted
  makedev ram6 b 1 6 root disk 0660: failed
  mknod: ‘ram7-’: Operation not permitted
  makedev ram7 b 1 7 root disk 0660: failed
  mknod: ‘ram8-’: Operation not permitted
  makedev ram8 b 1 8 root disk 0660: failed
  mknod: ‘ram9-’: Operation not permitted
  makedev ram9 b 1 9 root disk 0660: failed
  mknod: ‘ram10-’: Operation not permitted
  makedev ram10 b 1 10 root disk 0660: failed
  mknod: ‘ram11-’: Operation not permitted
  makedev ram11 b 1 11 root disk 0660: failed
  mknod: ‘ram12-’: Operation not permitted
  makedev ram12 b 1 12 root disk 0660: failed
  mknod: ‘ram13-’: Operation not permitted
  makedev ram13 b 1 13 root disk 0660: failed
  mknod: ‘ram14-’: Operation not permitted
  makedev ram14 b 1 14 root disk 0660: failed
  mknod: ‘ram15-’: Operation not permitted
  makedev ram15 b 1 15 root disk 0660: failed
  mknod: ‘ram16-’: Operation not permitted
  makedev ram16 b 1 16 root disk 0660: failed
  mknod: ‘loop0-’: Operation not permitted
  makedev loop0 b 7 0 root disk 0660: failed
  mknod: ‘loop1-’: Operation not permitted
  makedev loop1 b 7 1 root disk 0660: failed
  mknod: ‘loop2-’: Operation not permitted
  makedev loop2 b 7 2 root disk 0660: failed
  mknod: ‘loop3-’: Operation not permitted
  makedev loop3 b 7 3 root disk 0660: failed
  mknod: ‘loop4-’: Operation not permitted
  makedev loop4 b 7 4 root disk 0660: failed
  mknod: ‘loop5-’: Operation not permitted
  makedev loop5 b 7 5 root disk 0660: failed
  mknod: ‘loop6-’: Operation not permitted
  makedev loop6 b 7 6 root disk 0660: failed
  mknod: ‘loop7-’: Operation not permitted
  makedev loop7 b 7 7 root disk 0660: failed
  mknod: ‘tty0-’: Operation not permitted
  makedev tty0 c 4 0 root tty 0600: failed
  mknod: ‘console-’: Operation not permitted
  makedev console c 5 1 root tty 0600: failed
  ln: failed to create symbolic link ‘fd/fd’: Function not implemented
  ln: failed to create symbolic link ‘stdin’: File exists
  ln: failed to create symbolic link ‘stdout’: File exists
  ln: failed to create symbolic link ‘stderr’: File exists
  /sbin/MAKEDEV: don't know how to make device "tty0"
  dpkg: error processing package makedev (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   makedev
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  The workaround is similar to 1675163 except in this case the post-
  installation script should check for "container=zone" in
  '/proc/1/environ':

  
  if grep -q container=zone /proc/1/environ
  then
  echo "lx-brand container detected."
  exit 0
  fi

To manage notifications about this bug go to:

[Touch-packages] [Bug 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container

2017-05-20 Thread RussianNeuroMancer

https://github.com/systemd/systemd/issues/5900#issuecomment-300362005

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  New
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup when I check permission from within nspawn
  container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

2017-05-12 Thread RussianNeuroMancer

So after all nobody reported this to bugs.freedesktop.org?

I also guess there is few different issues in this bugreport, so I think
it's good idea to fill separate bugreport on bugs.freedesktop.org if you
have very different symptoms.

How to fill bugreport to bugs.freedesktop.org: 
https://01.org/linuxgraphics/documentation/how-report-bugs
drm-tip kernel is here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+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 1688689] Re: Owner and group of few files and folders from Bind directory visible as nobody/nogroup within nspawn container

Example:

~$ LANG=C sudo whoami
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
~$ LANG=C ls -l /usr/bin/sudo
-rwsr-xr-x 1 nobody nogroup 140944 Jan 14 07:41 /usr/bin/sudo
~$ LANG=C ls -l /var/lib/machines/builder/usr/bin/sudo
-rwsr-xr-x 1 root root 140944 Jan 14 07:41 
/var/lib/machines/builder/usr/bin/sudo


** Summary changed:

- Owner and group of few folders from Bind directory visible as nobody/nogroup 
within nspawn container 
+ Owner and group of few files and folders from Bind directory visible as 
nobody/nogroup within nspawn container

** Description changed:

- Owner and group of few folders from Bind directory visible as
+ Owner and group of few files and folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.
  
  Create testing.nspawn:
  
  [Files]
  Bind=/patch/to/folder
- Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.
+ Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.
  
  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup when I check permission from within nspawn
  container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders and files in Bind directory inside container is the 
same as on host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+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 1688689] Re: Owner and group of few folders from Bind directory visible as nobody/nogroup within nspawn container

Issue is also reproducible for files and folder within container, if
container is btrfs subvolume instead of disk image.

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

Title:
  Owner and group of few files and folders from Bind directory visible
  as nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+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 1688689] [NEW] Owner and group of few folders from Bind directory visible as nobody/nogroup within nspawn container

Public bug reported:

Owner and group of few folders from Bind directory visible as
nobody/nogroup when I check permission from within nspawn container.

Create testing.nspawn:

[Files]
Bind=/patch/to/folder
Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
Server 17.10 (systemd 233).

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/systemd/systemd/issues #5900
   https://github.com/systemd/systemd/issues/5900

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/5900
   Importance: Unknown
   Status: Unknown

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

Title:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup within nspawn container

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  Owner and group of few folders from Bind directory visible as
  nobody/nogroup when I check permission from within nspawn container.

  Create testing.nspawn:

  [Files]
  Bind=/patch/to/folder
  Use some folder with many subfolders, to expand the test coverage. Check if 
owners of all subfolders in Bind directory inside container is the same as on 
host.

  Issue is reproducible in Ubuntu Server 17.04 (systemd 232) and Ubuntu
  Server 17.10 (systemd 233).

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1688689/+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 1129402] Re: makedev installation fails in linux-vserver

Try this:
https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1679727/comments/4

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

Title:
  makedev installation fails in linux-vserver

Status in makedev package in Ubuntu:
  Confirmed

Bug description:
  After upgrading a server, which is running in a linux-vserver
  container on kernel 2.6.32-5-vserver-amd64, from Ubuntu 12.04 to
  12.10, I'm having problems with the "makedev" package: Because
  containers do not have permission to change host console devices, the
  installation fails and the package stays in a "not fully installed"
  state. This, in turn, causes the "ubuntu-minimal" package installation
  to fail.

  The package cannot be removed, because other packages such as
  "upstart" depend on it. Therefore, makedev should either be
  uninstallable or ignore permission errors when being installed in a
  vserver.

  
  Output of apt-get install:

  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  2 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue [Y/n]?
  Setting up makedev (2.3.1-91ubuntu2) ...
  mknod: `mem-': Operation not permitted
  makedev mem c 1 1 root kmem 0640: failed
  mknod: `kmem-': Operation not permitted
  makedev kmem c 1 2 root kmem 0640: failed
  mknod: `null-': Operation not permitted
  makedev null c 1 3 root root 0666: failed
  mknod: `port-': Operation not permitted
  makedev port c 1 4 root kmem 0640: failed
  mknod: `zero-': Operation not permitted
  makedev zero c 1 5 root root 0666: failed
  mknod: `full-': Operation not permitted
  makedev full c 1 7 root root 0666: failed
  mknod: `random-': Operation not permitted
  makedev random c 1 8 root root 0666: failed
  mknod: `urandom-': Operation not permitted
  makedev urandom c 1 9 root root 0666: failed
  mknod: `tty-': Operation not permitted
  makedev tty c 5 0 root tty 0666: failed
  mknod: `ram0-': Operation not permitted
  makedev ram0 b 1 0 root disk 0660: failed
  mknod: `ram1-': Operation not permitted
  makedev ram1 b 1 1 root disk 0660: failed
  mknod: `ram2-': Operation not permitted
  makedev ram2 b 1 2 root disk 0660: failed
  mknod: `ram3-': Operation not permitted
  makedev ram3 b 1 3 root disk 0660: failed
  mknod: `ram4-': Operation not permitted
  makedev ram4 b 1 4 root disk 0660: failed
  mknod: `ram5-': Operation not permitted
  makedev ram5 b 1 5 root disk 0660: failed
  mknod: `ram6-': Operation not permitted
  makedev ram6 b 1 6 root disk 0660: failed
  mknod: `ram7-': Operation not permitted
  makedev ram7 b 1 7 root disk 0660: failed
  mknod: `ram8-': Operation not permitted
  makedev ram8 b 1 8 root disk 0660: failed
  mknod: `ram9-': Operation not permitted
  makedev ram9 b 1 9 root disk 0660: failed
  mknod: `ram10-': Operation not permitted
  makedev ram10 b 1 10 root disk 0660: failed
  mknod: `ram11-': Operation not permitted
  makedev ram11 b 1 11 root disk 0660: failed
  mknod: `ram12-': Operation not permitted
  makedev ram12 b 1 12 root disk 0660: failed
  mknod: `ram13-': Operation not permitted
  makedev ram13 b 1 13 root disk 0660: failed
  mknod: `ram14-': Operation not permitted
  makedev ram14 b 1 14 root disk 0660: failed
  mknod: `ram15-': Operation not permitted
  makedev ram15 b 1 15 root disk 0660: failed
  mknod: `ram16-': Operation not permitted
  makedev ram16 b 1 16 root disk 0660: failed
  mknod: `loop0-': Operation not permitted
  makedev loop0 b 7 0 root disk 0660: failed
  mknod: `loop1-': Operation not permitted
  makedev loop1 b 7 1 root disk 0660: failed
  mknod: `loop2-': Operation not permitted
  makedev loop2 b 7 2 root disk 0660: failed
  mknod: `loop3-': Operation not permitted
  makedev loop3 b 7 3 root disk 0660: failed
  mknod: `loop4-': Operation not permitted
  makedev loop4 b 7 4 root disk 0660: failed
  mknod: `loop5-': Operation not permitted
  makedev loop5 b 7 5 root disk 0660: failed
  mknod: `loop6-': Operation not permitted
  makedev loop6 b 7 6 root disk 0660: failed
  mknod: `loop7-': Operation not permitted
  makedev loop7 b 7 7 root disk 0660: failed
  mknod: `tty0-': Operation not permitted
  makedev tty0 c 4 0 root tty 0600: failed
  mknod: `console-': Operation not permitted
  makedev console c 5 1 root tty 0600: failed
  /sbin/MAKEDEV: don't know how to make device "tty0"
  dpkg: error processing makedev (--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of ubuntu-minimal:
   ubuntu-minimal depends on makedev; however:
Package makedev is not configured yet.

  dpkg: error processing ubuntu-minimal (--configure):
   dependency problems - leaving unconfigured
  Errors were encountered

[Touch-packages] [Bug 1679727] Re: Don't attempt to create devices in lx-brand containers

I published fixed package: https://yadi.sk/d/_vXq0WdR3HgbTJ

I replaced LXC detection with following condition:

# don't stomp on container users
if [ "$(systemd-detect-virt -c)" != "none" ] 
then
echo "Container detected, aborting."
exit 0
fi

But I don't know if this good solution. Anyone from Canonical can check
this?

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

Title:
  Don't attempt to create devices in lx-brand containers

Status in makedev package in Ubuntu:
  Confirmed

Bug description:
  This is a similar issue to
  https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163

  In a Joyent lx-brand container environment an upgrade of the makedev
  package fails at the post-installation script:

  # apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ...
  mknod: ‘mem-’: Operation not permitted
  makedev mem c 1 1 root kmem 0640: failed
  mknod: ‘kmem-’: Operation not permitted
  makedev kmem c 1 2 root kmem 0640: failed
  mknod: ‘null-’: Operation not permitted
  makedev null c 1 3 root root 0666: failed
  mknod: ‘port-’: Operation not permitted
  makedev port c 1 4 root kmem 0640: failed
  mknod: ‘zero-’: Operation not permitted
  makedev zero c 1 5 root root 0666: failed
  mknod: ‘full-’: Operation not permitted
  makedev full c 1 7 root root 0666: failed
  mknod: ‘random-’: Operation not permitted
  makedev random c 1 8 root root 0666: failed
  mknod: ‘urandom-’: Operation not permitted
  makedev urandom c 1 9 root root 0666: failed
  mknod: ‘tty-’: Operation not permitted
  makedev tty c 5 0 root tty 0666: failed
  mknod: ‘ram0-’: Operation not permitted
  makedev ram0 b 1 0 root disk 0660: failed
  mknod: ‘ram1-’: Operation not permitted
  makedev ram1 b 1 1 root disk 0660: failed
  mknod: ‘ram2-’: Operation not permitted
  makedev ram2 b 1 2 root disk 0660: failed
  mknod: ‘ram3-’: Operation not permitted
  makedev ram3 b 1 3 root disk 0660: failed
  mknod: ‘ram4-’: Operation not permitted
  makedev ram4 b 1 4 root disk 0660: failed
  mknod: ‘ram5-’: Operation not permitted
  makedev ram5 b 1 5 root disk 0660: failed
  mknod: ‘ram6-’: Operation not permitted
  makedev ram6 b 1 6 root disk 0660: failed
  mknod: ‘ram7-’: Operation not permitted
  makedev ram7 b 1 7 root disk 0660: failed
  mknod: ‘ram8-’: Operation not permitted
  makedev ram8 b 1 8 root disk 0660: failed
  mknod: ‘ram9-’: Operation not permitted
  makedev ram9 b 1 9 root disk 0660: failed
  mknod: ‘ram10-’: Operation not permitted
  makedev ram10 b 1 10 root disk 0660: failed
  mknod: ‘ram11-’: Operation not permitted
  makedev ram11 b 1 11 root disk 0660: failed
  mknod: ‘ram12-’: Operation not permitted
  makedev ram12 b 1 12 root disk 0660: failed
  mknod: ‘ram13-’: Operation not permitted
  makedev ram13 b 1 13 root disk 0660: failed
  mknod: ‘ram14-’: Operation not permitted
  makedev ram14 b 1 14 root disk 0660: failed
  mknod: ‘ram15-’: Operation not permitted
  makedev ram15 b 1 15 root disk 0660: failed
  mknod: ‘ram16-’: Operation not permitted
  makedev ram16 b 1 16 root disk 0660: failed
  mknod: ‘loop0-’: Operation not permitted
  makedev loop0 b 7 0 root disk 0660: failed
  mknod: ‘loop1-’: Operation not permitted
  makedev loop1 b 7 1 root disk 0660: failed
  mknod: ‘loop2-’: Operation not permitted
  makedev loop2 b 7 2 root disk 0660: failed
  mknod: ‘loop3-’: Operation not permitted
  makedev loop3 b 7 3 root disk 0660: failed
  mknod: ‘loop4-’: Operation not permitted
  makedev loop4 b 7 4 root disk 0660: failed
  mknod: ‘loop5-’: Operation not permitted
  makedev loop5 b 7 5 root disk 0660: failed
  mknod: ‘loop6-’: Operation not permitted
  makedev loop6 b 7 6 root disk 0660: failed
  mknod: ‘loop7-’: Operation not permitted
  makedev loop7 b 7 7 root disk 0660: failed
  mknod: ‘tty0-’: Operation not permitted
  makedev tty0 c 4 0 root tty 0600: failed
  mknod: ‘console-’: Operation not permitted
  makedev console c 5 1 root tty 0600: failed
  ln: failed to create symbolic link ‘fd/fd’: Function not implemented
  ln: failed to create symbolic link ‘stdin’: File exists
  ln: failed to create symbolic link ‘stdout’: File exists
  ln: failed to create symbolic link ‘stderr’: File exists
  /sbin/MAKEDEV: don't know how to make device "tty0"
  dpkg: error processing package makedev (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   makedev
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  The workaround is similar to

[Touch-packages] [Bug 1679727] Re: Don't attempt to create devices in lx-brand containers

2017-04-19 Thread RussianNeuroMancer

Same issue in machined containers.

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

Title:
  Don't attempt to create devices in lx-brand containers

Status in makedev package in Ubuntu:
  Confirmed

Bug description:
  This is a similar issue to
  https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163

  In a Joyent lx-brand container environment an upgrade of the makedev
  package fails at the post-installation script:

  # apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ...
  mknod: ‘mem-’: Operation not permitted
  makedev mem c 1 1 root kmem 0640: failed
  mknod: ‘kmem-’: Operation not permitted
  makedev kmem c 1 2 root kmem 0640: failed
  mknod: ‘null-’: Operation not permitted
  makedev null c 1 3 root root 0666: failed
  mknod: ‘port-’: Operation not permitted
  makedev port c 1 4 root kmem 0640: failed
  mknod: ‘zero-’: Operation not permitted
  makedev zero c 1 5 root root 0666: failed
  mknod: ‘full-’: Operation not permitted
  makedev full c 1 7 root root 0666: failed
  mknod: ‘random-’: Operation not permitted
  makedev random c 1 8 root root 0666: failed
  mknod: ‘urandom-’: Operation not permitted
  makedev urandom c 1 9 root root 0666: failed
  mknod: ‘tty-’: Operation not permitted
  makedev tty c 5 0 root tty 0666: failed
  mknod: ‘ram0-’: Operation not permitted
  makedev ram0 b 1 0 root disk 0660: failed
  mknod: ‘ram1-’: Operation not permitted
  makedev ram1 b 1 1 root disk 0660: failed
  mknod: ‘ram2-’: Operation not permitted
  makedev ram2 b 1 2 root disk 0660: failed
  mknod: ‘ram3-’: Operation not permitted
  makedev ram3 b 1 3 root disk 0660: failed
  mknod: ‘ram4-’: Operation not permitted
  makedev ram4 b 1 4 root disk 0660: failed
  mknod: ‘ram5-’: Operation not permitted
  makedev ram5 b 1 5 root disk 0660: failed
  mknod: ‘ram6-’: Operation not permitted
  makedev ram6 b 1 6 root disk 0660: failed
  mknod: ‘ram7-’: Operation not permitted
  makedev ram7 b 1 7 root disk 0660: failed
  mknod: ‘ram8-’: Operation not permitted
  makedev ram8 b 1 8 root disk 0660: failed
  mknod: ‘ram9-’: Operation not permitted
  makedev ram9 b 1 9 root disk 0660: failed
  mknod: ‘ram10-’: Operation not permitted
  makedev ram10 b 1 10 root disk 0660: failed
  mknod: ‘ram11-’: Operation not permitted
  makedev ram11 b 1 11 root disk 0660: failed
  mknod: ‘ram12-’: Operation not permitted
  makedev ram12 b 1 12 root disk 0660: failed
  mknod: ‘ram13-’: Operation not permitted
  makedev ram13 b 1 13 root disk 0660: failed
  mknod: ‘ram14-’: Operation not permitted
  makedev ram14 b 1 14 root disk 0660: failed
  mknod: ‘ram15-’: Operation not permitted
  makedev ram15 b 1 15 root disk 0660: failed
  mknod: ‘ram16-’: Operation not permitted
  makedev ram16 b 1 16 root disk 0660: failed
  mknod: ‘loop0-’: Operation not permitted
  makedev loop0 b 7 0 root disk 0660: failed
  mknod: ‘loop1-’: Operation not permitted
  makedev loop1 b 7 1 root disk 0660: failed
  mknod: ‘loop2-’: Operation not permitted
  makedev loop2 b 7 2 root disk 0660: failed
  mknod: ‘loop3-’: Operation not permitted
  makedev loop3 b 7 3 root disk 0660: failed
  mknod: ‘loop4-’: Operation not permitted
  makedev loop4 b 7 4 root disk 0660: failed
  mknod: ‘loop5-’: Operation not permitted
  makedev loop5 b 7 5 root disk 0660: failed
  mknod: ‘loop6-’: Operation not permitted
  makedev loop6 b 7 6 root disk 0660: failed
  mknod: ‘loop7-’: Operation not permitted
  makedev loop7 b 7 7 root disk 0660: failed
  mknod: ‘tty0-’: Operation not permitted
  makedev tty0 c 4 0 root tty 0600: failed
  mknod: ‘console-’: Operation not permitted
  makedev console c 5 1 root tty 0600: failed
  ln: failed to create symbolic link ‘fd/fd’: Function not implemented
  ln: failed to create symbolic link ‘stdin’: File exists
  ln: failed to create symbolic link ‘stdout’: File exists
  ln: failed to create symbolic link ‘stderr’: File exists
  /sbin/MAKEDEV: don't know how to make device "tty0"
  dpkg: error processing package makedev (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   makedev
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  The workaround is similar to 1675163 except in this case the post-
  installation script should check for "container=zone" in
  '/proc/1/environ':

  
  if grep -q container=zone /proc/1/environ
  then
  echo "lx-brand container detected."
  exit 0
  fi

To manage notifications about this bug go to:

[Touch-packages] [Bug 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

2016-09-14 Thread RussianNeuroMancer

Thank you, Martin!

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

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Fix Released
Status in systemd package in Fedora:
  Unknown

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
    File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
    File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
    File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  ---
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

  SRU INFORMATION
  ===
  Fix: 
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=5c4291769cb426a

  Regression potential: This changes a central place of systemd
  (although the fix is quite obvious), so if that code is broken it
  could potentially lead to boot failure. However, the fix has been
  tested in yakkety, and all the time in upstrean and downstream CI, so
  if this would actually break anything it should have surfaced by now.
  So low overall.

  Test case: Should be verified by the reporter as the bug description
  did not include a reproducer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1491612] Re: doesn't scan for available wifi networks often enough + no way to manually force a scan

2016-08-15 Thread RussianNeuroMancer

I think do frequent automatic rescan could hurt battery life, so menu
item for manual rescan would be better idea.

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

Title:
  doesn't scan for available wifi networks often enough + no way to
  manually force a scan

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  - turn on a wifi router nearby
  - click on the network applet icon

  Expected behavior:
  As soon as the new network becomes available, it should become visible in the 
list within few seconds (and if it is a network you have already configured and 
set to automatically connect to, it should connect)

  Observed behavior:
  You won't see the network show up in the list, or perhaps it will, after a 
few minutes. Way too much time.

  
  Additionally, there should be an item in the menu such as "scan for networks 
now" to force scanning for available networks. But there's no such thing even.

  So the only workaround is to physically disable and reenable wifi on
  hardware, if your computer has a button for that. That will trigger
  re-scanning for available networks.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
  Uname: Linux 3.19.0-26-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep  2 23:48:42 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-11 (691 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.167
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-08-15 (18 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2015-02-20T16:52:59.722501
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTION   CON-UUID  CON-PATH
   
   wlan0  wifi  connected 
/org/freedesktop/NetworkManager/Devices/2  Sixty-Seven  
2dfa6e3a-076f-48f9-a40c-d182c47e4178  
/org/freedesktop/NetworkManager/ActiveConnection/0 
   43:29:1A:07:53:91  btdisconnected  
/org/freedesktop/NetworkManager/Devices/3  --   --  
  -- 
   eth0   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  -- 
   lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/0  --   --  
  --
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1491612/+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 433897] Re: Console/VT font is (randomly) not set (sometimes) on some machines. Stuck with the default VGA BIOS font.

2016-04-07 Thread RussianNeuroMancer

Patch: https://bugs.launchpad.net/ubuntu/+source/console-
setup/+bug/1565542

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

Title:
  Console/VT font is (randomly) not set (sometimes) on some machines.
  Stuck with the default VGA BIOS font.

Status in console-setup:
  New
Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Precise:
  Confirmed
Status in console-setup source package in Quantal:
  Won't Fix

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has 
started, the font is no longer set at bootup. This results in unreadable user 
prompts, whenever applications output non-ascii characters to screen and it 
also affects graphic box characters used by ncurses, such as for debconf 
dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/console-setup/+bug/433897/+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 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-15 Thread RussianNeuroMancer

> show something different than the original path?
No, only path that represent current image location (inside btrfs snapshot).

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

Title:
  virsh save doesn't work for vm with hdd image in non-default location,
  AppArmor-related error

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
  Error message:
  ~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
  error: Failed to save domain owncloud to 
/mnt/storage/data/images/owncloud.dump
  error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  Translation:
  error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  I tried to dumpxml and then define it again from xml, but that doesn't help.
  Ubuntu Server 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1531703/+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 1531703] Re: virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-03-11 Thread RussianNeuroMancer

This particular VM is removed now (guest moved to nspawn container) but
I find xml in host btrfs snapshots.

** Attachment added: "owncloud.xml"
   
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1531703/+attachment/4595747/+files/owncloud.xml

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

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

Title:
  virsh save doesn't work for vm with hdd image in non-default location,
  AppArmor-related error

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
  Error message:
  ~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
  error: Failed to save domain owncloud to 
/mnt/storage/data/images/owncloud.dump
  error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  Translation:
  error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  I tried to dumpxml and then define it again from xml, but that doesn't help.
  Ubuntu Server 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1531703/+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 1481832] Re: VA-API implementation for gallium missing

2016-03-07 Thread RussianNeuroMancer

Oibaf, you mean there is native VA-API implementation via
gallium_drv_video.so, not via vdpau-va-driver package?

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832/+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 1481832] Re: VA-API implementation for gallium missing

2016-03-04 Thread RussianNeuroMancer

Then maybe at least provide PPA with Mesa builds with enabled VA-API support?
Here, for example: https://launchpad.net/~graphics-drivers

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832/+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 1047761] Re: console-setup/utf8

*** This bug is a duplicate of bug 433897 ***
https://bugs.launchpad.net/bugs/433897

** This bug is no longer a duplicate of bug 657551
   console-setup doesn't start
** This bug has been marked a duplicate of bug 433897
   Console/VT font is (randomly) not set (sometimes) on some machines. Stuck 
with the default VGA BIOS font.

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

Title:
  console-setup/utf8

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  console-setup: 1.70ubuntu5

  Hi, i'm using ubuntu 12.04.1/LTS with latest updates i have some
  trouble with fonts in tty. By default there is no national language
  support in console (squares instead symbols). So I run sudo dpkg-
  reconfigure console-setup, choose UTF8->cyrilic->TerminusBoldVGA->14,
  then run setupcon and everything fine. But after rebooting, the
  console was resets to defaults without NLS.

  LANG=ru_RU.UTF-8 is everytime, in Xorg everything is ok.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1047761/+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 433897] Re: Console/VT font is (randomly) not set (sometimes) on some machines. Stuck with the default VGA BIOS font.

Still happening in Xenial. There is workaround:
https://bugs.launchpad.net/ubuntu/+source/console-
setup/+bug/657551/comments/23

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

Title:
  Console/VT font is (randomly) not set (sometimes) on some machines.
  Stuck with the default VGA BIOS font.

Status in console-setup:
  New
Status in console-setup package in Ubuntu:
  Confirmed
Status in console-setup source package in Precise:
  Confirmed
Status in console-setup source package in Quantal:
  Won't Fix

Bug description:
  [Impact]

  [Fix]

  [Test Case]

  [Regression Potential]

  [Original Report]
  Since the Karmic transition away from init.d scripts to upstart services has 
started, the font is no longer set at bootup. This results in unreadable user 
prompts, whenever applications output non-ascii characters to screen and it 
also affects graphic box characters used by ncurses, such as for debconf 
dialogs.

  ProblemType: Bug
  Architecture: i386
  Date: Mon Sep 21 12:51:40 2009
  DistroRelease: Ubuntu 9.10
  Package: console-setup 1.34ubuntu2
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fi_FI.UTF-8
   PATH=(custom, user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
  SourcePackage: console-setup
  Uname: Linux 2.6.31-10-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/console-setup/+bug/433897/+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 657551] Re: console-setup doesn't start

*** This bug is a duplicate of bug 433897 ***
https://bugs.launchpad.net/bugs/433897

** This bug has been marked a duplicate of bug 433897
   Console/VT font is (randomly) not set (sometimes) on some machines. Stuck 
with the default VGA BIOS font.

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

Title:
  console-setup doesn't start

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: console-setup

  On startup console-setup doesn't startup and I have wrong font on my console 
- it doesn't display Cyrillic.
  When I try to start it by hand I get:
  xxx@xxx:~/$ sudo service console-setup start
  console-setup stop/waiting

  When I do dpkg-reconfigure I get console font loaded until next reboot.
  I have all maveric, recently updated from 10.04. All updates installed 
regularly.
  Please let me know if I can provide any more information.
  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: console-setup 1.34ubuntu15
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Sun Oct 10 01:29:48 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=ru_RU:ru:en_GB:en
   PATH=(custom, user)
   LANG=ru_RU.utf8
   SHELL=/bin/bash
  SourcePackage: console-setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/657551/+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 713746] Re: console-setup bug with none-english locales

*** This bug is a duplicate of bug 433897 ***
https://bugs.launchpad.net/bugs/433897

** This bug is no longer a duplicate of bug 657551
   console-setup doesn't start
** This bug has been marked a duplicate of bug 433897
   Console/VT font is (randomly) not set (sometimes) on some machines. Stuck 
with the default VGA BIOS font.

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

Title:
  console-setup bug with none-english locales

Status in console-setup:
  Invalid
Status in console-setup package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: console-setup

  console-setup bug with cyrillic while rebooting the system.
  sudo /etc/init.d/console-setup restart :FAIL
  sudo dpkg-reconfigure console-setup :OK
  sudo reboot: FAIL (cyrillic).
  Pls, fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: console-setup 1.57ubuntu5
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  Date: Sat Feb  5 19:55:11 2011
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=ru_UA:ru:en_GB:en
   LANG=ru_UA.UTF-8
   LC_MESSAGES=ru_UA.utf8
   SHELL=/bin/bash
  SourcePackage: console-setup

To manage notifications about this bug go to:
https://bugs.launchpad.net/console-setup/+bug/713746/+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 1510276] Re: console-setup font ignored on boot

*** This bug is a duplicate of bug 433897 ***
https://bugs.launchpad.net/bugs/433897

** This bug is no longer a duplicate of bug 657551
   console-setup doesn't start
** This bug has been marked a duplicate of bug 433897
   Console/VT font is (randomly) not set (sometimes) on some machines. Stuck 
with the default VGA BIOS font.

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

Title:
  console-setup font ignored on boot

Status in console-setup package in Ubuntu:
  New

Bug description:
  Since cyrillic characters are not supported by the default font I
  tried to run

  # dpkg-reconfigure console-setup

  to change the font. It worked but only until the reboot. After
  rebooting I have to manually run setupcon or add it to rc.local or
  somewhere to make the adequate font appear.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: console-setup 1.108ubuntu9
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 26 22:35:03 2015
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1510276/+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 668360] Re: In the text mode cyrillic symbols are displayed as squares

*** This bug is a duplicate of bug 433897 ***
https://bugs.launchpad.net/bugs/433897

** This bug is no longer a duplicate of bug 609775
   Cyrillic characters doesn't displayed in VT and recovery mode
** This bug has been marked a duplicate of bug 433897
   Console/VT font is (randomly) not set (sometimes) on some machines. Stuck 
with the default VGA BIOS font.

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

Title:
  In the text mode cyrillic symbols are displayed as squares

Status in console-setup package in Ubuntu:
  New

Bug description:
  When I switch to the TTY1 (Ctrl+Alt+F1) all the cyrillic symbols are
  displayed as white squares. UNE 10.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/668360/+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 609775] Re: Cyrillic characters doesn't displayed in VT and recovery mode

2016-02-25 Thread RussianNeuroMancer

This issue is still reproducible on fresh installation of 
Ubuntu Server 16.04
Kubuntu 16.04
Xubuntu 16.04

As far I understand this is installer issue so it have nothing to do
with console-setup package, because if user installed Ubuntu with some
cyrillic language - cyrillic characters should be displayed correctly in
VT and recovery mode after installation - it's not user, but installer
job to take care of this.

** Also affects: debian-installer
   Importance: Undecided
   Status: New

** No longer affects: debian-installer

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: console-setup (Ubuntu)

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

Title:
  Cyrillic characters doesn't displayed in VT and recovery mode

Status in debian-installer package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Cyrillic characters doesn't displayed in VT and recovery mode since
  Kubuntu Natty. When I open VT or recovery console in Lucid all
  cyrillic characters displayed in without problems. But in Natty I see
  only rectangles instead of letters.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/609775/+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 990635] Re: Sans serif cyrillic font in kubuntu 12.04 is bad

2016-02-25 Thread RussianNeuroMancer

This is not reproducible in 14.04 (maybe earlier) as far I remember.

** No longer affects: hundredpapercuts

** No longer affects: fonts-nanum (Ubuntu)

** Changed in: fontconfig (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: qt4-x11 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Sans serif cyrillic font in kubuntu 12.04 is bad

Status in fontconfig package in Ubuntu:
  Fix Released
Status in qt4-x11 package in Ubuntu:
  Fix Released

Bug description:
  1) 'lsb_release -rd': 
  Description:Ubuntu 12.04 LTS
  Release:12.04

  2) Software version - default for kubuntu 12.04 on 28.04.2012 (no
  additional repositories)

  3) Description:
  Default font alias for 'Sans Serif' (cyrillic) looks horrible in kubuntu 
12.04. This font appear in KDM and when running programs with root access level 
(e.g. 'kdesudo kate').

  AFAIK the default alias for 'Sans Serif' font family is 'Dejavu Sans'. But in 
kubuntu 12.04 this setting got broken somehow.
  So now 'Sans Serif' (also 'Serif' and 'Monospace') have wrong aliases (I 
think it is 'Nimbus L' font family).

  See the attached screenshot for details (this is what shows up when
  running 'kdesudo kate').

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/990635/+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 1529079] Re: Can't start virtual machines with installed systemd-container package on Xenial

2016-02-17 Thread RussianNeuroMancer

** Summary changed:

- Can't start virtual machines after upgrade to Xenial
+ Can't start virtual machines with installed systemd-container package on 
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/1529079

Title:
  Can't start virtual machines with installed systemd-container package
  on Xenial

Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-02-13 Thread RussianNeuroMancer

Issue is still reproducible with latest version of libvirt package.

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

Title:
  Can't start virtual machines after upgrade to Xenial

Status in libvirt package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-02-09 Thread RussianNeuroMancer

Issue is still reproducible on Kubuntu 16.04 with installed updates. I
reproduced it with xml from commentary #15.

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

Title:
  Can't start virtual machines after upgrade to Xenial

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

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-24 Thread RussianNeuroMancer

Please tell me how I can help you find root of this issue? As I said,
reproducible for me on two installations (Kubuntu and Ubuntu Server).

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

Title:
  Can't start virtual machines after upgrade to Xenial

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

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-24 Thread RussianNeuroMancer

Maybe error message from #12 and#16 provide any useful information?

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

Title:
  Can't start virtual machines after upgrade to Xenial

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

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-19 Thread RussianNeuroMancer

> I still cannot reproduce this at all, even when starting VMs from 
> virt-manager.
Well, for fresh install this is not reproducible for me too. And 15.10-16.04 
upgrade may not be actual trigger - both testing systems get upgraded for a 
long time, Kubuntu from 11.04 as I remember. So there is may be something 
ancient that showed up just now. Or not so ancient - maybe some 
upstart->systemd upgrade issue. I have no idea actually what it may be. How I 
can help here find what's going on?

> Are you still able to reproduce this? (I'm wondering whether perhaps there 
> was a temporary bad state of systemd and libvirt being out of sync some 
> magical way)
Still reproducible on my testing Kubuntu 16.04 setup. I can try Ubuntu Server 
15.10->16.04 upgrade once again, if necessary. Is it needed if issue still 
reproducible on updated Kubuntu 16.04?

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

Title:
  Can't start virtual machines after upgrade to Xenial

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

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-19 Thread RussianNeuroMancer

> And it is still reproducible after reboot after the upgrade, right?
Yes, this Kubuntu was rebooted yesterday after system upgrade.

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

Title:
  Can't start virtual machines after upgrade to Xenial

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

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529079] Re: Can't start virtual machines after upgrade to Xenial

2016-01-07 Thread RussianNeuroMancer

> > I can add systemd package as affected package again?
> Yes I think that's fair, though it's more likely a bug in libvirt's use of 
> systemd-machined.

Okay, I added systemd package as affected.

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't start virtual machines after upgrade to Xenial

Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages in 
syslog when this error appear on the screen (or virsh output). Both systems was 
upgraded from 15.10.
  --- 
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  Package: libvirt (not installed)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.3.3-040303-generic 
root=UUID=a100d974-72cf-44ad-acf8-6ec060b773dd ro rootflags=subvol=@Xenial 
quiet nomdmonddf nomdmonisw
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=C
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.3.3-040303-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified]
  mtime.conffile..etc.libvirt.qemu.networks.default.xml: 
2015-02-27T11:49:59.773560

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529074] Re: Due to AppArmor profile restrictions Telepathy can't connect when networkd used instead of NetworkManager

2016-01-06 Thread RussianNeuroMancer

Thanks for fix!

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

Title:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager. That was tested with KDE
  Telepathy on Kubuntu 16.04. Error message:

  [ 2907.344638] audit: type=1400 audit(1450959038.587:32): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2907.345097] audit: type=1400 audit(1450959038.587:33): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300267] audit: type=1400 audit(1450959056.544:34): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300656] audit: type=1400 audit(1450959056.544:35): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915149] audit: type=1400 audit(1450959064.156:36): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915975] audit: type=1400 audit(1450959064.156:37): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.949765] audit: type=1400 audit(1450959105.184:38): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.951471] audit: type=1400 audit(1450959105.188:39): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1529074/+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 1531703] [NEW] virsh save doesn't work for vm with hdd image in non-default location, AppArmor-related error

2016-01-06 Thread RussianNeuroMancer

Public bug reported:

virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
Error message:
~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
error: Failed to save domain owncloud to /mnt/storage/data/images/owncloud.dump
error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

Translation:
error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

I tried to dumpxml and then define it again from xml, but that doesn't help.
Ubuntu Server 15.10.

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

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

** Also affects: apparmor
   Importance: Undecided
   Status: New

** Project changed: apparmor => apparmor (Ubuntu)

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

Title:
  virsh save doesn't work for vm with hdd image in non-default location,
  AppArmor-related error

Status in apparmor package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  New

Bug description:
  virsh save does work for vm located in /var/lib/libvirt/images, but doesn't 
work for vm located for example in /mnt/storage/data/limages
  Error message:
  ~$ LANG=C virsh save owncloud /mnt/storage/data/images/owncloud.dump
  error: Failed to save domain owncloud to 
/mnt/storage/data/images/owncloud.dump
  error: внутренняя ошибка: не удалось обновить профиль AppArmor 
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  Translation:
  error: internal error: unable to update AppArmor profile  
«libvirt-b9f02241-f8a7-4c11-86de-5eccbdff6511»

  I tried to dumpxml and then define it again from xml, but that doesn't help.
  Ubuntu Server 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1531703/+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 1529074] [NEW] Due to AppArmor profile restrictions Telepathy can't connect when networkd used instead of NetworkManager

2015-12-24 Thread RussianNeuroMancer

Public bug reported:

Due to AppArmor profile restrictions Telepathy can't connect when
networkd used instead of NetworkManager. That was tested with KDE
Telepathy on Kubuntu 16.04. Error message:

[ 2907.344638] audit: type=1400 audit(1450959038.587:32): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2907.345097] audit: type=1400 audit(1450959038.587:33): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2925.300267] audit: type=1400 audit(1450959056.544:34): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2925.300656] audit: type=1400 audit(1450959056.544:35): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2932.915149] audit: type=1400 audit(1450959064.156:36): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2932.915975] audit: type=1400 audit(1450959064.156:37): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2973.949765] audit: type=1400 audit(1450959105.184:38): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
[ 2973.951471] audit: type=1400 audit(1450959105.188:39): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125

** Affects: telepathy-mission-control-5 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apparmor wily xenial

** Tags added: apparmor wily xenial

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

Title:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager

Status in telepathy-mission-control-5 package in Ubuntu:
  New

Bug description:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager. That was tested with KDE
  Telepathy on Kubuntu 16.04. Error message:

  [ 2907.344638] audit: type=1400 audit(1450959038.587:32): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2907.345097] audit: type=1400 audit(1450959038.587:33): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300267] audit: type=1400 audit(1450959056.544:34): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300656] audit: type=1400 audit(1450959056.544:35): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915149] audit: type=1400 audit(1450959064.156:36): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915975] audit: type=1400 audit(1450959064.156:37): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.949765] audit: type=1400 audit(1450959105.184:38): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.951471] audit: type=1400 audit(1450959105.188:39): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r"

[Touch-packages] [Bug 1529079] [NEW] Can't start virtual machines after upgrade to Xenial

2015-12-24 Thread RussianNeuroMancer

Public bug reported:

Can't start virtual machines after upgrade to Xenial.

On Ubuntu Server 16.04:
# virsh start testserver
Cannot set property Before, or unknown property.

On Kubuntu 16.04:
Cannot set property Before, or unknown property.
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in cb_wrapper
callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/create.py", line 1873, in do_install
guest.start_install(meter=meter)
  File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
noboot)
  File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
libvirtError: Cannot set property Before, or unknown property.

At this moment there is no libvirt or systemd-related error messages in
syslog when this error appear on the screen (or virsh output). Both
systems was upgraded from 15.10.

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

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


** Tags: regression-release xenial

** Attachment added: "virt-manager.png"
   
https://bugs.launchpad.net/bugs/1529079/+attachment/4539684/+files/virt-manager.png

** Also affects: systemd (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Can't start virtual machines after upgrade to Xenial

Status in libvirt package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Can't start virtual machines after upgrade to Xenial.

  On Ubuntu Server 16.04:
  # virsh start testserver
  Cannot set property Before, or unknown property.

  On Kubuntu 16.04:
  Cannot set property Before, or unknown property.
  Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in 
cb_wrapper
  callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1873, in 
do_install
  guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 414, in start_install
  noboot)
File "/usr/share/virt-manager/virtinst/guest.py", line 478, in _create_guest
  dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/dist-packages/libvirt.py", line 3585, in 
createLinux
  if ret is None:raise libvirtError('virDomainCreateLinux() failed', 
conn=self)
  libvirtError: Cannot set property Before, or unknown property.

  At this moment there is no libvirt or systemd-related error messages
  in syslog when this error appear on the screen (or virsh output). Both
  systems was upgraded from 15.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1529079/+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 1529074] Re: Due to AppArmor profile restrictions Telepathy can't connect when networkd used instead of NetworkManager

2015-12-24 Thread RussianNeuroMancer

Workaround: add line
/run/systemd/resolve/resolv.confr,
to section /usr/lib/telepathy/telepathy-* in file 
/etc/apparmor.d/usr.lib.telepathy and then restart AppArmor.

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

Title:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager

Status in telepathy-mission-control-5 package in Ubuntu:
  Confirmed

Bug description:
  Due to AppArmor profile restrictions Telepathy can't connect when
  networkd used instead of NetworkManager. That was tested with KDE
  Telepathy on Kubuntu 16.04. Error message:

  [ 2907.344638] audit: type=1400 audit(1450959038.587:32): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2907.345097] audit: type=1400 audit(1450959038.587:33): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3758 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300267] audit: type=1400 audit(1450959056.544:34): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2925.300656] audit: type=1400 audit(1450959056.544:35): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3765 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915149] audit: type=1400 audit(1450959064.156:36): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2932.915975] audit: type=1400 audit(1450959064.156:37): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3772 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.949765] audit: type=1400 audit(1450959105.184:38): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125
  [ 2973.951471] audit: type=1400 audit(1450959105.188:39): apparmor="DENIED" 
operation="open" profile="/usr/lib/telepathy/telepathy-*" 
name="/run/systemd/resolve/resolv.conf" pid=3833 comm="pool" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=125

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1529074/+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 1481832] Re: VA-API implementation for gallium missing

2015-12-16 Thread RussianNeuroMancer

nouveau: add support for vaapi
http://lists.freedesktop.org/archives/mesa-dev/2015-December/103327.html

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

Title:
  VA-API implementation for gallium missing

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [needs-packaging] mesa
  Please include "gallium_drv_video.so" which is a native va-api state tracker 
for mesa(gallium).

  URL: http://mesa3d.sourceforge.net/
  URL: http://freedesktop.org/wiki/Software/vaapi/ #intel/vdpau
  License: http://www.mesa3d.org/license.html

  Notes:
  Currently (as of today) in ubuntu 15.10 nightly amd64, va-api(vaapi) on 
AMD/Ati radeon opensource display hardware is using a vdpau backend  0.7.4 by 
Splitted-Desktop Systems (wrapper) on gallium r600. Although its possible and 
probably preferred (better performance less copying) to use a native 
implementation which mesa(gallium) 10.4 and higher delivers in a form of a 
va-api state tracker.

  vainfo #current default setup vdpau backend
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
  libva info: Found init function __vaDriverInit_0_37
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: Splitted-Desktop Systems VDPAU backend for VA-API - 
0.7.4
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD

  The preferred setup needs that "gallium_drv_video.so" binary which is
  currently unavailable in ubuntu and debian. As an example I added a
  package/binary from archlinux. Copying the gallium_drv_video.so to
  /usr/lib/x86_64-linux-gnu/dri/ and symlinking(correcting) the
  libLLVM-3.6.so to arch-linux default /usr/lib/ location and exporting
  a variable was enough to make it work!
  https://www.archlinux.org/packages/extra/x86_64/libva-mesa-driver/
  #example by archlinux

  export LIBVA_DRIVER_NAME=gallium
  vainfo #preferred setup using gallium va-api from arch-linux (symlinked 
libLLVM-3.6.so to /usr/lib)
  libva info: VA-API version 0.38.0
  libva info: va_getDriverName() returns 0
  libva info: User requested driver 'gallium'
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: Found init function __vaDriverInit_0_38
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 0.38 (libva 1.6.0)
  vainfo: Driver version: mesa gallium vaapi
  vainfo: Supported profile and entrypoints
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileMPEG4Simple:   VAEntrypointVLD
    VAProfileMPEG4AdvancedSimple:   VAEntrypointVLD
    VAProfileVC1Advanced:   VAEntrypointVLD
    VAProfileH264Baseline   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointVLD

  I guess this binary "gallium_drv_video.so" might be available as a
  compile flag in the current mesa implementation... intel and vdpau has
  their own current implementation in a separate libva branch
  http://cgit.freedesktop.org/vaapi/libva/ ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832/+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 1493449] Re: Crash in libexa with radeon driver

2015-09-30 Thread RussianNeuroMancer

I can't reproduce this crash right now (with current kernel, drivers,
etc.)

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Crash in libexa with radeon driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  My previous report:
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312

  After latest xorg-server update previous crash seems like doesn't happen 
anymore, however there is another crash now:
  [  3184.619] failed to map pixmap: -2
  [  3184.619] (EE) 
  [  3184.619] (EE) Backtrace:
  [  3184.619] (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x55951956662e]
  [  3184.620] (EE) 1: /usr/bin/X (0x5595193b2000+0x1b8999) [0x55951956a999]
  [  3184.620] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbac39c7000+0x352f0) 
[0x7fbac39fc2f0]
  [  3184.620] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbac39c7000+0x9ff70) 
[0x7fbac3a66f70]
  [  3184.620] (EE) 4: /usr/lib/xorg/modules/libexa.so (0x7fbabfa92000+0x52fe) 
[0x7fbabfa972fe]
  [  3184.620] (EE) 5: /usr/lib/xorg/modules/libexa.so (0x7fbabfa92000+0x57b3) 
[0x7fbabfa977b3]
  [  3184.620] (EE) 6: /usr/lib/xorg/modules/libexa.so (0x7fbabfa92000+0x7e8f) 
[0x7fbabfa99e8f]
  [  3184.620] (EE) 7: /usr/lib/xorg/modules/libexa.so (0x7fbabfa92000+0x10555) 
[0x7fbabfaa2555]
  [  3184.620] (EE) 8: /usr/bin/X (miCopyRegion+0xdc) [0x55951954663c]
  [  3184.620] (EE) 9: /usr/bin/X (miDoCopy+0x466) [0x559519546cb6]
  [  3184.620] (EE) 10: /usr/lib/xorg/modules/libexa.so (0x7fbabfa92000+0x8345) 
[0x7fbabfa9a345]
  [  3184.620] (EE) 11: /usr/bin/X (0x5595193b2000+0x13f941) [0x5595194f1941]
  [  3184.621] (EE) 12: /usr/bin/X (0x5595193b2000+0xf48ec) [0x5595194a68ec]
  [  3184.621] (EE) 13: /usr/bin/X (0x5595193b2000+0xf5ef5) [0x5595194a7ef5]
  [  3184.621] (EE) 14: /usr/bin/X (0x5595193b2000+0x5818f) [0x55951940a18f]
  [  3184.621] (EE) 15: /usr/bin/X (0x5595193b2000+0x5c34b) [0x55951940e34b]
  [  3184.621] (EE) 16: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fbac39e7a40]
  [  3184.621] (EE) 17: /usr/bin/X (_start+0x29) [0x5595193f86c9]
  [  3184.621] (EE) 
  [  3184.621] (EE) Segmentation fault at address 0x0
  [  3184.621] (EE) 
  Fatal server error:
  [  3184.621] (EE) Caught signal 11 (Segmentation fault). Server aborting

  Also dmesg is full of radeon driver related errors:
  [ 2859.128902] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
  [ 2859.142511] radeon :00:01.0: 
evergreen_surface_check_linear_aligned:212 texture pitch 624 invalid must be 
aligned with 64
  [ 2859.142530] radeon :00:01.0: evergreen_cs_track_validate_texture:827 
texture invalid 0x09d81341 0x1390 0x0a0a 0x 0x0004 
0x8002001a

  Logs attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1493449/+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 1484279] Re: [FFe] Mesa 11.0.0

2015-08-13 Thread RussianNeuroMancer

Maybe it's possible to take
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1481832 into account
while building Mesa 11 packages?

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

Title:
  [FFe] Mesa 11.0.0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  ### WIP ###

  Mesa 11.0.0 will be released as follows:

  August 21st 2015 - Feature freeze/Release candidate 1
  August 28th 2015 - Release candidate 2
  September 04th 2015 - Release candidate 3
  September 11th 2015 - Release candidate 4/Mesa 11.0.0

  so even rc1 will miss feature freeze, which is why this bug exists.

  [Changes]
  Wily has 10.6.3 (in proposed as of now), biggest new features compared to it 
are:
  - support for new 'amdgpu' driver (to be merged)
  - support for OpenGL 4.2 in core mesa
  .
  .
  .

  [Packaging status]
  - snapshots pushed to debian git
  - packaging updated when necessary
  - builds  works

  [Plan for testing]
  - a snapshot will be uploaded to debian-experimental and 
canonical-x/x-staging ppa, call-for-testing sent once it's available
  - piglit runs on most common hw (intel, radeon, nouveau)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1484279/+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 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days

2015-08-12 Thread RussianNeuroMancer

I get same crash with Intel GPU (ironlake generation) on another laptop,
but with fglrx this crash seems like not reproducible (with same Radeon
HD 6620G).

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

Title:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days. Sometimes crash may happen few times per day.
  This crash is reproducible with packages from main repository and from
  Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

  Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
  If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login). Currently radeon driver is 
used (GPU is Radeon HD 6620G).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+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 1482312] [NEW] After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days

Public bug reported:

After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
crash every few days. Sometimes crash may happen few times per day. This
crash is reproducible with packages from main repository and from Xorg
Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login).

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


** Tags: regression-release wily

** Attachment added: xorgcrash
   https://bugs.launchpad.net/bugs/1482312/+attachment/4440567/+files/xorgcrash

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

Title:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days. Sometimes crash may happen few times per day.
  This crash is reproducible with packages from main repository and from
  Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

  Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
  If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+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 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.04 X Server starting to crash every few days

** Attachment added: gdb-Xorg2.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+attachment/4440572/+files/gdb-Xorg2.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/1482312

Title:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days. Sometimes crash may happen few times per day.
  This crash is reproducible with packages from main repository and from
  Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

  Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
  If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+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 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.04 X Server starting to crash every few days

** Attachment added: Xorglog2

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+attachment/4440573/+files/Xorglog2

** Tags added: wily

** Tags added: regression-release

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

Title:
After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
crash every few days

Status in xorg package in Ubuntu:
New

Bug description:
After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
crash every few days. Sometimes crash may happen few times per day.
This crash is reproducible with packages from main repository and from
Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and
gdb-Xorg2.txt.
If this matter, Xorg also crash on login if I trying to start with glamor or
modesetting driver (but I doesn't sure it's a same crash). I didn't tried
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some
issues, but at least it doesn't crash on login).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+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 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days

** Summary changed:

- After upgrade from Kubuntu 15.04 to Kubuntu 15.04 X Server starting to crash 
every few days
+ After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash 
every few days

** Description changed:

- After upgrade from Kubuntu 15.04 to Kubuntu 15.04 X Server starting to
+ After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days. Sometimes crash may happen few times per day. This
  crash is reproducible with packages from main repository and from Xorg
  Edgers PPA. Attached logs is crated with Xorg Edgers PPA.
  
  Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
  If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login).

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

Title:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to
  crash every few days. Sometimes crash may happen few times per day.
  This crash is reproducible with packages from main repository and from
  Xorg Edgers PPA. Attached logs is crated with Xorg Edgers PPA.

  Please look into attached xorgcrash file. Other relevant logs is Xorglog2 and 
gdb-Xorg2.txt.
  If this matter, Xorg also crash on login if I trying to start with glamor or 
modesetting driver (but I doesn't sure it's a same crash). I didn't tried 
modesetting driver in Kubuntu 15.04, but glamor works for sure (with some 
issues, but at least it doesn't crash on login).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1482312/+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 1482312] Re: After upgrade from Kubuntu 15.04 to Kubuntu 15.10 X Server starting to crash every few days